You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When your run your unit test with "-l" or "--list-test-names-only", the exit code of the process is the number of tests. This is quite incorrect behavior on any Unix operating system. A non-zero exit code indicates the program could not perform its intended function. It is reasonable for a tool that runs the program to assume that something went wrong with listing tests, and indeed, I'm using Catch in a framework that assumes exactly that. Furthermore, exit codes above 128 are supposed to have special meaning, and the exit code may not exceed 255. See here, for example: https://www.tldp.org/LDP/abs/html/exit-status.html
Please fix this to have the test runner exit 0 if there is, in fact, no error.
Steps to reproduce
Simply build and run any catch unit test with "-l" or "--list-test-names-only".
Extra information
Catch version: v2.4.1
Operating System: Linux
Compiler+version: GCC 5.4
The text was updated successfully, but these errors were encountered:
Previously it returned the sum of listed things because ???. This
was completely useless and in many ways actively counterproductive
because of the success/failure conventions around exit codes.
Closes#1410
Previously it returned the sum of listed things because ???. This
was completely useless and in many ways actively counterproductive
because of the success/failure conventions around exit codes.
Closes#1410
Previously it returned the sum of listed things because ???. This
was completely useless and in many ways actively counterproductive
because of the success/failure conventions around exit codes.
Closes#1410
- don't warn on zero return code of --list-reporters
- previously return code was the number of reporters (catchorg#1410, catchorg#1146)
- as of 2c06ee9 return code is zero on success
Description
When your run your unit test with "-l" or "--list-test-names-only", the exit code of the process is the number of tests. This is quite incorrect behavior on any Unix operating system. A non-zero exit code indicates the program could not perform its intended function. It is reasonable for a tool that runs the program to assume that something went wrong with listing tests, and indeed, I'm using Catch in a framework that assumes exactly that. Furthermore, exit codes above 128 are supposed to have special meaning, and the exit code may not exceed 255. See here, for example:
https://www.tldp.org/LDP/abs/html/exit-status.html
Please fix this to have the test runner exit 0 if there is, in fact, no error.
Steps to reproduce
Simply build and run any catch unit test with "-l" or "--list-test-names-only".
Extra information
The text was updated successfully, but these errors were encountered: