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)

Supported Input Formats:

• Text: Plain string input.

Argument	Description
<type> (Optional)	Provide the input type to stop execution according to the requirement. Supported Input Types are: testcase testgroup

Note: The inputs are case-sensitive. This works in Debug, normal Execution, and E2E Execution modes. You can specify any of the following options for stopping execution:

• Test Case Level: Execution stops for the current Test case. The current Test Step Groups and all remaining Test Step Groups in that Test case are skipped, and execution continues with the next Test case.

• Test Step Group Level: Execution stops only for the current Test Step Group. Execution continues with the next Test Step Group in the same Test case or moves to the next test case if no more groups exist.

• Empty: When no input is provided, the system treats it as Test Case Level. Execution stops for the current test case and continues with the next test case.

In Debug mode, If the only Test Step Groups (TSGs) exist within a single Test case. The Stop Execution action works for testcase and empty input.

Output Value: N/A

Argument	Description
N/A	Not Applicable

Example 1: Stopping Execution at Test Case Level (Empty Input Value)

In this example, we explain how to stop test execution at the Test Case level without providing any input in the Input Value.

• Action: Stop Execution

• Input Value: (No Input Value)

  • Empty Input Value stops the current Test case and continues with the next Test case.

• Output Value: N/A

  • No output value is generated for this action.

• Logical Explanation: The Stop Execution action takes an empty value from the Input Value column. By default, the action stops execution for the current Test case only. All remaining steps and Test Step Groups within the same Test case are skipped, and execution continues with the next Test case.

Example 2: Stopping Execution at Test Group Level

In this example, we explain how to stop the test execution at the Test Step Group level.

• Action: Stop Execution

• Input Value: testgroup

  • The input value (testgroup) specifies that only the current Test Step Group stops, and it continues with the next Test Step Group in the same Test case.

• 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 (testgroup) and stops execution for the current Test Step Group. The remaining Test Step Groups within the same Test case continue to execute normally.

Example 3: Stopping Execution at Test Case Level

In this example, we explain how to stop the test execution explicitly at the Test case level.

• Action: Stop Execution

• Input Value: testcase

  • The input value (testcase) specifies that the current Test case stops, and it continues with the next Test case in the folder.

• 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 execution for the current Test case. All remaining steps and Test Step Groups in that Test case are skipped, and execution proceeds to the next Test case.