Defining Destination Context for an Action

Feature Availability        accelQ 3.0 and above

Destination Context refers to the resulting Context of test application once the Action is performed. 

Following situations are possible when an Action is performed:

1. Specific Context
Choose this option if the performance of the action always navigates the application to a specific (fixed) context.

Example:
You may land in “User Home Page” after the user performs “Login" in the “Login Page”. In this case, “User Home Page” is the Destination Context of Login Action.

2. Current Context
In some cases you may find that the Action performed doesn't change the context and it resolves to the context on which the Action is performed. In cases like these,  select “Current Context” for Destination.

Most commonly, Validation Actions do not alter the state of a context.

There is an important distinction to consider while choosing Destination Context, to use Current Context vs. explicitly providing the name of the Context on which the Action is defined.

Example:
If you perform an Action in the Home Page which does not move your Application to a different Context, you have two choices for the Destination. Choose "Specific Context" and provide “Home Page” as the name of the Context, or choose “Current Context” as the option.

When the Actions is shared across multiple Contexts, it may be called from any of the Sharee Context in the Scenario. In such cases, “Current Context” resolves to the actual Context on which the Action is exercised in the Scenario workflow. If you select “Home Page”, then the destination is hard coded to this in all situations. Depending on the Action behavior, one of these two choices must be carefully selected.

3. Multiple Destination Contexts

Choose this option if the performance of the action could navigate the application to more than one possible context under different situations. This is very common when defining reusable navigation-type actions, which could take the application to different pages based on the navigation item. Also common for actions performed in modal type of pages. 

Another common situation you can use this is for negative testing. Login Action could either take you to a User Home Page (upon success) or leave the user in the same Login Page (in case of invalid credentials). You can define the Login Action to have 2 possible destinations. This will allow you to build Scenarios applicable for both happy path and negative scenario with Login.

Note: You can set multiple destination contexts for an Action by clicking on the "Destination Context" field in the Action sidebar. You cannot set this in the Action modal during creation.

4. Unspecified

Use this option sparingly. Choose this option only if you are not sure of which context the action would lead the application to. When using such Actions in a Scenario, no constraints are placed on the applicability of next steps in the Scenario.