Failing Assertions on Script (JMeter) Monitor Timeouts

When your JMeter contains assertions of any kind and the script times out before reaching a step evaluated with assertion, we now try to find and fail the assertion (artificial assertion failure) because it was not evaluated at all. The feature is particularly useful for customers who have APM integration alerts set up based on JMeter monitor assertion names.
cacm
When your JMeter contains assertions of any kind and the script times out before reaching a step evaluated with assertion, we now try to find and fail the assertion (artificial assertion failure) because it was not evaluated at all. The feature is particularly useful for customers who have APM integration alerts set up based on JMeter monitor assertion names.
ASM uses the following algorithm:
  1. Finds the corresponding step in JMX (source script) file.
  2. Finds the first assertion that comes after this step.
  3. Fails it.
  4. If there is no such assertion, inserts artificial assertion result for the last step where timeout occurred.
 Timeout messages or error codes were not changed.
ASM cannot match JTL output (partial script results on timeout) to JMX request for all occasions with 100 percent correctness due to limitations imposed by JMeter. This feature might not fail the exception that you expected.
If you think we failed an incorrect assertion, create a support ticket with the following information:
  • Original JMX script
  • Partial JTL output from the script run
  • Indicate the assertion that you expected to fail instead