allure-framework / allure-framework/allure-python

allure-pytest 2.13.2 will merge parameterized use cases

Open
#772 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
814
Forks
260
PR merge metrics
No merged PRs in 30d

Description

#### Bug Description
When using @pytest.mark.parametrize() parametrization, the use cases are merged in the generated allure report, and it is not possible to generate an execution result record for each parametrized use case.

#### Steps to reproduce
![image](https://github.com/allure-framework/allure-python/assets/35887237/9e19ceb4-a67c-46dd-a613-37c4aa9eb2c4)

#### Getting report results
The @pytest.mark.parametrize() parameterization executes four use cases, three of which pass and one of which fails, and sets the failing use case to retry once, and after the execution is complete, the generated allure report can only see the last report record, and the other use case executions are all categorized under " Retries" below
![image](https://github.com/allure-framework/allure-python/assets/35887237/74652429-d100-4268-851f-3a02c64a9405)

#### Expected Result
It is possible to display execution results for each use case individually, as in allure-pytest 2.13.1.
![image](https://github.com/allure-framework/allure-python/assets/35887237/6bf5af4a-83d0-47f4-8b78-4f3b37b3ffcd)

#### Running environment
- Allure version: 2.13.0
- Test framework: pytest 7.1.0
- Allure adaptor: allure-pytest 2.13.2

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.