[svn:bz-trunk] 18908: Fix failing MBean tests.

Revision: 18908
Revision: 18908
Author:   [email protected]
Date:     2010-12-01 11:58:31 -0800 (Wed, 01 Dec 2010)
Log Message:
Fix failing MBean tests. The name of the web application changed in the web.xml file for the webapp causing the test to break. I updated the test to use the new webapp name which is "Flex QA Web Application".
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/messagingservice/Streaming AMFEndpointMBean.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/messagingservice/Streaming HTTPEndpointMBean.mxml

Similar Messages

  • [svn:bz-trunk] 18907: Fix failing MBean test.

    Revision: 18907
    Revision: 18907
    Author:   [email protected]
    Date:     2010-12-01 11:55:22 -0800 (Wed, 01 Dec 2010)
    Log Message:
    Fix failing MBean test. The name of the web application changed in the web.xml file for the webapp causing the test to break. I updated the test to use the new webapp name which is "Flex QA Web Application". There are a few more MBean tests that are failing likely due to the same problem. I will update these as I have time unless someone else wants to tackle this.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/MBean/jmx/MBeanServerGateway.mxm l

    Pierre-Charles David a écrit :
    > Hi,
    >
    > I've got a very strange issue and I don't know where to look for to fix
    > it. In some Eclipse configuration I use, SWTBot does not work at all: it
    > fails the very first method with a WidgetNotFoundException.
    [snip]
    Well, I found the issue:
    SWTBot declares a dependency to org.apache.log4j but does not indicate
    any specific version. However, it uses APIs which only appeared in log4j
    1.2.12 (at least Logger.trace(), maybe others).
    In the Eclipse installation I have which did not work ("Topcased RCP"),
    there was a bundle which provided the org.apache.log4j package, but
    using log4j version 1.2.8. As it happens, Eclipse decided to provide
    this one to SWTBot instead of other versions available from different
    bundles (1.2.12 and 1.2.15). The test failed with an internal
    NoSuchMethodError, which must have been caught by some code and wrapped
    as the WidgetNotFoundException I saw.
    Removing the plugin with log4j 1.2.8 from the test's run configuration
    solves the issue.
    I have opened bug #286527 about this.

  • [svn:bz-trunk] 5137: Fix failing security tests on BlazeDS/ trunk by using a remote object to invalidate the FlexSession at the end of each test method which should cause each test method to run with a new /clean session.

    Revision: 5137
    Author: [email protected]
    Date: 2009-03-02 10:28:59 -0800 (Mon, 02 Mar 2009)
    Log Message:
    Fix failing security tests on BlazeDS/trunk by using a remote object to invalidate the FlexSession at the end of each test method which should cause each test method to run with a new/clean session. It looks like some test methods were leaving some things in a bad state which was causing the next test that ran to fail. These may be legitimate bugs/issues so we should investigate further to see what sequence of events gets things into a bad state but for these tests we want all of the test methods to run in isolation.
    Modified Paths:
    blazeds/trunk/qa/apps/qa-manual/WEB-INF/flex/services-config.mods.xml
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/flex/remoting-config.mods.xml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/JMSAuthSendSubscribeConstraintTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-http/JMSAuthSendSubscribeConstraintTest.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-http/MessagingAuthProSendTest.mxml
    Added Paths:
    blazeds/trunk/qa/apps/qa-regress/WEB-INF/src/qa/messaging/SessionManager.java

    In general theory, one now has the Edit button for their posts, until someone/anyone Replies to it. I've had Edit available for weeks, as opposed to the old forum's ~ 30 mins.
    That, however, is in theory. I've posted, and immediately seen something that needed editing, only to find NO Replies, yet the Edit button is no longer available, only seconds later. Still, in that same thread, I'd have the Edit button from older posts, to which there had also been no Replies even after several days/weeks. Found one that had to be over a month old, and Edit was still there.
    Do not know the why/how of this behavior. At first, I thought that maybe there WAS a Reply, that "ate" my Edit button, but had not Refreshed on my screen. Refresh still showed no Replies, just no Edit either. In those cases, I just Reply and mention the [Edit].
    Also, it seems that the buttons get very scrambled at times, and Refresh does not always clear that up. I end up clicking where I "think" the right button should be and hope for the best. Seems that when the buttons do bunch up they can appear at random around the page, often three atop one another, and maybe one way the heck out in left-field.
    While I'm on a role, it would be nice to be able to switch between Flattened and Threaded Views on the fly. Each has a use, and having to go to Options and then come back down to the thread is a very slow process. Jive is probably incapable of this, but I can dream.
    Hunt

  • [svn:bz-trunk] 23083: Fix failing MXUnit test.

    Revision: 23083
    Revision: 23083
    Author:   [email protected]
    Date:     2011-10-21 07:11:32 -0700 (Fri, 21 Oct 2011)
    Log Message:
    Fix failing MXUnit test.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/DateTy pesTest.mxml

  • [svn] 834: Fix failing MBean tests.

    Revision: 834
    Author: [email protected]
    Date: 2008-03-17 10:15:31 -0700 (Mon, 17 Mar 2008)
    Log Message:
    Fix failing MBean tests. The name of the qa-regress webapp changed in web.xml so the MBean name used in the tests needed to get updated.
    Modified Paths:
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/MBeanS erver/StreamingAMFEndpointMBean.mxml
    blazeds/branches/3.0.x/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/MBeanS erver/StreamingHTTPEndpointMBean.mxml

  • [svn:bz-trunk] 13380: Fix failing config suite tests.

    Revision: 13380
    Revision: 13380
    Author:   [email protected]
    Date:     2010-01-08 10:25:30 -0800 (Fri, 08 Jan 2010)
    Log Message:
    Fix failing config suite tests. One of these was due to an error message that got changed. The other two were due to the server's console log being different from the servlet log file. One of these I logged a bug for because the two error messages did not match at all. . . but in general when writing config suite tests you need to use the error message from the servlet log file and not the console output as these will be slightly different. . . and it's the servlet log file that the config suite checks.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/factories/NonExistentClassTest/e rror.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidMess ageTypeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/error.txt

  • [svn:bz-trunk] 23072: - fixed failing test on J2EE version based on . Net changes.

    Revision: 23072
    Revision: 23072
    Author:   [email protected]
    Date:     2011-10-20 06:59:14 -0700 (Thu, 20 Oct 2011)
    Log Message:
    - fixed failing test on J2EE version based on .Net changes.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/remotingService/dataTypes/Boolea nTypesTest.mxml

    The first thing I would do is go the the CF administrator and
    make sure all of your DEBUG information is being displayed. By
    default, some isn't. A lot of times when you get a .net error and
    it tells you nothing, go to the area below Execution Time and there
    is an exceptions area. That is usually where .NET errors are
    returned (system.nullReferenceException for example).
    When passing in strings, I typically assign it to a variable,
    then pass in the variable. It shouldn't matter, but sometimes I
    have run into issues with passing a string in. In your second
    object, look at the date object. The Coldfusion date object and the
    .Net date object are not the same. Hope this helps.

  • [svn:bz-trunk] 7681: Fix bunch of failing config tests on BlazeDS/ trunk by removing javax.servlet. UnavailableException from the expected error string.

    Revision: 7681
    Author:   [email protected]
    Date:     2009-06-09 11:44:36 -0700 (Tue, 09 Jun 2009)
    Log Message:
    Fix bunch of failing config tests on BlazeDS/trunk by removing javax.servlet.UnavailableException from the expected error string.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/destination/IncorrectRootElement Test/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/AdaptiveFrequencyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/FrequencyStepSizeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/AdaptiveServerT oClient/MaxQueueSizeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/DestinationWith NoChannelTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/DestinationWith NoIDTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidAckn owledgeModeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidDeli veryModeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidDest inationTypeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/InvalidMess ageTypeTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/NoConnectio nFactoryTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/jms/NoJNDINameT est/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidBufferPolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/InvalidConflatePolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/UnknownInboundPolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leInbound/frequencies/McfGreaterthanMfTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidBufferPolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidConflatePolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/InvalidErrorPolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/UnknownOutboundPolicyTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/throttle/thrott leOutbound/frequencies/McfGreaterthanMfTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/nonE xistingValidatorTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/same ExplicitTypeValidatorTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/same TypeValidatorTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/wron gTypeValidatorTest/error.txt

  • [svn:bz-trunk] 17048: Fix two failing config tests.

    Revision: 17048
    Revision: 17048
    Author:   [email protected]
    Date:     2010-07-23 12:09:49 -0700 (Fri, 23 Jul 2010)
    Log Message:
    Fix two failing config tests. Looks like the way messages get logged changed slightly which broke the tests. Should be fixed now. 
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/good ValidatorTest/error.txt
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/messagingService/validation/patt ernFilterLoggingValidatorTest/error.txt

  • [svn:bz-trunk] 16330: QA: Yes - Ran test locally and it was failing but tested condition was true - there is no services-config .xml file

    Revision: 16330
    Revision: 16330
    Author:   [email protected]
    Date:     2010-05-26 07:55:41 -0700 (Wed, 26 May 2010)
    Log Message:
    QA: Yes - Ran test locally and it was failing but tested condition was true - there is no services-config.xml file
    Doc: No
    Checkintests: NA
    Details: Updated expected error message to match current error.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/config/tests/NoServicesConfigFileTest/error.t xt

    I have uploaded detail.txt at below url.
    http://m.uploadedit.com/b041/1413264342685.txt
    Hi Mahesh,
    According to log file, I find the message ‘The setup100.exe.config file was not found, therefore the DTSWizard and SQLWatson app config files were not replaced’. It seems that the SQL Server setup file is not complete. Please check that if the SQL Server
    setup file is corrupted, if it is corrupted, please download it again and reinstall SQL Server 2008 R2.
    However, if there’s no problem with the setup file, please check that if there is third-party software such as anti-virus software on your computer blocking the process of SQL Server installation. In addition, make sure that you choose ‘Run as administrator’
    to launch the setup and configure SQL Server service accounts appropriately with administrator permission during the installation.
    For more details about this error, please review the following similar thread.
    http://answers.flyppdevportal.com/categories/sqlserver/sqlsetupandupgrade.aspx?ID=ad794a97-09ae-4aae-9d68-0b06f9af3e16
    Thanks,
    Lydia Zhang

  • [svn:osmf:] 15899: Attempted fix for unit tests failure.

    Revision: 15899
    Revision: 15899
    Author:   [email protected]
    Date:     2010-05-04 17:21:06 -0700 (Tue, 04 May 2010)
    Log Message:
    Attempted fix for unit tests failure.
    Modified Paths:
        osmf/trunk/framework/OSMFTest/org/osmf/OSMFTests.as

  • [svn:osmf:] 11014: Temporarily disable failing unit test.

    Revision: 11014
    Author:   [email protected]
    Date:     2009-10-19 16:09:18 -0700 (Mon, 19 Oct 2009)
    Log Message:
    Temporarily disable failing unit test.
    Modified Paths:
        osmf/trunk/framework/MediaFrameworkFlexTest/org/osmf/MediaFrameworkTests.as

  • [svn:bz-trunk] 14655: Fix hostname in failing MXUnit proxy service tests.

    Revision: 14655
    Revision: 14655
    Author:   [email protected]
    Date:     2010-03-09 18:41:52 -0800 (Tue, 09 Mar 2010)
    Log Message:
    Fix hostname in failing MXUnit proxy service tests. The hostname flexteam.macromedia.com no longer resolves. Changed the tests to just use flexteam as the hostname. We probably shouldn't have tests that rely on flexteam but we can worry about that later.
    Modified Paths:
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/202863/bug202863Doc Lit.mxml
        blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/202863/bug202863Rpc Enc.mxml

  • [svn:fx-trunk] 5812: Fixed a bug where direct use of Animation failed because AnimationProperty was not setting up its internal keyframes with correct duration information , so the animation would skip immediately to the end.

    Revision: 5812
    Author: [email protected]
    Date: 2009-03-31 11:34:56 -0700 (Tue, 31 Mar 2009)
    Log Message:
    Fixed a bug where direct use of Animation failed because AnimationProperty was not setting up its internal keyframes with correct duration information, so the animation would skip immediately to the end.
    Bugs: SDK-20356
    QE Notes: spark/effects Mustella tests currently hosed, couldn't run test suite
    Doc Notes: None
    Reviewer: Jason
    Testing: checkintests, Mustella effects tests could not be run (post-rename issues)
    Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-20356
    Modified Paths:
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/AnimationProperty.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/animation/Animation.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateColorIns tance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/AnimateShaderTr ansitionInstance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/FadeInstance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/MoveInstance.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/ResizeInstance. as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/Rotate3DInstanc e.as
    flex/sdk/trunk/frameworks/projects/flex4/src/spark/effects/supportClasses/RotateInstance. as

    Hi
    Can you please try setting up full persmission in the security properties for everyone on the wsconfig folder C:\ColdFusion10\config\wsconfig  and restart ColdFusion Server.
    Swaraj

  • [svn:fx-trunk] 11523: Fix return values for ASyncListView/setItemAt(), removeItemAt(): return failed items if they exist.

    Revision: 11523
    Author:   [email protected]
    Date:     2009-11-06 11:58:50 -0800 (Fri, 06 Nov 2009)
    Log Message:
    Fix return values for ASyncListView/setItemAt(),removeItemAt(): return failed items if they exist.
    QE notes:
    Doc notes:
    Bugs: sdk-24078
    Reviewer: Evtim
    Tests run: AsyncListView Mustella tests pass
    Is noteworthy for integration: no
    Ticket Links:
        http://bugs.adobe.com/jira/browse/sdk-24078
    Modified Paths:
        flex/sdk/trunk/frameworks/projects/framework/src/mx/collections/AsyncListView.as

Maybe you are looking for