DO NOT REPLY [Bug 34824] - [beanutils] test.wrap.dynabean fails because testSetIndexedValues runs before testGetIndexedValues

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

DO NOT REPLY [Bug 34824] - [beanutils] test.wrap.dynabean fails because testSetIndexedValues runs before testGetIndexedValues

Bugzilla from bugzilla@apache.org
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG?
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=34824>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND?
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=34824





------- Additional Comments From [hidden email]  2005-05-28 01:48 -------
I was surprised by this as the setUp() / tearDown() methods run before every
test and whatever order they're executed, the tests should always start in the
same "state".

Turns out that "listIndexed" was defined as a static variable in TestBean , so
that even though a new TestBean is being instantiated in the setUp() method of
WrapDynaBeanTestCase, being static meant that it wasn't re-initialized -
causing the order then to matter.

I have modified TestBean so that "listIndexed" is now an instance variable.
Could you please give it a test with jikes/kaffe to confirm that this has
resolved the issue?

--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]