allure-framework / allure-framework/allure-python

Prevent allure from force adding test folder name as parent suite name when parent suite is not specified

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

描述

I have tests in several folders with all tests having a common **allure.dynamic.suite** name.
In my allure report all the tests get grouped under this name.

However, of late, the suites go under the folder name of the tests such that the folder name is taken as the Parent Suite.

Is there a way to prevent the folder names from being taken as Parent Suite name and simply group the tests under the suite names like how it used to be?

The only way i can think of currently to avoid this issue is to rename all allure.dynamic.suite to allure.dynamic.parent_suite in all of my tests.

But the reason this will be a problem is,
If I collect multiple allure artifacts and consolidate them into a single report, I would want to group them under a common parent suite name. But since each report will have a parent suite name, they will get overwritten.

### What Operating System are you using (both controller, and any agents involved in the problem)?

Windows

### Reproduction steps

1. Have tests in two folders (Folder_A, Folder_B) with each of the tests having the same allure.dynamic.suite name("Tests")
2. Run the tests and generate allure report

### Expected Results

Report should display,

Image

### Actual Results

Report is displaying,

Image

The name of the test folder is taken as the parent suite name although no parent suite has been specified.

### Anything else?
Can we have,
A configuration option like `--no-parent-suite` or `--disable-auto-parent-suite`
Or a new pytest.ini option like `allure_skip_parent_suite = true`

### Are you interested in contributing a fix?

Yes

贡献指南

打开贡献指南

调研方向

使用 Folder_A 和 Folder_B 中共享相同 allure.dynamic.suite("Tests") 值的测试重现该报告。检查用于分配父套件的 pytest 集成路径,以及 issue 中提到的 pytest.ini 配置。当未指定父套件时,文件夹名称不会被添加为父套件,而显式定义的父套件仍能正常工作,即表示完成。

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

评估

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

把新 issue 发到你的邮箱

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