➤ Running and Analyzing a Parameterized Test
You will now run the modified Parameter test. QuickTest will run the test three times, once for each departure city in the Data Table. Each test run is called an iteration.
1 Run the Parameter test.
Click Run on the Testing toolbar or choose Test > Run. The Run dialog box opens.
Select New run results folder and accept the default results folder name.
Click OK. When the test run is completed, the Test Results window opens.
2 Examine the results summary.
The Test Results window shows that the second and third iterations of the test failed, even though the text checkpoint passed in all three iterations.
See below for further information about why the iterations failed.
➤ Iteration 2:
In the results tree, expand (+) Parameter Iteration 2 > Action1 Summary
> Welcome Mercury Tours > Flight Confirmation: Mercury.
1 Run the Parameter test.
Click Run on the Testing toolbar or choose Test > Run. The Run dialog box opens.
Select New run results folder and accept the default results folder name.
Click OK. When the test run is completed, the Test Results window opens.
2 Examine the results summary.
The Test Results window shows that the second and third iterations of the test failed, even though the text checkpoint passed in all three iterations.
See below for further information about why the iterations failed.
➤ Iteration 2:
In the results tree, expand (+) Parameter Iteration 2 > Action1 Summary
> Welcome Mercury Tours > Flight Confirmation: Mercury.
Highlight Checkpoint "New York".
The checkpoint results in the Details pane show that Portland was the expected result and the actual result. Therefore, the checkpoint passed.
You can also see, in the Application pane, that the flight information reflects the flight from Portland.
➤ Iteration 3:
In the results tree, expand (+) Parameter Iteration 3 > Action1 Summary > Welcome Mercury Tours > Flight Confirmation: Mercury.
Highlight Checkpoint "New York".
The checkpoint results in the Details pane show that Seattle was the expected result and the actual result. Therefore, the checkpoint passed.
The Application pane shows the flight information for the flight from Seattle.
The table below summarizes the results of the text checkpoint in each iteration:
The checkpoint results in the Details pane show that Portland was the expected result and the actual result. Therefore, the checkpoint passed.
You can also see, in the Application pane, that the flight information reflects the flight from Portland.
➤ Iteration 3:
In the results tree, expand (+) Parameter Iteration 3 > Action1 Summary > Welcome Mercury Tours > Flight Confirmation: Mercury.
Highlight Checkpoint "New York".
The checkpoint results in the Details pane show that Seattle was the expected result and the actual result. Therefore, the checkpoint passed.
The Application pane shows the flight information for the flight from Seattle.
The table below summarizes the results of the text checkpoint in each iteration:
Note: Although the text checkpoints passed in all three iterations, the second and third iterations of the test still failed because the table checkpoint failed in these iterations—the ticket price changed when the departure city changed. In the next lesson, you will modify the table checkpoint so that when you run your test, QuickTest will update the expected ticket price in the checkpoint with the correct ticket price for the current departure city.
3 Close the Test Results window.
Choose File > Exit to close the Test Results window.
3 Close the Test Results window.
Choose File > Exit to close the Test Results window.
No comments:
Post a Comment