allure-framework / allure-framework/allure-python
Prevent allure from force adding test folder name as parent suite name when parent suite is not specified
- Lenguaje dominante
- Python
- Estrellas
- 814
- Forks
- 260
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
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,
### Actual Results
Report is displaying,
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
Guía de contribución
Línea de trabajo
Reproducir el informe con tests en Folder_A y Folder_B que comparten el mismo valor de allure.dynamic.suite("Tests"). Inspeccionar la ruta de integración de pytest que asigna suites principales y la configuración de pytest.ini mencionada en la issue. Se considera terminado cuando los nombres de las carpetas no se añaden como suites principales cuando no se especifica ninguna, mientras que las suites principales definidas explícitamente siguen funcionando.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- testing
- Tipo de issue
- Error
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Tranquilo
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100