catchorg/Catch2
1
0
Fork 1
mirror of https://github.com/catchorg/Catch2.git synced 2025-08-15 10:31:16 +02:00
Code Issues Packages Projects Releases Wiki Activity

Added --abort

philsquared
2012-06-02 15:27:14 -07:00
parent 09b185e7c4
commit ce4b0b0018
1 changed files with 10 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
Command-line.md

@@ -60,6 +60,16 @@ In addition to the command line option, ensure you have built your code with the
Usually you only want to see reporting for failed tests. Sometimes it's useful to see *all* the output (especially when you don't trust that that test you just added worked first time!). Usually you only want to see reporting for failed tests. Sometimes it's useful to see *all* the output (especially when you don't trust that that test you just added worked first time!).
To see successul, as well as failing, test results just pass this option. To see successul, as well as failing, test results just pass this option.
## Aborting after a certain number of failures
<pre>
-a, --abort [&lt;failure threshold>]
</pre>
If a REQUIRE assertion fails the test case aborts, but subsequent test cases are still run.
If a CHECK assertion fails even the current test case is not aborted.
Sometimes this results in a flood of failure messages and you'd rather just see the first few. Specifying -a or --abort on its own will abort the whole test run on the first failed assertion of any kind. Following it with a number causes it to abort after that number of assertion failures.
## Listing available tests or reporters ## Listing available tests or reporters
<pre> <pre>
-l, --list [tests | reporters] [xml] -l, --list [tests | reporters] [xml]