Page History
...
The iteration fails only when it contains a validator that fails and has the property Action if Failed set to Stop Iteration.failed set to any value but Continue.
- Abort Iteration to stop the current iteration, and start a new one.
- Abort VU to stop the current iteration and don't start new iterations by this VU.
- Go to the last transaction: to skip to the last top-level transaction in the test case, it's usually the logout transaction, and start a new iteration.
If the iteration during execution encountered an HTTP error in one or several responses, this would not cause the iteration to fail, and it will continue its execution.
If you want a particular HTTP particular HTTP error to cause an iteration to fail, you need to define a validator detecting this error, for example, by checking the response status - code.
If you want all HTTP errors to cause any iteration to fail, you can define a validator with Scope property sets to Global. A single global validator is capable of failing any iteration.
If an iteration is marked as failed, it will be counted toward started and failed iterations. It will not be counted toward passed or incomplete iterations. Performance metrics, such as average response time for such iteration is iterations are excluded from the test metrics.
...
All Pages and Transactions that are fully complete before a validator failed are considered as started and completed.
...
Overview
Content Tools