[svn:bz-trunk] 23085: Fix test to explicitly remove an event listener after the test is finished .

Revision: 23085
Revision: 23085
Author:   [email protected]
Date:     2011-10-21 07:49:33 -0700 (Fri, 21 Oct 2011)
Log Message:
Fix test to explicitly remove an event listener after the test is finished. Not doing this was causing the test to throw an RTE.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/messagingService/security/stream ing-amf/MessagingAuthProSendTest.mxml

Thanks for the ideas regarding beforeInvoke, Ben. I will try to check that out. In my situation, here's essentially how my script is working...
BeforeSave is invoked.
Script makes a change to the document, which should be captured in the saved file.
Document saves.
Document appears saved for a moment, and then appears unsaved (asterisk in the document title).
My biggest problem is that this behavior isn't consistent. I have dozens of users, all running the same script, and the problem only occurs with certain users and at random times. I can move a problematic document from a user's machine to a different machine, and the problem doesn't occur there. It's very difficult to troubleshoot because I can't reproduce it consistently.

Similar Messages

[svn:bz-trunk] 10026: Fixed a bug around handling ping commands while running load-testing-tool against Servlet-based endpoints .

Revision: 10026
Author:   [email protected]
Date:     2009-09-04 10:28:18 -0700 (Fri, 04 Sep 2009)
Log Message:
Fixed a bug around handling ping commands while running load-testing-tool against Servlet-based endpoints.
Modified Paths:
    blazeds/trunk/modules/core/src/flex/messaging/MessageBroker.java

[svn:fx-trunk] 9127: Fixes bug in Slider animation where we would set the actual value during the animation , ignoring any snapInterval setting.

Revision: 9127
Author:   [email protected]
Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
Log Message:
Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
QE notes: None
Doc notes: None
Bugs: SDK-21776
Reviewer: Hans
Tests run: checkintests, Mustella (gumbo/components/Slider)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21776
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

Revision: 9127
Author:   [email protected]
Date:     2009-08-05 17:25:39 -0700 (Wed, 05 Aug 2009)
Log Message:
Fixes bug in Slider animation where we would set the actual value during the animation, ignoring any snapInterval setting. The fix uses the pendingValue property to hold the animated value, which makes the slider look correct, but no actual value update is sent until the animation completes.
QE notes: None
Doc notes: None
Bugs: SDK-21776
Reviewer: Hans
Tests run: checkintests, Mustella (gumbo/components/Slider)
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21776
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/components/supportClasses/Slider.as

[svn:fx-trunk] 6752: * Fixed issues with unconverted Bindable metadata being left in the

Revision: 6752
Author: [email protected]
Date: 2009-05-08 07:40:29 -0700 (Fri, 08 May 2009)
Log Message:

You might need a custom TextArea Skin with different minWidth/Height and
maybe take out the Scroller if you don't want it.

[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] 10641: Fix ambiguous reference error when compiling a performance test.

Revision: 10641
Author:   [email protected]
Date:     2009-09-28 08:44:38 -0700 (Mon, 28 Sep 2009)
Log Message:
Fix ambiguous reference error when compiling a performance test.
Fully qualify mx.events.Requests in generated code for FlexInit.
QE notes: None.
Doc notes: None.
Bugs:
Reviewer:
Tests run: checkintests
Is noteworthy for integration: no.
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/tools/PreLink.java

Start by validating your HTML code. You have numerous code validation errors on line 230 caused by UPPER case tags. XHTML doc types, need lower case tags. After you fix your code errors, republish your page.
HTML Validator - http://validator.w3.org
CSS Validator - http://jigsaw.w3.org/css-validator/
HTML & CSS Tutorials - http://w3schools.com/
Nancy O.
Alt-Web Design & Publishing
Web | Graphics | Print | Media Specialists
www.alt-web.com/
www.twitter.com/altweb
www.alt-web.blogspot.com

[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] 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] 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

[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] 14778: fix the tests by checking all possible return text.

Revision: 14778
Revision: 14778
Author:   [email protected]
Date:     2010-03-16 09:14:53 -0700 (Tue, 16 Mar 2010)
Log Message:
fix the tests by checking all possible return text.
Modified Paths:
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/httpservice/amfchan nel/hs_resultformat.mxml
    blazeds/trunk/qa/apps/qa-regress/testsuites/mxunit/tests/proxyService/httpservice/httpcha nnel/hs_resultformat.mxml

I believe that plugins rely on the libraries being located in a specific location. The installer can place these libraries in the specific location or some other installer can do that. You can create code that scans the library directly to "learn" what packages/libraries are available. Then you would build the path to that VI and open the reference to it.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

[svn:fx-trunk] 6993: * Fixed a duplicate Bindable metadata bug that showed up with

Revision: 6993
Author:   [email protected]
Date:     2009-05-16 23:57:42 -0700 (Sat, 16 May 2009)
Log Message:
Fixed a duplicate Bindable metadata bug that showed up with
describeType().
tests Passed: checkintests
Needs QA: YES, just confirm the bug fix, please.
Needs DOC: NO
Bug fixes: SDK-21133
API Change: NO
Reviewer: Pete F.
Code-level description of changes:
BindableSecondPassEvaluator.java
    Modified moveMetaDataToNewDefinition() to no longer insert the new
    Bindable metadata into the definition's statement list, because
    prepMetaDataNode() already handles this.
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21133
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java

I just noticed that for some reason the project is using an old path to my SVN repository. I recreated it and reimported the project but for some reason Xcode didn't realize that. I'm betting there's some little file somewhere that's causing my problem.

[svn:fx-trunk] 12982: Fix for issue with exposing accessible names for combobox list items

Revision: 12982
Revision: 12982
Author:   [email protected]
Date:     2009-12-15 20:44:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for issue with exposing accessible names for combobox list items
QE notes: none
Doc notes: none
Bugs: n/a
Reviewer: Gordon
Tests run: checkintests
Is noteworthy for integration: no
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ComboBoxAccImpl.as
    flex/sdk/trunk/frameworks/projects/spark/src/spark/accessibility/ListBaseAccImpl.as

Add this to the end of your nav p CSS selector at Line 209 of your HTML file, after 'background-repeat...':
margin-bottom: -2px;
Your nav p will then look like this:
nav p {
          font-size: 90%;
          font-weight: bold;
          color: #FFC;
          background-color: #090;
          text-align: right;
          padding-top: 5px;
          padding-right: 20px;
          padding-bottom: 5px;
          border-bottom-width: 2px;
          border-bottom-style: solid;
          border-bottom-color: #060;
          background-image: url(images/background.png);
          background-repeat: repeat-x;
          margin-bottom: -2px;

[svn:fx-trunk] 10229: Fixes for some transform effects problems.

Revision: 10229
Author:   [email protected]
Date:     2009-09-14 08:43:43 -0700 (Mon, 14 Sep 2009)
Log Message:
Fixes for some transform effects problems.
- We were not animating the postLayout properties in some cases where we should have, effectively pinning the object in place. We now animate those properties whenever applyChangesPostLayout is true.
- A copy/paste error meant that we did not animate the scaleZ property in cases where we should have.
- A problem in the transform code means that using a null transform center is not the same as a transform center which uses the transformX/Y/Z properties of the target object. We now force the creation/use of a transform center in all cases to avoid that problem.
QE notes: This breaks about a dozen tests in the transform effects area, but I believe the new results are correct and the tests/bitmaps should be changed.
Doc notes: None
Bugs: sdk-23177
Reviewer: Hans
Tests run: checkintests, Mustella transform effects
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-23177
Modified Paths:
    flex/sdk/trunk/frameworks/projects/spark/src/spark/effects/AnimateTransform.as

[svn:bz-trunk] 23085: Fix test to explicitly remove an event listener after the test is finished .

Similar Messages

Maybe you are looking for