Does Parameterized JUnit test correct with `mvn test`?

Question

I'm just implemented a JUnit test case using JUnit 4.11 following the example:

https://github.com/junit-team/junit/blob/master/doc/ReleaseNotes4.11.md#example-1

I create a maven project using

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">

    <modelVersion>4.0.0</modelVersion>
    <groupId>com.yyt</groupId>
    <artifactId>example</artifactId>
    <version>0.0.1-SNAPSHOT</version>

    <dependencies>
        <dependency>
            <groupId>junit</groupId>
            <artifactId>junit</artifactId>
            <version>4.11</version>
            <scope>test</scope>
        </dependency>         
    </dependencies>

</project>

And this test case:

import java.util.Arrays;

import org.junit.Assert;
import org.junit.Test;
import org.junit.runner.RunWith;
import org.junit.runners.Parameterized;
import org.junit.runners.Parameterized.Parameters;

@RunWith(Parameterized.class)
public class Example {

    @Parameters(name = "{index}: fib({0})={1}")
      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 input;
    private int expected;

    public Example(int input, int expected) {
      this.input = input;
      this.expected = expected;
    }

    @Test
      public void test() {
      }
}

But when I test it using mvn test , maven said:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
There are no tests to run.

How to make it work?

please supply more info, the pom, your project structure etc. — emesx, Mar 01 '13 at 14:21
Well, do you actually have any tests to run? They should be in the relative folder `src/test/java`, under your project root. — Perception, Mar 01 '13 at 14:24
@khmarbaise you're right, I renamed `Example.java` to `ExampleTest.java` and this works! — jackalope, Mar 01 '13 at 14:45

score 10 · Accepted Answer · answered Mar 01 '13 at 15:16

10

The problem is the naming convention of maven which is based on maven-surefire-plugin which needs a naming like Test.java, Test.java or TestCase*.java for unit tests. For integration tests the maven-failsafe-plugin is responsible which has the naming convention IT*.java, *IT.java or *ITCase.java.

answered Mar 01 '13 at 15:16

khmarbaise

92,914
28
189
235

Currently, this behavior is documented at http://maven.apache.org/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html – user7610 Dec 02 '17 at 10:47

score 2 · Answer 2 · answered Sep 27 '16 at 16:00

2

Got stuck on the same problem. Found this (still) open issue in junit https://github.com/junit-team/junit4/issues/664. So, there is no way to make it work now.

answered Sep 27 '16 at 16:00

artkoshelev

872
7
22

score 1 · Answer 3 · answered Aug 26 '13 at 18:37

@khmarbaise nailed it in this case, but...

On occasion you ventured here because

Maven and Eclipse both tell you you have no tests in your class
you clearly do; and well-named
both tools seem to find the right class and try to execute tests there
you're starting to doubt if Maven and Parameterized work at all together and the title of this question sounds promising

Your Maven output should state something along these lines if related conditions listed above are met:

-------------------------------------------------------
 T E S T S
-------------------------------------------------------
Running your.maven.properly.named.SomeTest
Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 7.684 sec

Results :

Tests run: 0, Failures: 0, Errors: 0, Skipped: 0

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] No tests were executed!  (Set -DfailIfNoTests=false to ignore this error.)

if it does, my suggestion is: try looking if whatever you use to get data actually returns anything. In other words: take a look at method annotated with @Parameters. Your tests won't run without data.

dsd · Answer 4 · 2021-06-10T13:27:03.590

0

the only solution i know - is to run a whole class, not a test in class.

ex that works:

mvn clean -Dtest=ExampleClassTest test

ex that doesnt work:

mvn clean -Dtest=ExampleClassTest#test test

but be careful, all tests in the class will run with the parameters!

edited Jun 10 '21 at 13:27

answered Jun 10 '21 at 13:01

dsd

1
2

Does Parameterized JUnit test correct with `mvn test`?

4 Answers4

Linked