allure-framework / allure-framework/allure-python

allure-pytest 2.13.2 will merge parameterized use cases

未关闭
#772 2 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看
主要语言
Python
星标
814
派生
260
PR 合并指标
30 天内没有已合并 PR

描述

#### 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

贡献指南

打开贡献指南

调研方向

首先使用 pytest 7.1.0 和 allure-pytest 2.13.2,通过 @pytest.mark.parametrize() 重现该问题,然后将生成的报告与 allure-pytest 2.13.1 的报告进行比较。当每个参数化用例都有自己的执行结果(包括失败的用例及其重试),而不是被合并到 Retries 下时,即表示完成。

由索引模型根据 Issue 内容生成。

评估

技术栈
python
领域
testing
Issue 类型
缺陷
难度
3/5
预计耗时
1-2 天
活跃度
停滞
描述清晰度
基本清楚
新手友好度
42/100

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。