On 23 Jan 2015, at 12:42, Max Rydahl Andersen
<max.andersen(a)redhat.com> wrote:
So this always been one of the things I disliked about our parent pom. I much rather
prefer run all the test classes automatically.
The reason for the current pattern is historically - that most tests were done via
testsuites instead of individual ones since there was no other good way of grouping
tests.
Problem is we haven't found a good way of moving from the old to the new without
having to go through all the existing test code and ensure the tests are not double
executed.
But right now I think the only one I know that is pro-testsuites being the default is Rob
S. who have just
said he is fine switching to Tests being executed by default - he can just use the
TestSuite pattern in his test projects if he insists :)
One drawback of not having testsuites is though that we loose the ability to easily run a
group of tests from eclipse or maven.
Anyone found a good way of doing that via junit ? (testng has groups but tycho
surefire/junit does not support that afaik)
That said - i'm all for looking at moving to this for Mars builds.
I guess the suggestion is to:
exclude *Abstract*, *Suite* and only include *Test.class, correct ? (Xavier used
*TestCase.class which is a different pattern than the rest afaics)
True, I suffixed my test classes with "TestCase", but I have no reason
to stick with that if everyone else used "Test" and if the parent pom.xml uses
that pattern, too.