This is the implementation for a feature of Configurable Categories

https://github.com/KentBeck/junit/issues/307

You can make a narrow list of tests in your build process according t build process specifics.
See the test CategoriesConfiguredBySystemPropertiesTest.
There the suite accepts almost all platforms, and the system properties suppress some of them.

src/main/java/org/junit/experimental/categories/Categories.java

@@ -25,6 +25,7 @@
  * 
  * Note that, for now, annotating suites with {@code @Category} has no effect.
  * Categories must be annotated on the direct method or class.
+ *
  * <p>
  * Two system properties override categories declared by {@link IncludeCategory}
  * and {@link ExcludeCategory}. Every of these two properties use a comma separated

src/test/java/org/junit/tests/AllTests.java

@@ -78,6 +78,7 @@
 import org.junit.tests.validation.InaccessibleBaseClassTest;
 import org.junit.tests.validation.ValidationTest;
 
+
 // These test files need to be cleaned.  See
 // https://sourceforge.net/pm/task.php?func=detailtask&project_task_id=136507&group_id=15278&group_project_id=51407
 

src/test/java/org/junit/tests/experimental/categories/CategoriesConfiguredBySystemPropertiesTest.java

@@ -21,6 +21,7 @@
 import static org.hamcrest.core.IsEqual.equalTo;
 import static org.hamcrest.core.Is.is;
 
+
 public final class CategoriesConfiguredBySystemPropertiesTest {
 
     private static String convertToFileNames(final Class<?>... types) {