maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Elliotte Rusty Harold (Jira)" <j...@apache.org>
Subject [jira] [Updated] (SUREFIRE-778) failIfNoTests=false should not be required when using -Dtest=MyTestClass in multi-module reactor builds
Date Fri, 20 Dec 2019 11:38:00 GMT

     [ https://issues.apache.org/jira/browse/SUREFIRE-778?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Elliotte Rusty Harold updated SUREFIRE-778:
-------------------------------------------
    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/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.



  was:
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://jira.codehaus.org/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.




> failIfNoTests=false should not be required when using -Dtest=MyTestClass in multi-module
reactor builds
> -------------------------------------------------------------------------------------------------------
>
>                 Key: SUREFIRE-778
>                 URL: https://issues.apache.org/jira/browse/SUREFIRE-778
>             Project: Maven Surefire
>          Issue Type: Improvement
>    Affects Versions: 2.10
>            Reporter: Scott Carey
>            Priority: Major
>             Fix For: 3.0
>
>
> 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/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.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Mime
View raw message