Inserting Existing Actions

When you plan a suite of tests, you may realize that each test requires one or more identical activities, such as signing in. Once you have created the action and stored it with one test, you can insert either a call to a copy of the existing action, or a call to the existing action, into other tests.

When you insert a call to a copy of an existing action, you can make changes to the copied action, and your changes will neither affect, nor be affected by, any other test. Calls to existing actions, however, are read-only in the calling test. They can be modified only in the test in which they were stored. Calls to existing actions enable you to call the same action from several tests and make it easy to maintain tests, because when your application changes you only have to update the existing action stored with the original test.

In the following exercises you will create a new test that is similar to the ActionA test, except that the Sign_in and ReturnHome actions are external actions (calls to existing actions stored with other tests) and the FlightOrder action is slightly modified

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