Dividing the Test into Two Actions

Here i explained how to divide the test into two actions. Follow the below steps:

Since your test currently contains two main processes: signing-in and purchasing a flight, it makes sense to divide the test into separate actions.

1.Select the page where you want the second action to begin. In the Keyword View, expand Action1 > Welcome: Mercury Tours.

2.Split the test into two actions.
Select the first Find a Flight: Mercury page and choose Edit > Action > Split Action or click the Split Action button . The Split Action dialog box opens.
3.Enter names and descriptions for the two actions.In the Name box of the 1st action type: Sign_in.

In the Description box of the 1st action, type: Enters user name and password to sign in.

In the Name box of the 2nd action type: FlightOrder.

In the Description box of the 2nd action, type: Chooses and purchases a flight.

Click OK to close the Split Action dialog box and accept the other default selections. The two actions are displayed in the Keyword View.

Choose View > Expand All to examine the contents of each action. Note that the FlightOrder action begins and ends with the Find a Flight: Mercury page.

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