forked from testng-team/testng
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Configure TestNG to fail when all tests are skipped
Closes testng-team#217 Currently TestNG doesn’t throw an exception which build tools can leverage to fail a build, when all the “@test” methods get skipped and nothing was run. TestNG returns the proper status, but sometimes build tools may not be reading that status and take appropriate action. Introduced a new configuration through this PR using which a user can instruct TestNG itself to trigger an exception when no tests were executed. If one is using surefire plugin, then your surefire plugin configuration would look like below: <configuration> <properties> <property> <name>failwheneverythingskipped</name> <value>true</value> </property> </properties> </configuration> If you are using command line, then this feature can be turned on by passing -failwheneverythingskipped=true
- Loading branch information
1 parent
d480811
commit c3b61f8
Showing
4 changed files
with
50 additions
and
10 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters