Support @Param metadata for TestNG test parameters#1288
Merged
Conversation
2 tasks
vdvukhzhilov
approved these changes
Jun 11, 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
2 participants
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
TestNG users can now use Allure’s
@Paramannotation on test method parameters to control how those parameters appear in the report. Custom names, hidden and masked modes, and excluded parameters are preserved for both data provider values and parameters supplied through TestNG XML.This also fixes cases where TestNG injects framework parameters such as
Method,ITestContext,ITestResult,XmlTest, orObject[]into a test method. Allure now skips those injected arguments when matching user-provided values to parameter names, so renamed parameters no longer produce duplicate stale entries or shift names onto the wrong values.fixes #893
Checklist