Running and Analyzing a Multi-action Test

You will now run the ActionB test. The entire test will run only once, but the FlightOrder action will run twice; one time for each set of data in the Copy of FlightOrder data sheet.

Run the ActionB test.
Confirm that all Web browsers are closed.

Click Run or choose Automation > 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.

Examine the test results.
Examine the Results Summary. The test is marked as Done. This indicates that the test ran without any failures (there were no checkpoints to "pass").

Expand Test ActionB Summary > ActionB Iteration 1 (Row 1) in the Test Results window. Select the Copy of FlightOrder Summary action in the results tree.

Note that within the summary, the results of both iterations are displayed.
Close the Test Results window.
Choose File > Exit to close the Test Results window.

Comments

Post a Comment

Popular posts from this blog

2.Areas of Deployment

Image
The below figure explains the systematic representation of the areas of deployment for automated testing:It is important to identify what part of the testing processes would be automated. The enterprise application, which are subjected to change either because of maintenance or project go-live, are most suitable for automated testing.
Read more

Setting Actions as Reusable Actions

Reusable actions are like functions in programming. When you have a process that you may need to include in several tests, you record, modify, and enhance the steps of the process and save them in a reusable action. Then you can call the action from other tests, rather than recording, modifying, and enhancing the same steps each time. To call an action from another test, you must make it a reusable action in the test with which it was stored. The Sign_in and ReturnHome action you created in this lesson can apply to almost any test you might create on the Mercury Tours site, so it makes sense to make them reusable actions. Make the Sign_in action reusable. In the Keyword View, right-click the Sign_in action and choose Action Properties. The Action Properties dialog box opens. Select the Reusable action check box and click OK. If a message box is displayed, read the message, click Do not show this dialog box again, and click OK. The action icon changes to a reusable action icon . ...
Read more

Sample QA/Testing Resume

QA Analyst  XXXXX(NAME),QA email@email.com XX Any Street XXXXXX XX 90000 (000) 000-0000 Senior QA Analyst with expertise in all phases of testing for client/server and Web applications SUMMARY OF QUALIFICATIONS Over "X" years of QA experience in all phases of life cycle, including requirements gathering, risk analysis, project planning, scheduling, testing, defect tracking, management, and reporting. Adept at using both manual and automated testing tools to troubleshoot systems, integration, user acceptance, positive and negative, functionality, object, and regression Develop use cases, user interface specifications, and user requirement specification documents. Liaise with developers, business analysts, and user representatives in application design and document reviews. Superior analytical, troubleshooting, communication and presentation skill. TECHNICAL SKILLS Testing Tools : QuickTest Pro, LoadRunner, Test Director, Visual Source Safe, Visual Intercept,...
Read more