An origin context is a context from which the said Action is initiated.
Performing the action of Sign In on the Homepage of a website. In this example Homepage is the Origin Context for the action Sign In.
Destination Context refers to the resulting Context of test application once the Action is performed.
Following situations are possible when an Action is performed:
- Change in Context of the test application
Select appropriate Context name in the destination field.
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.
No change in Context of the application
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 those cases select “Current Context”.
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.
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. “Home Page” or “Current Context”. 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.
Results in closure of the browser
Select “App Exit” as the destination for the Action.