allure-framework / allure-framework/allure2
Test cases with equal titles/names override each other
- Dominant language
- HTML
- Stars
- 5.5k
- Forks
- 782
- Avg merge
- 2d 33m
- Merged PRs (30d)
- 16
Description
### Describe the Bug
We are using Allure to generate reports from the `allure-results` produced by `newman-reporter-allure`. We have already tested it, and `newman-reporter-allure` works perfectly—it runs all tests and the `allure-results` contains every test as expected. The issue arises with the `allure generate` command: when tests within the same collection or group share an identical name/title, only one test appears in the generated Allure report.
We consider this a bug because each test has its own UUID and is correctly saved in the `allure-results`, indicating that the Allure results format supports unique identifiers. However, it appears that `allure generate` is using a HashMap somewhere, and instead of using the UUID as the test case identifier (hashmap key), it is using the "name" property.
### Steps to Reproduce
1. Prepare an `allure-results` folder with test cases within the same suite/collection that have identical titles/names.
2. allure generate
3. Browse the "Suites" section.
4. Notice that only one test is visible, while the other tests with the same title are missing.
### Expected Behaviour
All tests should be visible. Since each test has a unique UUID, Allure should reference them by UUID rather than by title.
### Screenshots or Additional Context
`equal test case names`:
`not equal`:
### What Language are you using?
Java
### What Framework/Allure Integration you are using?
newman-reporter-allure
### What version of Allure Integration you are using?
3.1.0
### What version of Allure Report you are using?
2.32.2
### Code of Conduct
- [x] I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Start by reproducing the issue with an allure-results folder containing tests with identical titles, then run the allure generate command and inspect the generated Suites view. Trace how the report handles each test's UUID and name, and confirm that all tests remain visible when generation is complete.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100