Sangeetha

• May 15th, 2006

 

Hi,

Eternal Actions in QTP are actions that can be called from other tests but cannot be modified inside the test that they are called.

But Reusable actions are actions that can be called from other tests and ALSO can be modified inside the test that they are called.

Thanks.

dileepdon

 Profile Answers by dileepdon 

• Jun 11th, 2006

 

The actions called from another test script will be treated as External Action and these are Readonly actions.

These actions contains Internal links with the source actions

Nikhil

• Nov 21st, 2007

 

Reusable Actions:-  Reusable Actions are those which are called from within the current Test.

External Actions:- External Actions are those which are called from External Test and these Actions are Read-only.

manymore

 Profile Answers by manymore 

• Dec 24th, 2010

 

First of all let's know, why we need all these actions?
When we record scripts for end to end scenarios the script will be
duplicated
For ex: in a banking application the task it to withdraw

Here scenarios will be 1> login 2>check balance 3>withdraw 4> check balance 5> logout if we consider positive flow.
When we write script and run in one action file for all these 5 scenarios it will not be clear. in-order to optimize the script we can create an action file for each scenario, make them reusable and call these reusable actions to an external action (driver)
>General (or) non-reusable actions will contain script for each scenario.

After writing or recording this script we can save them in a test file
>We can change them as reusable actions
>Then we can call them to an external action (or) driver by attaching the test file and the reusable actions that we want to perform

We can not edit the script in the reusable action
If at all we need to edit we can change it in the normal action.
Once after calling all these reusable actions to an external action or driver
Script looks simple and optimized.

manymore

 Profile Answers by manymore 

• Dec 24th, 2010

 

And this will be used when we go for regression testing, where in when there module is rectified in order to check the functionality of the module related to the particular module we will use these actions.