mvn test in gwt-lib packaging does not run test cases about gwt-maven-plugin

[tbroyer]

Actually, gwt:test defaults to running test suites, rather than test cases (see https://tbroyer.github.io/gwt-maven-plugin/test-mojo.html#includes). Given the perf gains, I set it as the default to enforce (or at least incentivize to) the “best practice”: http://www.gwtproject.org/doc/latest/DevGuideTesting.html#DevGuideJUnitSuites

NB: I should settle on a channel for such questions; the issue tracker is OK for now, as well as StackOverflow (I monitor the gwt tag) or the GWT forums on Google Group.

[dnouls]

Thanks, that did it

[rjeeb]

@tbroyer is this applied on Junit 5 too?

Update:

adding this to gwt-maven-plugin fixes the problem

<executions>
    <execution>
        <goals>
            <goal>test</goal>
        </goals>
        <configuration>
            <includes>
                <include>**/*Test.java</include>
            </includes>
        </configuration>
    </execution>
</executions>

[tbroyer]

GWT only supports JUnit 3 kind of tests (JUnit 4 to some extent, though actually only for the @RunWith(Suite.class)).

Please note that if you have a shared library (both client/GWT and JVM), you shouldn't use a gwt-lib; you should have a jar for the server and a gwt-lib that works as an adapter: see https://tbroyer.github.io/gwt-maven-plugin/
(if you find that verbose, remember that you're using Maven)