Adding Steps to Actions QTP

Adding Steps to Your Test Actions

When your actions are ready, you can add steps to them.

Add steps by selecting the keywords (operations) that represent the application functionality you want to test. For more information, see Working with the Keyword View.
You can insert steps in the Keyword View, the Expert View, or a combination of both. You can add steps by dragging test objects from the Available Keywords pane, using the New Step option, using the Step Generator, entering steps manually, and so on. Make sure to fill in any missing values, as needed.
For more information, see Adding a Standard Step to Your Test, Adding Other Types of Steps to Your Test, and Generating Statements in the Expert View or in a Function Library.


Consider enhancing your tests by inserting checkpoint and output value steps to verify that your application is behaving as expected during a run session.
You can insert checkpoints to check for differences in the text strings, objects, and tables in your application. For more information, see Understanding Checkpoints.
You can insert output value steps that retrieve values in your test and store them for use as input values at a different stage in the run session. For more information, see Outputting Values.


Consider data-driving your test to check how your application behaves with different data input during subsequent run sessions. You can also data-drive your test to check how your application behaves during multiple iterations of the same action during a single run session. For more information, see Working with Data Tables.


Consider increasing the power and flexibility of your test by replacing fixed values with parameters, if applicable. When you parameterize your test, you can check how it performs the same operations with multiple sets of data, or from data stored or generated by an external source. For more information, see Parameterizing Values.
Note: If you have useful WinRunner assets, you may want to link to WinRunner tests and call WinRunner TSL functions from your QuickTest test. For more information, see Working with WinRunner.