JUnit 3 integration fails to link tests to source files

[Google Code Exporter]

When a instinct JUnit 3 suite runs and the results are show in say an IDE
results window, double clicking on the test (specification) do not take you
to the Specification source method but rather to the SpecificationTestCase
class.  This is of course because our SpecificationMethods are wrapped
inside a SpecificationTestCase and the IDE (or JUnit) believes the
SpecificationTestCase holds the actual test methods.

The JUnit 4 integration works fine however, because (it has a much better
architecture!) it has a Description class of which we with the declaring
context class.

Original issue reported on code.google.com by [e-mail] on 10 Aug 2007 at 3:01

[Google Code Exporter]

My initial thought is this may be impossible to fix without an IDE plugin.

Original comment by [e-mail] on 10 Aug 2007 at 3:06

[Google Code Exporter]

Correction - should read: it has a Description class of which we *build* with 
the
declaring context class.

Original comment by [e-mail] on 11 Aug 2007 at 9:16

[Google Code Exporter]

Chris, I'm going to strike this one off. We'll just assume JUnit 4 integration 
I think.

Original comment by [e-mail] on 15 Nov 2007 at 10:08

• Changed state: WontFix