"[EMAIL PROTECTED]" wrote : | Also, another change to the default JUnit test case behavior is that there will NOT be a new instance of the server test created when it moves to the next test method. This is due to not knowing where the clients will be in their test run, so can't tear down a server test case instance and build up a new one just to run a new test method. |
So strike this. Going to be close to impossible to do this without rewriting JUnit. The TestSuite's private method addTestMethods() calls on public static method createTest() which will contruct a new TestCase instance and set the test method on it and puts in a collection for each test method. This collection is iterated at a later point and runs each TestCase (as a seperate instance). So will just doument the hell out of server test case saying that if have more than one test method, will have more than one instance of the server created. Imagine this will reduce mis-use by about 10%. ;) View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3874160#3874160 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3874160 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-Development mailing list JBoss-Development@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-development
