Batch test
What is Batch test?
A batch test is a test script that contains call statements to other tests. It opens and executes each test and saves the test results. A test becomes a “batch test” when the user select the Run in batch mode option in the Run category of the General Options dialog box before executing the test. Messages are suppressed for a batch test only if user runs the test using the Verify run mode. If user uses the Update or Debug run mode to run the test, messages are displayed. WinRunner suppresses all pause statements and any halts in the test run resulting from run time errors. If tests contain TSL texit statements, WinRunner interprets these statements differently for a batch test run than for a regular test run. During a regular test run, texit terminates test execution. During a batch test run, texit halts execution of the current test only and control is returned to the batch test.
When the user runs a regular, interactive test, results are stored in a subfolder under the test. If run in batch mode is selected, and then WinRunner saves the results for each (top-level) called test separately in a subfolder under the called test. Additionally, a subfolder is also created for the batch test that contains the results of the entire batch test run, including all called tests.
When a batch test run is completed, user can view information about the events that occurred during the run in the Test Results window. If one of the called tests fails, the batch test is marked as failed. The Test Results window lists all the events that occurred during the batch test run. Each time a test is called, a call_test entry is listed. The details of the call_test entry indicate whether the call statement was successful.
Related posts:
- I don’t like/want to use Procmail to hand mail off to bug_email.pl. What alternatives do I have? You can call bug_email.pl directly from your aliases file,...
Related posts brought to you by Yet Another Related Posts Plugin.