Threshold Evaluation Timing in k6 Load Tests

k6 Threshold Evaluation Timing

The precise goal is to configure k6 load tests to reliably signal performance regressions without generating excessive alert noise from transient metric spikes.

Constraints and Uncertainty

The current uncertainty involves balancing immediate failure detection against the need to filter out short-lived anomalies using abortOnFail and delayAbortEval.

• Threshold results are summarized post-execution by default.
• The behavior of these options is version-dependent.

What is the documented evaluation sequence when delayAbortEval is active versus when it is omitted? Does abortOnFail execute before or after the delay period concludes? How should a user verify the effective timing of a threshold breach against the specific k6 version being used?