allure-framework / allure-framework/allure-python
Prevent allure from force adding test folder name as parent suite name when parent suite is not specified
- Lingua principale
- Python
- Stelle
- 814
- Fork
- 260
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
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
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Riprodurre il report con test in Folder_A e Folder_B che condividono lo stesso valore di allure.dynamic.suite("Tests"). Ispezionare il percorso di integrazione di pytest che assegna le suite padre e la configurazione pytest.ini menzionata nell’issue. Il lavoro è completato quando i nomi delle cartelle non vengono aggiunti come suite padre se non ne viene specificata nessuna, mentre le suite padre definite esplicitamente continuano a funzionare.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- python
- Ambito
- testing
- Tipo di issue
- Bug
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Stato di attività
- Tranquilla
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 45/100