Some extractors, such as security tokens, are critical for test case integrity. If a critical extractor is not found during a test run, then the iteration can't continue. This section describes how to mark an extractor as critical and the steps that will occur if it is not found during the test run.
Marking critical extractors
To mark an extractor as critical, set the Action if not found property to one of the following values:
- Abort iteration: The response that contains the extractor is marked as an error. Stops the current iteration and starts a new one.
- Abort VU: The response that contains the extractor is marked as an error. Stops sending requests from this VU.
- Go to the last transaction: The response that contains the extractor is marked as an error. Skips to the last top-level transaction in the test case, it's usually the logout transaction and starts a new iteration.
Failed iteration
If a critical extractor is not found then the current iteration is marked as failed.
Overview
Content Tools
