Why don't generated reports take uid from allure-results?

[noomorph]

I am troubled by this inconsistency — I have no deterministic way to generate a link to a specific test case result in the HTML report, even if I know what the "id" is in the container or result JSON.

Is there a good reason?

[noomorph]

In other words, why do you use dest.setUid(uidGenerator.get()); here:

https://github.com/allure-framework/allure2/blob/main/allure-generator/src/main/java/io/qameta/allure/allure2/Allure2Plugin.java#L184

instead of taking result.getUuid()?

[noomorph]

So, if I need it sooner, I may try luck with a fork, right?

Indeed, I need to report deep links in advance before the report is even generated. 🤔
In some cases, post-processing allure-report could do the job as well, though.

Thanks for the explanation! 👍

[baev]

It would be nice if you bring it to light and share some insights on the problem you're trying to solve.

Initially, the idea was to use custom plugins and generate the needed output with all the links from the report (or publish report links via API directly, similar to the Jira/Xray plugin we provide). So, instead of post-processing the existing allure-report, the custom plugin may provide you with a separate JSON with all the data needed.

[noomorph]

Okay, so to put it short, I wanted to have a guarantee that if I add a test like this:

@AllureId('UNIQ-1`)
someTestCase() {
 // or whatever: allure.id('UNIQ-1') inside test body
}

that I will be able to find it on https://allure-framework.github.io/allure-demo/5/#testresult/UNIQ-1.

In my case, I'd like to embed iframes with a specific test result on a statically generated website. It is uncommon, but I just asked if it was possible. If I know the id in advance, I don't even need to regenerate the website — I can just regenerate allure-report if needed.

[baev]

The easiest way, in my opinion, would be to create a custom redirect layout in the report that would redirect #allureId/UNIQ-1 to #testresult/$uid. To active that, all you need is to create a plugin that will create data/redirects.json, populate it with data needed (a simple map from-to will do), then create a layout that will access data/redirects.json and do the redirect if value found.

By the way, using @AllureId for something else but Allure TestOps isn't recommended. Many features (including IDE integrations) may behave weirdly. Instead, you can create a custom label instead.

[noomorph]

Thank you, Dmitry. Looks like I have a clear picture of the status. Thanks for your time and effort to explain.

P.S. I hope you will find some time in the near future to review the Owner PR. My IntelliJ trial is expiring on 25th April 😅