-
Notifications
You must be signed in to change notification settings - Fork 227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Annotation @Param doesn't work with TestNG framework #893
Labels
Comments
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 22, 2024
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 22, 2024
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 22, 2024
…t-showing-names-in-report Fix for allure-framework#893 - param annotation name not coming up in report
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 22, 2024
…ng up in report" This reverts commit b85e6ae.
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 25, 2024
…t-showing-names-in-report Fix for allure-framework#893 - param annotation name not coming up in report
mr-possible
pushed a commit
to mr-possible/allure-java
that referenced
this issue
Sep 25, 2024
…ng up in report" This reverts commit b85e6ae.
2 tasks
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 25, 2024
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Sep 25, 2024
mr-possible
added a commit
to mr-possible/allure-java
that referenced
this issue
Nov 29, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Annotation @param doesn't work with TestNG framework
To Reproduce
Actual behavior
Params in allure report marked as arg0, arg1, etc.
Expected behavior
Params marked with text from @param annotation
Screenshots
Versions:
The text was updated successfully, but these errors were encountered: