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

AllureIssue and AllureTMS annotations will not build up the full URL by getting allureConfig.json #452

Open
1 of 3 tasks
SuravinS opened this issue Feb 20, 2024 · 0 comments

Comments

@SuravinS
Copy link

SuravinS commented Feb 20, 2024

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 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

image

image

If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

  1. 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"
    ]
    }
    }

  2. Add following annotation under test case level

 [AllureIssue("ISSUE-123")]
 [AllureTms("TMS-123")]

  1. After executing the test case, please validate by clicking or inspecting the hyperlink generated during the build.

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:

  • Allure version: 2.11.0
  • Test framework: selenium c#
  • Allure adaptor: Allure.NUnit (2.11.0)
  • Generate report using: .net 6

Other information

//: # (
Other NuGet Packages using in the framework

<PackageReference Include="Allure.Net.Commons" Version="2.11.0" />
<PackageReference Include="Allure.NUnit" Version="2.11.0" />
<PackageReference Include="JUnitTestLogger" Version="1.1.0" />
<PackageReference Include="NTextCat" Version="0.3.65" />
<PackageReference Include="NUnit" Version="4.0.1" />
<PackageReference Include="NUnit.Engine.Api" Version="3.16.3" />
<PackageReference Include="NUnit3TestAdapter" Version="4.5.0" />
<PackageReference Include="Microsoft.NET.Test.Sdk" Version="17.9.0-preview-23577-04" />
<PackageReference Include="WebDriverManager" Version="2.17.1" />
<PackageReference Include="DotNetSeleniumExtras.PageObjects" Version="3.11.0" />
<PackageReference Include="DotNetSeleniumExtras.PageObjects.Core" Version="4.14.1" />
<PackageReference Include="DotNetSeleniumExtras.WaitHelpers" Version="3.11.0" />
<PackageReference Include="Newtonsoft.Json" Version="13.0.3" />
<PackageReference Include="NUnit.Console" Version="3.16.3" />
<PackageReference Include="System.Runtime" Version="4.3.1" />
<PackageReference Include="Selenium.Support" Version="4.16.2" />
<PackageReference Include="Selenium.WebDriver" Version="4.16.2" />
<PackageReference Include="System.Data.SqlClient" Version="4.8.5" />
<PackageReference Include="Microsoft.Extensions.Configuration.Json" Version="8.0.0" />
<PackageReference Include="Microsoft.Extensions.Configuration.Binder" Version="8.0.0" />

)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant