HTML Report: Error report displays wrong failure message when Response Assertion checks Ignore Status and response code is not 200

[asfimport]

@pmouawad (Bug 65885): See attached screenshot showing Response Assertion that:

• has Ignore status checked
• has a Pattern to test: 403|404 and custom failure set to Mensch Maier!

HTML report shows as error:

• 404/Not Found (https://github.com/apache/jmeter/blob/master/src/core/src/main/java/org/apache/jmeter/report/processor/ErrorsSummaryConsumer.java#L90)

While it should display as BackendListener:

• Mensch Maier! (https://github.com/apache/jmeter/blob/master/src/components/src/main/java/org/apache/jmeter/visualizers/backend/ErrorMetric.java#L44)

Created attachment BUG_REPORT_BACKEND_GRAFANA_ERROR.png: Grafana OK

Severity: normal OS: All

[asfimport]

@pmouawad (migrated from Bugzilla): Created attachment HTML_REPORT_404-fs8.png: HTML Report KO

[asfimport]

@pmouawad (migrated from Bugzilla): pmouawad pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/jmeter.git

The following commit(s) were added to refs/heads/master by this push: new 8546e23 https://github.com/apache/jmeter/issues/5632 - HTML Report: Error report displays wrong failure message when Response Assertion checks Ignore Status and response code is not 200 8546e23 is described below

commit 8546e2372ac08eecc27f56a5bfc24a6c4ecc7135 Author: pmouawad <[email protected]> AuthorDate: Tue Feb 15 23:09:16 2022 +0100

https://github.com/apache/jmeter/issues/5632 - HTML Report: Error report displays wrong failure message
when Response Assertion checks Ignore Status and response code is not
200

---

.../jmeter/report/processor/ErrorsSummaryConsumer.java | 9 ++++++--- .../jmeter/report/processor/ErrorsSummaryConsumerTest.java | 13 +++++++++++-- xdocs/changes.xml | 1 + 3 files changed, 18 insertions(+), 5 deletions(-)

[asfimport]

@milamberspace (migrated from Bugzilla): I don't reproduce this issue on JMeter 5.3/5.4.2. Can you provide a sample test case?

[asfimport]

@pmouawad (migrated from Bugzilla): Created attachment BUG_65885.jmx: Test plan that shows difference in behaviour between 5.4.3 and 5.5

[asfimport]

@pmouawad (migrated from Bugzilla): (In reply to Milamber from comment 3)

I don't reproduce this issue on JMeter 5.3/5.4.2. Can you provide a sample test case?

Hello Bruno, I added a test plan that should allow you to reproduce issue. Run it in 5.4.3 and generate report, then in 5.5 , you should see report differs for errors.