Make TestNG custom listener evidence work automatically#1312
Merged
Conversation
pratushnyi
approved these changes
Jul 8, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Context
Starting with TestNG 7.5, TestNG changed listener callback ordering in a way that could close the Allure test result before custom
ITestListenercallbacks added their evidence. This PR makes Allure handle that ordering automatically, so users on TestNG 7.5+ can keep custom listeners registered with@Listenersortestng.xmland still get steps and attachments on the correct test case.Example: a custom
ITestListener.onTestFailure(...)callback that callsAllure.addAttachment("Screenshot on failure", "image/png", screenshotStream, ".png")now attaches that screenshot to the failed test automatically.Related closed reports: #707, #875, #444, #813, #390, #352, #215, #177.
fixes #1150
Checklist