When you are testing an application (manually or otherwise), there is a particular order in which different steps are performed to achieve the use case.
Scenario steps are sequenced to reflect the test flow. ACCELQ automatically helps you select the correct sequence of steps based on the defined behavior of your application. This is primarily driven by the Origin and Destination context attributes of Actions involved in the Scenario flow.
If the flow defined in the Scenario does not follow the appropriate sequence, Missing Step alerts are indicated at various places.
At the end of each step in a Scenario, the test flow is in a particular contextual state. You are only allowed to select the next step based on this context.
Start a Scenario with Init step
An Init step is something that invokes your application to begin the test. When you are testing a web-based application, invoking the browser is what is accomplished in this step. By default, ACCELQ provides Init steps for various application types such as Web, Mobile, Terminal Emulator etc. which you can directly use. Apart from this, you can also create your custom Actions and mark them as Init Actions. Learn more about Init Actions here.
The first step in a UI-based Scenario should be an Init step (there may be exceptions, especially if there is a need to perform non-UI logic for setting up the test). You may use system provided Init step or one of the custom-defined Init Actions that you define yourself, but a Scenario should include this step before you insert other steps that interact with the UI.
Sequencing the steps in the flow
Every step you insert in the Scenario must be aligned with the step that was performed just before this step. For example, if the first step in the Scenario was to login to Qbank, then the next step must be from the Account Summary page, where the application would land after the login. As you add steps while building a Scenario, ACCELQ makes it easy by presenting only appropriate steps (Relevant Actions) at every point. If this sequence is broken, a missing-step alert is created in the Scenario.
ACCELQ supports a special class of Actions called Library Actions. When you need Actions that are general-purpose and do not need UI-based logic, you can simply define them as part of a Library Context. Learn more about Library Context/Actions. Library Actions are universally relevant and applicable anywhere in the Scenario flow.