TestPlan Execution Options
Aus ExpeccoWiki
Inhaltsverzeichnis |
Test Execution Options
In the TestPlan editor, a number of execution options are available:
Pre Execution
An optional activity (block) to be executed BEFORE the testplan is executed. Typically, this can be a setup block, or a block which notifies an operator, that some manual installation has to be done (such as: "Please plug in cable XXX"). It could even send an email, and wait for response.
If the pre-execution block fails (i.e. reports FAIL or ERROR), the testplan is not executed.
Post Execution
An optional activity (block) to be executed AFTER the testplan is executed, but only if the pre-execution block is either absent, or it did not fail. Typically, this can be a cleanup block, or a block which notifies an operator, that some manual deinstallation action has to be done (such as: "Please remove cable XXX").
If a post-execution block is present, and it returns non-SUCCESS, that status will be reported as the testplans overall status.
Run Time Limit
You can specify that the test execution should stop after that time duration. If not looping, the remaining testcases will not be executed if the time limit is reached. If looping, the execution of any remaining testcases is controlled by the "Finish testplan even if Time Limit Reached" flag setting.
In addition to this "Testplan"-flag, you can also specify runtime-limits for each individual testcase.
Loop
Specify that the testplans testcases should be repeated until a special condition arises:
- Stop on FAIL or ERROR
- Stop on SUCCESS
In addition, a loop count limit can be specified.
If the above runtime-limit is non-empty, the loop will also stop, if the time has passed. However, in this situation, the "finish testplan even if time limit reached" allows for the remaining testcases to be still executed (i.e. to complete the testplan). If that flag is unchecked, the loop and the testplan will stop immediately, and the remaining testcases will not be executed.
The various loop flags allow for a number of combinations. The "Loop Forever" (loop checked, stop on X unchecked, loop count empty, time limit empty) is only allowed when the testplan is executed interactively (i.e. not, if the test was started via expeccoNET). This mode of operation makes sense for demonstration purposes, or to generate load to a SUT for a stress-test (and maybe monitor its performance using another instrument or another expecco at the same time).
Stop between Loop Cycles
Useful for demonstrations or if manual user interaction is required after each cycle.
Stop between individual Tests
Useful for demonstrations or if manual user interaction is required after each testcase.
Stop on Non-Success
Controls if the remaining testcases should be executed or skipped, when a required testcase is non-successful. Execution is always continued, if a testcase which has been marked as optional is non-successful.
Re-Execute Failed Tests
There are two "Run"-Buttons: one which executes all checked testcases of the testplan, the other only re-executes testcases which failed in the previous run(s).
Test Groups and Risk Classes
In addition to the check-boxes which enable/disable individual testcases, there are also filters to select particular test groups by tag or by risk-class.
Back to Online Documentation
