1. In JBDS9, use these new default patterns for Surefire to define which test classes to run/exclude:
include = *Test*, *Test, *TestCase exclude = *Abstract*
2. If that causes test failures because running incorrectly named
abstract stuff, they can refactor, add their own root pom overrides, use
a TestSuite, or use @Ignore in test classes.
3. If the count of tests run suddenly DROPS because the pattern isn't
running the correct # of tests, they can add their own root pom
overrides, or use a TestSuite.
Ref: http://lists.jboss.org/pipermail/jbosstools-dev/2015-January/009688.html
- is cloned by
-
JBIDE-22739 Use simpler Surefire include/exclude pattern in root poms
- Closed
- is related to
-
JBIDE-24968 VersionProviderTest.testFallBackEmbeddedValues is failing
- Closed
- relates to
-
JBIDE-22449 Better parse qualifiers for versions
- Closed