allure-framework / allure-framework/allure-python
Allure report doesn't take in correct number of tests when using parametrized tests where tests parameters are duplicated
- Dominant language
- Python
- Stars
- 814
- Forks
- 260
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the Bug**
Allure report doesn't take in correct number of tests when using parametrized tests where tests parameters are duplicated.
**Steps to Reproduce**
1. Create a Python virtual env
2. Install allure-pytest
3. Create example tests to reproduce:
import pytest
@pytest.mark.parametrize(
'a, b',
[
(1, 1),
(1, 1)
]
)
def test_one(a, b):
assert a == b
4. Run tests using `pytest --clean-alluredir --alluredir=/tmp/allure-results`
5. Generate allure report `allure generate /tmp/allure-results/ --clean --output /tmp/allure-results/allure-report --single-file`
6. Open Allure report
**Expected Behaviour**
The report is generated without errors and the report shows 2 tests.
**Screenshots or Additional Context**
_Current version:_

pip freeze:
allure-pytest==2.14.2
allure-python-commons==2.14.2
attrs==25.3.0
iniconfig==2.1.0
packaging==25.0
pluggy==1.6.0
pytest==8.3.5
_Version 2.9.44 (expected working result):_

pip freeze:
allure-pytest==2.9.44
allure-python-commons==2.9.44
attrs==25.3.0
iniconfig==2.1.0
packaging==25.0
pluggy==1.6.0
pytest==8.3.5
six==1.17.0
**What Language are you using?**
Python 3.11.12
**What Framework/Allure Integration you are using?**
Pytest
**What version of Allure Integration you are using?**
2.34.0
**What version of Allure Report you are using?**
Latest
**Code of Conduct**
I agree to follow this project's Code of Conduct
Contributor guide
Research direction
Reproduce the issue with the provided parametrized pytest example and the listed --clean-alluredir and allure generate commands. Compare the generated report with the expected version and trace how the duplicate parameters are represented in the results. Done means the report generates without errors and displays 2 tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100