This content has been marked as final.
Show 3 replies
-
1. Re: refactor tests using INVM acceptors/connectors
jmesnil Feb 24, 2009 9:09 AM (in response to jmesnil)I'll also add clearing the InVMRegistry in the setUp() of UnitTestCase
-
2. Re: refactor tests using INVM acceptors/connectors
clebert.suconic Feb 24, 2009 10:04 AM (in response to jmesnil)"jmesnil" wrote:
I'll also add clearing the InVMRegistry in the setUp() of UnitTestCase
don' t we have tests that share a server start?
Also: we have lots of tests where tearDown is not calling its super method. -
3. Re: refactor tests using INVM acceptors/connectors
jmesnil Feb 24, 2009 10:47 AM (in response to jmesnil)"clebert.suconic@jboss.com" wrote:
don' t we have tests that share a server start?
I'm not aware of any such test. Do you have an example?"clebert.suconic@jboss.com" wrote:
Also: we have lots of tests where tearDown is not calling its super method.
Yes, I'm fixing it when I see setUp/tearDown w/o the call to the super methods.
The idea is to prevent all the cascading failures asap.
I've got a regression in the failover tests and it is impossible to check what's going on with all the noisy cascading failures