allure-framework / allure-framework/allure-python

I want to addEnvironment(name, value) via code instead of xml file

Abierto
#276 1 comentario 0 reacciones 0 asignados Ver en GitHub
task:new feature theme:pytest
Lenguaje dominante
Python
Estrellas
814
Forks
260
Métricas de merge de PR
Sin PR fusionados en 30 d

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 ...
- [ ] bug report
- [x] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.

#### What is the current behavior?
I can't found add environment function in allure

#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem

#### What is the expected behavior?
I want to addEnvironment(name, value) via code

#### What is the motivation / use case for changing the behavior?
I want to add environment to show my test line info, and I use jenkins to executor our testcase

#### Please tell us about your environment:

- Allure version: 2.5.0
- Test framework: pytest@3.6.3
- Allure adaptor: allure-pytest@2.5.0

#### Other information

[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)

Guía de contribución

Abrir la guía de contribución

Línea de trabajo

Comienza localizando el manejo del XML de entorno y las APIs públicas en el adaptador allure-pytest; el issue no indica archivos ni tests. Determina dónde debería ubicarse una entrada de entorno basada en código y define la finalización como la posibilidad de añadir un par name/value mediante el adaptador y verificarlo en el informe de Allure generado.

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

Evaluación

Stack tecnológico
python
Área
testing
Tipo de issue
Nueva funcionalidad
Dificultad
4/5
Tiempo estimado
3-5 días
Estado de actividad
Estancado
Claridad
Necesita aclaración
Aptitud para principiantes
25/100

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.