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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We should create an annotation @Link(name, url, type)
@Link(name, url, type)
Also you can use system properties for common parts of links:
allure.link.{type}.pattern = https://example.org/{}
allure.link.{type}.pattern
https://example.org/{}
Predefines for issue and tms:
@Issue
issue
@Tms
tms
Examples of usage:
@Link("https://example.org") @Link(name = "My site", url = "https://example.org") @Link(name = "My other site", url = "https://example.org", type = "hello") @Link(name = "Yet another site", url = "id-123", type = "hello") // and system property `allure.link.hello.pattern: https://example.org/{}` @Issue("SOME-123") @Issue("https://example.org/SOME-123") @Issue(name = "SOME-123", url = "https://example.org/SOME/123") @Issue(name = "SOME-123", url = "SOME/123") // and system property `allure.link.hello.pattern: https://example.org/{}`
The text was updated successfully, but these errors were encountered:
9dd042e
baev
No branches or pull requests
We should create an annotation
@Link(name, url, type)
Also you can use system properties for common parts of links:
allure.link.{type}.pattern
=https://example.org/{}
Predefines for issue and tms:
@Issue
is the link with typeissue
@Tms
is the link with typetms
Examples of usage:
The text was updated successfully, but these errors were encountered: