views:

366

answers:

1

Language is Java. Using JUnit4.1 jar, and jMock1.1 but still using JUnit3 style definitions.

Test classes extend MockObjectTestCase (which eventually extends JUnit's TestCase).

If I open a test class with more than one test, then right-click in outline view and select run, it runs that one test, then it runs all the other tests in Unrooted Tests.

3.1 would only run the one test requested, and this is very annoying.

Has anyone else experienced this, and determined how to get 3.3 to behave correctly?

EDIT: Thank you Paul C. The link to nabble in the other question does explain somewhat what the problem is. i.e. a test that extends TestCase in some manner doesn't get handled correctly in Eclipse 3.3, so the answer appears to be refactor to use the @Test approach.

Next 'question'. I'm using JMock1.1, so my test classes actually extend MockObjectTestCase. I guess the answer there is to upgrade jMock to 2.5, which uses annotations, and again shouldn't have problems.

+2  A: 

See this question.

Paul Croarkin