You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
The linkage to the issue tracker/TMS is not properly established, even though the full URL with parameterization has been set up in the Allure configuration JSON. It takes local host URL instead and throws 404 error
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Add the following details in allureConfig.json file
I'm submitting a ...
What is the current behavior?
The linkage to the issue tracker/TMS is not properly established, even though the full URL with parameterization has been set up in the Allure configuration JSON. It takes local host URL instead and throws 404 error
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
Add the following details in allureConfig.json file
{
"allure": {
"directory": "allure-results",
"links": [
"https://github.com/nunit/docs/issues?utf8=✓&q={issue}",
"https://example.org/{tms}",
"{link}"
],
"brokenTestData": [
"System.Exception"
]
}
}
Add following annotation under test case level
What is the expected behavior?
Users should be able to navigate to the link generated from the allureConfig.json file by clicking upon the link through the report it self
What is the motivation / use case for changing the behavior?
Since this feature previously worked and has encountered issues in the interim, I would like to revert it back to its previous working state.
Please tell us about your environment:
Other information
//: # (
Other NuGet Packages using in the framework
)
The text was updated successfully, but these errors were encountered: