Repository navigation
馃悶: [Feature] Rename @TmsLink annotation to @Tms聽#987
Description
What happened?
I'm submitting a ...
- bug report
- feature request
- support request => Please do not submit support request here, see note at the top of this template.
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:
- Allure version: 2.25.0
- Test framework: junit 5.10.1
- Allure adaptor: allure-junit5 2.25.0
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
- I agree to follow this project's Code of Conduct
Activity
harmin-parra commentedon Dec 27, 2023
See also allure-python/issues/786
Scot3004 commentedon Dec 13, 2024
I do have a question around this issue, since I'm seeing that currently on
allure-cucumber7-jvmWe have a class namedLabelBuilder聽 where is possible to map the annotation vs the tms linkallure-java/allure-cucumber7-jvm/src/main/java/io/qameta/allure/cucumber7jvm/LabelBuilder.java
Line 58 in 5dc185e
The thing is that ZephyrReport uses instead
@TestCaseKey=ABC-T123https://support.smartbear.com/zephyr-scale-cloud/docs/en/test-automation/cucumber-integration.html
And maybe it would be good to have the possibility to configure the Tag that will be used on the tests, because for example in my team we are comfortable with the provided
@TestCaseKey=ABC-T123and I don't feel that make full refactor to adapt the current implementation to support the allure automatic link with@TMSLink=ABC-T123is viable