A Scenario in ACCELQ represents the use case you are testing on the application-under-test (AUT). Example Scenarios could be
- Verify Login to QBank
- Verify funds transfer on QBank
- Round-trip booking validation on QTravel site
- Convert Lead to Opportunity etc.
A Scenario comprises a series of “Steps”. Examples of steps in "Verify Login to QBank" Scenario may be:
- Login to QBank
- Verify home page
- Logout from QBank
A Scenario is a use case you are testing, and is made up of series of Steps.
Here is how a Scenario looks like in ACCELQ, which has 4 steps starting with invoking the application in a browser to logging out.
Step is an Action
Each Step in a Scenario is an Action, defined in ACCELQ. Action is a reusable component that includes statements to perform necessary logic.
For example, Login to QBank is an Action that includes logic/statements to enter username and password and click on the Login button.
An Action is a reusable component used across multiple Scenarios in a project. Action becomes a "Step" in a Scenario.
An Action is defined in a Context, called Origin Context. This is the Page/Screen in which this Action can execute. For example, Login to QBank Action may be defined in a Context called "QBank Login Page".
Once the Action is executed, the application may transition to a different page. This is defined as the Destination Context of this Action. For the Login to QBank Action, here are the origin and destination Contexts.
- QBank Login Page is the Origin Context
- Account Summary Page is the Destination Context
An Action is applicable in an Origin Context and leads the application to a Destination Context.
Here is how a simple Action may look like: