Nothing stops you from creating a suite of suites:
@RunWith(Suite.class)
@SuiteClasses({ com.package1.MySuiteA.class,
com.package2.MySuiteB.class })
public class RunAllTests {
}
Reference: Launch Suite classes using Another Suite class (in English)
On the other hand, the fact that you’re trying to group Suites shoots my Spider-sense. Do you really need suites of suites? What is your goal?
Maybe you are looking to divide your tests according to some criteria:
- To categorize tests (e.g., fast and slow) and choose which ones you want to include / delete from a Suite from a look at the functionality of Categories (in English).
- If you want to run tests as determined profile of Maven, the functionality of Categories goes very well with the functionality of profiles. For more information see the article Using Junit @Category and Maven profiles to get stable test suites (in English).
If you give more details about the problem you are trying to solve I will be happy to help you with further suggestions.
I thought that just by scoring as solved you already earned the points. [=
– uaiHebert