5. GUI Actions – Part 2

GUI Actions – Part 2

Inserting a call

We can insert a call to

1. New action
2. Existing action
3. Copy of an action

Ways in which we can insert a call

                                                  1. From the Design menu option

2. From the Canvas/Keyword view
3. Record toolbar

Call to COPY of an Action

1. the action is copied in its entirety, including checkpoints, parameterization, and the corresponding action tab in the Data Table into the calling test
2. you can make changes to the copied action, and your changes will not affect nor be affected by any other test
3. You can insert copies of both reusable and non-reusable actions

Call to an EXISTING Action

1. Calls to existing actions are read-only in the calling test
2. can only be modified in the test in which they were created
3. Enables you to use the same action in several tests and makes it easy to maintain tests
4. You can make calls to only "Reusable" actions

LoadAndRunAction statement

We can load and call actions dynamically using the LoadAndRunAction statement.

Syntax - LoadAndRunAction(TestPath, ActionName, [Iteration], [Parameters])

TestPath - Type - Variant - absolute path of the action, ALM path or relative path
ActionName - Type - Variant - Name of the action
Iteration - Type - Variant - default value - one iteration or 0
                                                                   alliterations or 1
                                                                   range of iterations 1-7

Commands to Exit Actions

ExitAction – exits the current action regardless of its iteration attributes

ExitActionIteration – exists the current iteration of the action