QTP Training
| QTP - Actions | |||||
GAReddy
| ||||||
| What - Actions
Actions are the logical units that divide the test into independent blocks
Actions can be divided into logical sections, like the main sections of a transaction, or by specific business processes.
When you create a new test, it contains one action. By dividing your tests into multiple actions, you can design more modular and efficient tests.
Actions help divide your test into logical units
Why - Actions
o Makes code reusable.
o Scripts are easy to maintain.
o Scripts are efficient.
o Saves development time..
Actions – Types of Actions
It’s a good idea to use Web Layout view (on the View menu, click Web Layout) when creating your newsletter. That’s the look your customers will be seeing when they receive your e-mail.
| |||||
| Actions – More Info
o Inserting Actions :
o You can insert an existing action by inserting copy of the action into your test, or by inserting a call to the original action.
o QTP > Insert > Actions
o Call to New Action , Call to Copy of Action , Call to Existing Action
o Nesting Actions:
o Sometimes you may want to run an action within an action.
o This is called nesting.
o Splitting Actions:
o You can split an existing action into two sibling actions or into parent-child nested actions.
o QTP > Edit > Actions > Split Actions
o Select the position from where you want to split the action
Call to New Action
Each time while we create a new action a New Action is created and more over we can convert this action into either a Reusable Action or a Non Reusable Action.
QTP > Insert > Actions > Call to New Action
Call to Copy of Action
A Call to Copy of Action :
(1) In the copy of actions we can change the script; we can edit anything that can be applicable to the current test.
(2) The changes which are made to the copy of actions will not be reflected in the main action tests where they are referenced from.
(3) The changes which are made to the copy of actions will be reflected current tests where they are reused as copy of actions (and the changes are not reflected on the main action/test)
Call to Existing Action
A Call to Existing Action :
(1) In the existing actions we cannot change the script, we cannot edit anything.
(2) The changes which are made to the main action test, will be reflected in the existing action tests where they are referenced to.
Actions - Parameterization
Actions – Parameterization – How To
o Declare Variables in Actions - Parameters Tab
o Choose Parameters type
§ Input Parameters
§ Output Parameters
o Use keyword - Parameter in script
o Parameter(“VariableName”)
o Reuse the actions and pass the parameters
o RunAction <Action> Iteration, Var1,Var2..
Actions - Miscellaneous
o Setting Action Properties
o Sharing Action Information
o Exiting an Action
o Removing Actions from a Test
o Renaming Actions
o Creating an Action Template
o How To - ActionTemplate
Actions – Action Driven Framework
o What is Framework
o Global OR
o Local OR
o Framework Structure
o Framework Process
o Framework Implementation
Actions – Lab - Practical
o W/ H forms of Actions
o Creating Actions
o Reusable / Non Reusable actions
o Action Driven Framework Implementation
o Global / Local OR
o Actions Parameterization
| |||||
0 comments:
Post a Comment