Stop Execution

This is a pre-built Action located under the @Generic Element. The functionality of this Action in Avo Assure is to stop the test execution at a specific step and prevent any further steps from running. The execution result is then stored in a dynamic variable.

Syntax

Input Value: <type>(Optional)

Argument	Description
<type> (Optional)	Provide the input type based on the requirement. Supported input types are: Scenario Module Test Case

Note: The inputs are not case-sensitive. You can use any of the following options:

• Empty or Scenario Level: Stops the scenario execution as soon as it is triggered and does not run any further steps.

• Module Level: Stops the entire module execution when the input value is triggered and skips all remaining steps in that module. This option is helpful for end-to-end or batch executions.

• Test Case Level: Stops the test case execution when the input value is triggered and prevents any remaining steps in that test case from running.

Output Value: N/A

Argument	Description
N/A	Not Applicable

Example 1: Default Stop Execution (No Input Provided)

In this example, we explain how the Stop Execution action behaves when no input value is provided.

• Action: Stop Execution

• Input Value: N/A

  • This action does not require any input value. It automatically stops the current scenario execution.

• Output Value: N/A

  • No output value is generated for this action.

• Logical Explanation: The Stop Execution action executes without any input value. In such cases, it automatically stops the test execution at the scenario level by default. Other scenarios or modules within the suite will continue to execute normally.

Example 2: Stopping Execution at Scenario Level

In this example, we explain how to stop the test execution at the scenario level.

• Action: Stop Execution

• Input Value: Scenario

  • The input value (Scenario) specifies that only the current scenario stops, while other scenarios or modules continue to execute.

• Output Value: N/A

  • No output value is generated for this action.

• Logical Explanation: The Stop Execution action takes the value from the Input Value column (Scenario) and stops the execution for the current scenario. Other scenarios or modules in the suite will continue to execute.

Example 3: Stopping Execution at Module Level

In this example, we explain how to stop the test execution at the module level.

• Action: Stop Execution

• Input Value: Module

  • The input value (Module) specifies that the execution of the entire module stops, and no other scenarios under that module are executed.

• Output Value: N/A

  • No output value is generated for this action.

• Logical Explanation: The Stop Execution action takes the value from the Input Value column (Module) and stops the execution for the entire module. No other scenarios under the same module will execute.

Example 4: Stopping Execution at Testcase Level

In this example, we explain how to stop the test execution at the testcase level.

• Action: Stop Execution

• Input Value: Testcase

  • The input value (Testcase) specifies that only the current test case stops, while other test cases continue to execute.

• Output Value: N/A

  • No output value is generated for this action.

• Logical Explanation: The Stop Execution action takes the value from the Input Value column (Testcase) and stops the execution for the current testcase only. Other testcases under the same scenario or module will continue to execute.