Wednesday, August 4, 2010

Calling External Actions as Existing and Copy of Action

1. Actions syntax : RunAction "ActionName",No.ofIterations,IpParameters,OpParameters


2. Returning Value syntax: RetVal=RunAction("ActionName",No.Ofiterations,IpParameters,OpParameters)

3. If we write the Action call syntax directly in test and execute... that reusable action should be available in the same test... if not "Action not found" error will be appeared


call to existing Action

1. If we call the existing action to test all the called existing actions will be in readonly mode even the datatables.

2. If the two actions with same datatable variables (i.e., columns with same name) will be appear as many actions as it contains in read only mode.

3. While executing the external called actions will be used only the data available in their particular action datatables.

4. Only the calling action can use the data available in global as well as all action datatables including the readonly datatables related to the external actions.

5. If you call as many times as you want... it will include the statement for calling the particular existing external action but not the Action again with datatable.



Call to Copy of Actions

1. If we call to copy of action to test all the called external actions will be in editable mode, even the datattables.

2. If the two actions with same datatable variables (i.e., columns with same name) will be appear as many actions as it contains in read only mode.

3. While executing the copy of called actions can be used all the data available in their all global/action datatables just like the own test actions.

4. These called copy of actions are indirectly becomes the own test actions with the script copied from called external actions. so, these can be use all the datatables available in the test

5. If you call as many times as you want... every time it will make a new copy of the total action including the datatables with editable mode.


No comments:

There was an error in this gadget