Skip to content
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

[Feature] Pytest - Rename @allure.testcase decorator to @allure.tms #786

Open
1 of 3 tasks
harmin-parra opened this issue Dec 27, 2023 · 1 comment
Open
1 of 3 tasks
Labels
task:improvement Change that improves some user experience but can't be considered a new feature theme:core

Comments

@harmin-parra
Copy link

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?

The different Allure API implementations use different names for the testcase link:

  • Python behave: @allure.tms:TMS-456
  • Python pytest: @allure.testcase("TMS-456")
  • Java JUnit: @TmsLink("TMS-456")
  • .Net NUnit: [AllureTms("TMS-456")]
  • Cucumber.js: this.tms("https://example.com/tms/TMS-456", "TMS-456");
  • PHPUnit: #[TmsLink('TMS-456')]

What is the expected behavior?

For the sake of coherence, could we rename the @allure.testcase decorator to @allure.tms for pytest ?

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: pytest@7.4.2
  • Allure adaptor: allure-pytest@2.13.2

Other information

@harmin-parra
Copy link
Author

harmin-parra commented Dec 27, 2023

See also allure-java/issues/987

@harmin-parra harmin-parra changed the title [Feature] Rename @testcase decorator to @tms [Feature] Pytest - Rename @allure.testcase decorator to @allure.tms Jan 4, 2024
@delatrie delatrie added theme:core task:improvement Change that improves some user experience but can't be considered a new feature labels Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
task:improvement Change that improves some user experience but can't be considered a new feature theme:core
Projects
None yet
Development

No branches or pull requests

2 participants