allure-framework / allure-framework/allure-java

Add supports for categorize test cases with TestNG Groups

Abierto
#413 0 comentarios 3 reacciones 0 asignados Ver en GitHub
Lenguaje dominante
Java
Estrellas
376
Forks
240
Merge medio
1 d 7 h
PR fusionados (30 d)
45

Descripción

[//]: # (
. 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.

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza revisando la integración de TestNG y el escenario de merge de Jenkins descrito en el issue. Determina cómo se representan actualmente la pertenencia a grupos y los resultados fusionados, y luego define pruebas que distingan el mismo caso ejecutado en los grupos UK y US; se considerará completado cuando el informe fusionado exponga esas ejecuciones por grupo.

Escrito por el modelo de indexación a partir del texto del issue.

Evaluación

Stack tecnológico
java
Área
testing
Tipo de issue
Nueva funcionalidad
Dificultad
5/5
Tiempo estimado
Más de una semana
Estado de actividad
Estancado
Claridad
Bastante claro
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.