allure-framework / allure-framework/allure-java
Add supports for categorize test cases with TestNG Groups
- Lingua principale
- Java
- Stelle
- 376
- Fork
- 240
- Merge medio
- 1g 7h
- PR unite (30g)
- 45
Descrizione
[//]: # (
. Note: for support questions, please use Stackoverflow or Gitter**.
. This repository's issues are reserved for feature requests and bug reports.
.
. In case of any problems with Allure Jenkins plugin** please use the following repository
. to create an issue: https://github.com/jenkinsci/allure-plugin/issues
.
. Make sure you have a clear name for your issue. The name should start with a capital
. letter and no dot is required in the end of the sentence. An example of good issue names:
.
. - The report is broken in IE11
. - Add an ability to disable default plugins
. - Support emoji in test descriptions
)
#### I'm submitting a ...
- feature request
#### What is the current behavior?
Recently, I came across the problem that I wasn't able to check the results of test case group wise when I executed the same test case in different groups in different Jenkins jobs.
Below is the scenario:
1. Test case **A** is a part of group UK and US.
2. Trigger Jenkins job **J** to execute test case **A** in Jenkins job **J1** as a part of UK and in Jenkins job **J2** as a part of US.
4. Copy allure artifacts of **J1** and **J2** in **J** and merge the report using allure Jenkins plugin.
**Results**: Jenkins job **J** merged test case **A** results as a history.
#### What is the expected behavior?
I want to see the execution results group-wise for clear understanding.
#### Please tell us about your environment:
No need to specify as its feature request.
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Inizia esaminando l’integrazione di TestNG e lo scenario di merge di Jenkins descritto nell’issue. Determina come vengono attualmente rappresentati l’appartenenza ai gruppi e i risultati uniti, quindi definisci test che distinguano lo stesso caso eseguito nei gruppi UK e US; il lavoro è completato quando il report unito espone tali esecuzioni per gruppo.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- java
- Ambito
- testing
- Tipo di issue
- Funzionalità
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Stato di attività
- Ferma
- Chiarezza
- Abbastanza chiara
- Idoneità per principianti
- 25/100