Execution of a scenario is launched by clicking the Start execution button available on top of the scenario window.
Scenarios can be executed in batch. Please visit this step by step guide for further details.
You have the option of selecting if you want your scenarios to run the automated execution in maintenance mode or not. This is controlled by the status you set for your scenario. The maintenance window will be displayed in case of an error during automated execution just as long as your scenario is not in "Ready" status, any other status would get the Task Maintenance window displayed.
Obs: Given that a scenario is a grouping of flows, the error handling mechanism is controlled by the flows' statuses, too. If the scenario maintenance mode is ON, next the flow maintenance mode will be assessed. If we have a scenario with status different than Ready the maintenance mode will be on, but if certain flow in that scenario has status equal to Ready then that specific flow will have the maintenance mode OFF.
Please visit this article to see a full description of the Task Maintenance window and the error handling mechanism.
End execution of scenario
When executing a scenario an additional option is displayed in the Manual and Automated tester’s tray icon which is Exit and stop scenario.
Scenarios executed automatically can be stopped from the Automated Tester options too:
More over, if during scenario execution the Task Maintenance window is prompted an extra button will offer you the option of ending the scenario execution. For extra information regarding the Task Maintenance window please visit this article.
Scenario testing logs
Each scenario execution has an attached log that can be found under the Execution logs section.
Below you may see and example of a Not completed execution.
On the right of the window there are listed the flows and other relevant information. These easy to read logs provide great insight to the execution of the flow and help determine quickly the cause of the errors.
Information presented in the first execution from the image below:
- SAP - Log on: Flow name
- DEFAULT: Iteration name
- Log on: Task name
- Navigate to P_WEBBROWSER: User action
- Type P_BW_USERNAME in bw_username: User action
Not completed action: