We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allure API implementations use different names for TMS links:
JUnit: @TmsLink
@TmsLink
Cucumber-JVM: Allure.tms
Allure.tms
NUnit: [AllureTms]
[AllureTms]
Behave: @allure.tms
@allure.tms
Playwright: allure.tms
allure.tms
Jest: allure.tms
Cucumber.js and Mocha: this.tms
this.tms
For the sake of coherence, could we rename the @TmsLink annotation to @Tms for Java JUnit ?
@Tms
To have a coherent API
allure-junit5
2.25.0
The text was updated successfully, but these errors were encountered:
See also allure-python/issues/786
Sorry, something went wrong.
No branches or pull requests
What happened?
I'm submitting a ...
What is the current behavior?
Allure API implementations use different names for TMS links:
JUnit:
@TmsLink
Cucumber-JVM:
Allure.tms
NUnit:
[AllureTms]
Behave:
@allure.tms
Playwright:
allure.tms
Jest:
allure.tms
Cucumber.js and Mocha:
this.tms
What is the expected behavior?
For the sake of coherence, could we rename the
@TmsLink
annotation to@Tms
for Java JUnit ?What is the motivation / use case for changing the behavior?
To have a coherent API
Please tell us about your environment:
Other information
What Allure Integration are you using?
allure-junit5
What version of Allure Integration you are using?
2.25.0
What version of Allure Report you are using?
2.25.0
Code of Conduct
The text was updated successfully, but these errors were encountered: