When I create a test suite the tests are runned twice, once independenly and in suite. [mvn test]

[sveridovd]

How to solve that problem, that tests that are grouped in suite, only will be runned in suite, not independently?

[marcphilipp]

One common solution is to use a naming pattern. For example, call all suites *Suite and all tests *Tests and configure Maven Surefire to only include the former.

[laeubi]

I like to add something here and even as what @marcphilipp suggests here "solves" the issue this is not very straight forward/convenient from a users point of view:

1. This naming patterns are a constant confusing for users, e.g. if I run tests usually from the IDE there is no such restriction, then one (maybe even much later) notice that tests are never executed on the CI and regressions slipped in unnoticed
2. That junit can scann the class-path is really great and that's again something similar to whats from the IDE is well know, just select a folder or project chose run and your are done
3. Its a bit strange that a tool should not be able to make a simple filtering of duplicates, as these classes are literally the same, the are from the same project and even referencing each other (at least uni-directional)

So to summarize, it would really be great if JUnit would sort that out without any extra configuration and naming schemes.