Building a Scenario is a simple process to select steps one-by-one, to reflect the test flow. Step Selector dropdown presents a filtered list of Relevant Actions that are applicable at a given point in the Scenario flow.
Relevant Actions include the following, at a given step in a Scenario:
- Actions that are available in the page (or Context), where the application will be at this point in the flow
- All the library Actions available in the Project
In addition, you can always insert an Init Action at any point in the flow, to initialize a new browser and create a sub-flow.
You continue selecting a sequence of steps to create the Scenario. When done, press "Esc" on the keyboard.
Selecting Init Action
Init Action is one that a Scenario flow can start with, and typically involves the logic to invoke the browser/mobile device, etc.
When you are adding an Init Action, you can provide values for the parameters that the Init action requires. For example, when you are invoking a browser, provide URL to invoke.
You may either type literal values, or choose an option between Global Properties and Run Properties. Alternatively, you can choose to defer providing the parameter values in a Test Case.
Refer to the Parameter configuration section for further details.
When you are adding Init Action, you are also required to select the page/Context in which the application will land after the URL is loaded.
Capturing application Views while adding Init step
When you are adding an Init step (as described above), you may be selecting an existing Context as the landing page or creating a new one. Typically you create a new Context for the landing page if you are starting on a brand new project or introducing a new application for automation. ACCELQ will prompt and allow you to record Views for this newly created Context. This is an extremely useful step, as you can quickly gather the application assets as part of the Scenario creation itself.
You can start the recorder and capture all the Views relevant for this Scenario, not just the Context selected for the landing page of Init step. Remember the Contexts and Views are reusable assets that may be used across multiple Scenarios.
Selecting an Action with multiple destinations
Sometimes, an Action may have been defined with the possibility of multiple destination contexts (or unspecified destination).
For example, imagine in your test application that after Login, you may be directed either to the Dashboard page or to the Password Expiration page depending on some business rules. In this case, you would define the Login Action with the possibility of multiple destinations (Dashboard page or Password Expiration page).
When you add such a multi-destination Action in a Scenario, you will be required to select one of the Contexts as the specific destination applicable for the flow. For the above example, if this Scenario was about verifying the Password Expiration functionality, you would choose the destination page as the Password Expiration page.
Learn more about multi-destination Actions.
Selecting a step from All Actions tab
When you are building a Scenario, you may also review all available Actions by clicking on All Actions tab in the step-selector. This list also includes all the Init Actions from the project.
You may typically navigate to All Actions either to review available Actions or to insert a new Init step in the middle of the flow, to initialize another application window.
Note: If you select an Action from All Actions tab that is not part of the Relevant list, the system will create a Missing Step alert.
Please sign in to leave a comment.