jUnit: Generic test class - setting test name to something else than class/method name?

Question

I have a project testsuite with a set of files which I want to use as a testsuite - one test per file.

But the number of tests will go to hundreds, and each tests is the same: Parse the file and check the output. Maintaining a method per each file is tedious.

The JBoss Operation Network used TestNG which allowed to create a test suite, and stuff it with several instances of the same class, and allowing to explicitly set the test name.

In jUnit, I haven't found a way to change the test name. So it would be the same for all.

Is there some way or extension to run the same class multiple times with custom resulting test name?

PS: I'd prefer not to resort to class instrumentation.

Yogendra Singh · Accepted Answer · 2012-10-18T19:32:04.687

4

When you create TestSuite, you can pass desiredTestCaseName as constructor argument:

public class AllTestSuite extends TestSuite{

  public static Test suite() {
      TestSuite suite= new TestSuite();
      Test testCase1 = new MyTest("TestCaseOne");
      Test testCase2 = new MyTest("TestCaseTwo");
      suite.addTest(testCase1);
      suite.addTest(testCase2);
      return suite;
  }
}

When you run the suite, it will refer the names supplied in constructor i.e. TestCaseOne and TestCaseTwo while test class is MyTest.

EDIT:

Please make sure you have defined the constructor in MyTest class as:

public MyTest(String name) {
    super(name);
}

If additional parameters support is desired, you can add an constructor in Test case to accept the parameters and assign them to test case class variables(initially defaulted with default test scenario values), which can be used during test execution:

public MyTest(String name, String param1, Integer param2...) {
    super(name);
    this.param1 = param1;
    this.param2 = param2;
}

Once you run your test suite, JUnit Console looks like screen below: enter image description here

edited Oct 18 '12 at 19:32

answered Oct 18 '12 at 03:02

Yogendra Singh

33,927
6
63
73

I'm not sure how a constructor param of my class would make this happen. Is there any docs? – Ondra Žižka Oct 18 '12 at 03:08
Ah, I should be adding TestSuite objects to the root TestSuite, right? – Ondra Žižka Oct 18 '12 at 03:10
Try it out and check the JUnit Runner: Test Case listing. – Yogendra Singh Oct 18 '12 at 03:13
Yes. I updated the answer with full sample code. If you think, this is helpful, please don't forget to accept the answer. – Yogendra Singh Oct 18 '12 at 03:16
Doesn't work. MyTest("foo"), as I expected, simply ignores the param, and JUnit doen't magically get renamed. Also, the only way to run the testsuite I found was to use `@Suite`, which only has SuiteClasses({...}). Can you pls point me to some working example? – Ondra Žižka Oct 18 '12 at 17:21
I Put some more details in the answer. Please let me know, if you are looking for something else? – Yogendra Singh Oct 18 '12 at 17:36
Ok, it took me a while as the testsuite had some desing issues (like initialization in `static {...}` etc, but finally I made it work. Thanks. – Ondra Žižka Oct 22 '12 at 05:36

score 3 · Answer 2 · answered Oct 18 '12 at 12:20

If you're using JUnit4, you can look at @Parameterized. The basic idea is that you provide a list of things to do, and JUnit executes the same test method for each item in the list.

With version 4.10, the naming isn't too great, you get 0, 1, 2... as names, but with 4.11-beta-1 (which should come out of beta soon), you can get a better naming scheme, because you can specify the name. See the javadoc at the top of @Parameterized.

@RunWith(Parameterized.class)
public class FibonacciTest {
    @Parameters(name= "{index}: fib({0})={1}") // we specify the name here
    public static Iterable<Object[]> data() {
        return Arrays.asList(new Object[][] { { 0, 0 }, { 1, 1 }, { 2, 1 },
                { 3, 2 }, { 4, 3 }, { 5, 5 }, { 6, 8 } });
    }

    private int fInput;

    private int fExpected;

    public FibonacciTest(int input, int expected) {
        fInput= input;
        fExpected= expected;
    }

    @Test
    public void test() {
        assertEquals(fExpected, Fibonacci.compute(fInput));
    }
}

In the above, you end up with names such as

fib(0)=0
fib(1)=1
fib(2)=1

etc.

Parametrized is nice, but the method has to be static. I intended to have this class extendable as there are multiple sets of files with slightly different settings for the project, and I'd have a class for each. Is that possible somehow? — Ondra Žižka, Oct 18 '12 at 17:31

jUnit: Generic test class - setting test name to something else than class/method name?

2 Answers2