[SUREFIRE-778] failIfNoTests=false should not be required when using -Dtest=MyTestClass in multi-module reactor builds

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.10
• Assignee: Unassigned
• Reporter: Scott Carey
• Created: 18/Oct/11 17:29
• Updated: 16/Aug/22 20:28
• Resolved: 20/Dec/19 11:39

Description

Configure a trivial multi-module build with two tests (TestA, TestB) and two modules, one test in each module.

a multi-module aggregate build will succeed with

'mvn test'

but fail with

'mvn test -Dtest=TestA'

This happens with 2.10, but does not with 2.6 for http://avro.apache.org/ (https://issues.apache.org/jira/browse/AVRO-935)

This is related to bug
http://issues.apache.org/jira/browse/SUREFIRE-464

-Dtest=Foo should not require that every module have a matching Foo, only one needs match. Or to simplify things, don't automatically switch from failIfNoTests=false to failIfNoTests=true when -Dtest= is set at all.

Users who are running one test by hand don't need this behavior (they will notice if the test they are trying to run doesn't run) and automated tools/scripts that use this parameter that want it to fail should set -DfailIfNoTests=true.

Issue Links

• duplicates: SUREFIRE-464 Default for failIfNoTests should be false
• is duplicated by: SUREFIRE-839 If no tests are found that would match a given JUnit category, mvn test should not fail in multi-module project
• relates to: SUREFIRE-806 Make ignoring of <includes> and <excludes> on -Dtest=... optional (for multiple Surefire executions)