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 a process when needed.

Syntax: 

Input Value: <type>(Optional)

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).

TestCase 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: N/A

Usecase/Example

Scenario:

In an online banking test, while transferring funds, the test might find an invalid account number. The “stop execution” action stops the process right away to prevent further actions like submitting the transfer, helping testers catch the issue early.

Output: Invalid account number is detected during a funds transfer, the “stop execution” action will immediately stop the process.