ansaurus

Question

Running Eclipse Junit Plugin tests with Junit 4.4 or newer -- why aren't tests detected?

Answer 1

A:

I don't know which version of JUnit it was, but to succesfully find test the test methods name must start with the word "test".

In newer version you can simply mark test with @Test, for me it works in this combination:

import static junit.framework.Assert.*;
...
@Test
    public void testDummy() throws Exception

Drejc 2008-11-04 08:26:46

It was all JUnit versions prior to JUnit 4. This "old style" still works, though.

Urs Reupke 2008-11-04 16:31:28

...and if you look at my test case, it uses both (@Test and a v. <4 naming convention)

rcreswick 2008-11-04 16:40:35

Answer 2

A:

Maybe your JUnit bundle is missing an entry in the MANIFEST.MF:

Dynamic-Import-Package: *

This is mandatory to load classes from other bundles.

Bebbo

2008-11-25 08:05:35

Answer 3

A:

ActivatorTest needs to extend TestCase

shsmurfy 2008-11-25 08:25:50

That is not true in Junit 4+.

2008-12-01 21:30:43

You're absolutely right reppimp, I didn't realize he was using JUnit 4 at the time I posted.

shsmurfy 2008-12-04 05:21:07

Answer 4

+3 A:

I cannot test this right now as I don't have an Eclipse 3.4 installation handy, but I've run across a similar problem a while ago in (I think) IntelliJ IDEA 7.0.x, and a workaround was to explicitly specify a test runner.

With JUnit 4.5:

import org.junit.runners.JUnit4;

@RunWith(JUnit4.class)
public class ActivatorTest {
    //...
}

If this does not work you may have more success with org.junit.runners.BlockJUnit4ClassRunner

For JUnit 4.4 I would try org.junit.internal.runners.JUnit4ClassRunner

EDIT : not too sure about the com.springsource. part as I don't use Springsource. From your question it seems that springsource repackages JUnit under com.springsource.org.junit but you use just org.junit in your code so I'll stick with that.

Thomas Dufour 2008-12-11 08:44:52

The repackaging is just to supply junit as an OSGi bundle. com.springsource.org.junit is just the name of the bundle, and has no relation to the actual packages provide by the bundle (other than the convention that you use <organization>.<library> for the naming.

rcreswick 2008-12-17 18:25:06

I'll try the @RunWith(..) idea next time I have a chance though -- we're just using junit 3.8 for now :(. I have some doubts that changing the test running will work, simply because the tests have to have a very specific plug-in environment to work, and I'm unsure if that includes the test runner.

rcreswick 2008-12-17 18:32:21

Thanks, your solution worked for me!

Maciek 2010-01-07 21:30:25

Answer 5

+1 A:

I'm wondering whether you might need to import the @Test tag from com.springsource.org.junit and not from org.junit.

Volker

ShiDoiSi 2009-01-30 08:03:46

Answer 6

+1 A:

I had some similar sounding problems with jMock, JUnit & Eclipse recently, although admittedly not with plugin tests.

I'm not sure if it's relevant, but I got it all working with the following versions :-

jmock-2.5.1.jar
hamcrest-core-1.1.jar
hamcrest-library-1.1.jar
jmock-junit4-2.5.1.jar

I also found I had to use the JMock test runner like this :-

  import org.junit.Test;
  import org.junit.runner.RunWith;

  import org.jmock.Mockery;
  import org.jmock.Expectations;
  import org.jmock.integration.junit4.JUnit4Mockery;
  import org.jmock.integration.junit4.JMock;

  @RunWith(JMock.class)
  public class PublisherTest {

    Mockery context = new JUnit4Mockery();

    @Test 
    public void oneSubscriberReceivesAMessage() {

floehopper 2009-02-06 23:18:20

Answer 7

A:

@RunWith(Suite.class) @SuiteClasses( { UserServiceTest.class,ABCServiceTest.class })

public class AllTestSuite {

public static Test suite() {

  return new JUnit4TestAdapter(AllTestSuite .class);
 }

}

2009-05-21 10:05:28

Answer 8

A:

I think the spring testing framework is not compatible with junit 4.4+

ssmithstone 2009-05-21 11:25:28

Answer 9

+1 A:

In my experience this happens if the plugin which contains the plugin tests does not depend on junit. After adding the junit 4.4 dependency to my MANIFEST.MF file the error went away and all tests were executed. The junit dependency should be optional because the plugin usually only needs it for the test code.

2009-06-02 12:42:47

Thanks for your answer this is exactly what solved my ptoblem.I struggled with running Junit tests since I expected that Eclipse's "Plugin Junit Test" configuration will add it automatically

Petr Gladkikh 2010-02-04 12:10:01

ansaurus

tags:

views:

answers:

Running Eclipse Junit Plugin tests with Junit 4.4 or newer -- why aren't tests detected?

related questions