Description

harmin-parra

opened on Dec 27, 2023

Issue body actions

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

1. harmin-parra

   added

   triage

   pr:bugSomething isn't workingSomething isn't working

   on Dec 27, 2023
2. harmin-parra commented on Dec 27, 2023

   

   harmin-parra

   on Dec 27, 2023

   Author

   More actions

   See also allure-python/issues/786
3. Scot3004 commented on Dec 13, 2024

   

   Scot3004

   on Dec 13, 2024

   More actions

   I do have a question around this issue, since I'm seeing that currently on allure-cucumber7-jvm We have a class named LabelBuilder  where is possible to map the annotation vs the tms link

   allure-java/allure-cucumber7-jvm/src/main/java/io/qameta/allure/cucumber7jvm/LabelBuilder.java

   Line 58 in 5dc185e

   private static final String TMS_LINK = "@TMSLINK";

   The thing is that ZephyrReport uses instead @TestCaseKey=ABC-T123

   https://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-T123 and I don't feel that make full refactor to adapt the current implementation to support the allure automatic link with @TMSLink=ABC-T123 is viable
4. baev

   added the

   Bug

   issue type on Jul 10, 2026
5. baev

   removed

   pr:bugSomething isn't workingSomething isn't working

   on Jul 10, 2026

Issue actions