allure-framework / allure-framework/allure2
Permalink testcases/{testName}
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
#### I'm submitting a ...
- [ ] feature request
#### What is the current behavior?
Permalinks for allure dashboard are currently formed like this (ids) :
https://demo.qameta.io/allure/#suites/bd5db97a62d5115f1a4b09738ac3c2b1/64cfd40c8b6df023/
#### What is the expected behavior?
Could it be possible to display it with full name instead ?
https://demo.qameta.io/allure/#suites/AlwaysPassingTest/testFour
#### What is the motivation / use case for changing the behavior?
Same behaviour as junit jenkins plugin.
Like that we could also use lastJob link and it's easier to send link in a clever way to other people.
#### Please tell us about your environment:
| Allure version | 2.2.0 |
| --- | --- |
| Test framework | junit@4.12 |
| Generate report using | allure-plugin |
Contributor guide
Research direction
No file or test is named. Start by tracing how the Allure dashboard builds suite and test permalink URLs for the JUnit 4.12 report generated by allure-plugin. Done means the existing id-based link can use the test's full name, producing a stable URL like suites/AlwaysPassingTest/testFour while preserving dashboard navigation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100