]
Max Rydahl Andersen commented on JBIDE-19081:
---------------------------------------------
I haven't had time to test this yet - but its free for anyone to do so.
Just run with current parent pom on all the major test suites we have - note the number of
tests ran (failure/errors should not matter here)
Then run with new suggested parent pom and see what the numbers reveal and if any big
difference we'll just need to open issues against those components about what they
need to do to fix it....
Use simpler Surefire include/exclude pattern in parent pom
----------------------------------------------------------
Key: JBIDE-19081
URL:
https://issues.jboss.org/browse/JBIDE-19081
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: build
Affects Versions: 4.3.0.Alpha1
Reporter: Nick Boldt
Assignee: Max Rydahl Andersen
Fix For: 4.3.0.Alpha2
1. In JBDS9, use these new default patterns for Surefire to define which test classes to
run/exclude:
{code}
include = *Test*, *Test, *TestCase
exclude = *Abstract*
{code}
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