diff options
| author | Peter Andersson <[email protected]> | 2015-11-24 00:11:45 +0100 |
|---|---|---|
| committer | Peter Andersson <[email protected]> | 2015-12-10 15:24:59 +0100 |
| commit | 6d2bac38720ec27763a0cea2ae48060d501fce62 (patch) | |
| tree | 51d5c038e051f67677ec663b6081ca9dee9b068a /lib/common_test/doc/src | |
| parent | 49f56f9dc37499b6ebb365d2304eee940d57801d (diff) | |
| download | otp-6d2bac38720ec27763a0cea2ae48060d501fce62.tar.gz otp-6d2bac38720ec27763a0cea2ae48060d501fce62.tar.bz2 otp-6d2bac38720ec27763a0cea2ae48060d501fce62.zip | |
Let missing suites affect ct:run_test/1 return and ct_run exit status
Diffstat (limited to 'lib/common_test/doc/src')
| -rw-r--r-- | lib/common_test/doc/src/run_test_chapter.xml | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/lib/common_test/doc/src/run_test_chapter.xml b/lib/common_test/doc/src/run_test_chapter.xml index d80453fc98..082a587c8d 100644 --- a/lib/common_test/doc/src/run_test_chapter.xml +++ b/lib/common_test/doc/src/run_test_chapter.xml @@ -60,15 +60,15 @@ <p>If compilation should fail for one or more suites, the compilation errors are printed to tty and the operator is asked if the test run should proceed without the missing suites, or be aborted. If the operator chooses to proceed, - it is noted in the HTML log which tests have missing suites. If Common Test is - unable to prompt the user after compilation failure (if Common Test doesn't - control stdin), the test run will proceed automatically without the missing - suites. This behaviour can however be modified with the - <c><![CDATA[ct_run]]></c> flag <c><![CDATA[-abort_if_missing_suites]]></c>, + it is noted in the HTML log which tests have missing suites. Also, for each failed + compilation, the failed tests counter in the return value of + <c><![CDATA[ct:run_test/1]]></c> is incremented. If Common Test is unable to prompt + the user after compilation failure (if Common Test doesn't control stdin), the test + run will proceed automatically without the missing suites. In order to always + abort the test run (without operator interaction) if one or more suites fail + to compile, the <c><![CDATA[ct_run]]></c> flag <c><![CDATA[-abort_if_missing_suites]]></c>, or the <c><![CDATA[ct:run_test/1]]></c> option - <c><![CDATA[{abort_if_missing_suites,TrueOrFalse}]]></c>. If - <c><![CDATA[abort_if_missing_suites]]></c> is set (to true), the test run - will stop immediately if some suites fail to compile.</p> + <c><![CDATA[{abort_if_missing_suites,true}]]></c> should be set.</p> <p>Any help module (i.e. regular Erlang module with name not ending with "_SUITE") that resides in the same test object directory as a suite |