Role of an action in a testcase

Actions are the building blocks of the testcase

An action consists of ordered steps that should be followed to interact with your application.

A testcase is made up of Actions. Each test must have at least one action and may contain multiple actions.

Each action contains one or more steps for a particular process. For example, to log into an application, you may have the following steps:

1. Launch the application.
2. Enter the username.
3. Enter the password.
4. Click OK.

When planning and implementing your test, you can decide to include all steps in one action or to divide the steps into multiple actions. Dividing the steps into multiple actions allows you to modularize the test, have better control over iteration, and reuse these steps in multiple tests (a reusable action). For example, you may have the following testing scenario:

1. Launch and log into the flight application.
2. Create 4 orders.
3. Delete 2 orders.
4. Close the flight application.

It is likely the process to launch and close the application will be repeated in multiple tests. Create separate reusable actions for these. Once created, the reusable actions can be used in multiple tests while only requiring maintenance in one location. The steps to create and delete orders only need to be generated once. If these steps are placed into individual actions, you can use QuickTest Professional’s built-in functionality to control the number of iterations executed within the test. As individual actions, they can also be reused in other tests.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s