Details
-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
None
-
None
-
Undefined
Description
I've done various hacks with profiles to disable running surefire in maven modules outside the testsuite part of the tree when various profiles are activated, e.g. -Dts.ee9, -Dts.bootable, etc. Basic idea being that test jobs using these profiles are not benefiting from running the tests in modules outside of 'testsuite' as those modules gain no additional coverage from such test jobs.
But I've noticed that there are still tests in various clustering modules that run when -Dts.ee9 is used.
Maybe this relates to the use of the build-test-java# files in some modules, as at a glance the tests I saw running seemed to be associated with modules with those files, and I saw nothing in their poms that would specifically defeat the mechanism I set up for disabling surefire.
The mechanism is in a high level pom configure the 'phase' for the 'default-test' surefire execution to be an expression that resolves by default to the standard 'test'. Various profiles can then set that property to 'none' (and set it back to test in parts of the testsuite where that execution should run.)