allure-framework / allure-framework/allure-python
Allure doesn't include information appended to Scenario or Feature description in before statements
- Lenguaje dominante
- Python
- Estrellas
- 814
- Forks
- 260
- Métricas de merge de PR
- Sin PR fusionados en 30 d
Descripción
#### I'm submitting a ...
- [ x] bug report
- [ ] feature request
#### What is the current behavior?
If you include modify a Feature or Scenario description text in Behave's before_feature or before_scenario this is not reflected in the allure result.
#### Steps:
I've added something like this to my environment.py file
```
def before_feature(context, feature):
if 'server' in context.config.userdata:
feature.name += ' on ' + context.config.userdata['server'] + ' environment.'
def before_scenario(context, scenario):
if 'browser' in context.tags:
context.driver = webdriver.Chrome()
scenario.name += ' in ' + context.driver.capabilities['browserName'] + ' ' + context.driver.capabilities['version']
```
Then running with something like `behave -D server="testing" qa/functional/features/`
#### What is the expected behavior?
The feature should have ` on testing environment.` added to it on the allure report. And the scenario should have something like ` in chrome 68.0.3440.84` appended to the end of the name. Currently the allure report includes the feature and scenario descriptions without the appended information. Behave will include this appended information if I do not run with the formatter.
#### What is the motivation / use case for changing the behavior?
I'm trying to edit the Scenario and feature names without using Tables.
#### Please tell us about your environment:
- Allure version: 2.6.0
- Test framework: behave==1.2.6
- Allure adaptor: allure-behave==2.50
Guía de contribución
Línea de trabajo
Empieza por los hooks de environment.py mostrados en la issue y la integración allure-behave utilizada con behave==1.2.6. Reprodúcelo con `behave -D server="testing" qa/functional/features/` y compara el informe con y sin el formatter. Se considera terminado cuando los nombres de Feature y Scenario añadidos aparecen en el informe de Allure.
Escrito por el modelo de indexación a partir del texto del issue.
Evaluación
- Stack tecnológico
- python
- Área
- testing-qa
- Tipo de issue
- Error
- Dificultad
- 3/5
- Tiempo estimado
- 1-2 días
- Estado de actividad
- Estancado
- Claridad
- Bastante claro
- Aptitud para principiantes
- 45/100