Stop Execution

The Stop Execution action in the Avo Assure is found under the @Generic Element and is used to stop the execution at a specific step and prevents further execution. Its stops execution in the middle of the automation testing when needed.

Syntax

Input Value: <type>(Optional)

Argument	Description
<type> (Optional)	In the Input Value Column only three inputs types are supported: Empty or Scenario Module Level Test Case Level

The inputs are case-insensitive, only the following can be accepted

Empty or Scenario Level: The “Stop Execution” action will stop the scenario’s execution as soon as it’s triggered, preventing any further steps from running.

Module Level: The “Stop Execution action stops the execution of the entire module when its input value is triggered, preventing any further steps within that module from running. (Easy for end-to-end and batch executions).

Test Case Level: The “Stop Execution” action stops the entire Test Case when it appears with the given input value, so no more steps in that testcase will run.

Output Value:

Argument	Description
N/A	Not Applicable

Example:

Stop execution at different levels (Scenario, Module, or Test Case)

The Stop Execution action can take an optional value from the Input Value column (e.g., Scenario Level, Module Level, or Test Case Level). Based on the input, it stops the execution at the specified level. If no input is provided, it defaults to stopping the scenario.

Below is the screenshot for - Scenario Level

Below is the screenshot for - Module level

Below is the screenshot for - Test Case Level