allure-framework / allure-framework/allure-python
FEATURES BY STORIES is missing
- 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 ...
- [ x] bug report
- [ ] feature request
- [ ] support request => Please do not submit support request here, see note at the top of this template.
#### What is the current behavior?
In the allure home page the FEATURES BY STORIES is missing.
The section is correctly showed up to ver 2.20.1.
More recent versions included 2.24.0 do not show the section FEATURES BY STORIES anymore.
#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
1. GO to the allure WEB homepage
#### What is the expected behavior?
The FEATURES BY STORIES section should correctly showed.
#### What is the motivation / use case for changing the behavior?
#### Please tell us about your environment:
- Allure version: 2.24.0
- Test framework: behave
- Allure adaptor: allure-behave@2.13.2
#### 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
Línea de trabajo
Comienza en la página de inicio web de Allure y reproduce la sección faltante FEATURES BY STORIES con Allure 2.24.0, allure-behave 2.13.2 y el contexto del informe proporcionado. Compara el resultado con la versión 2.20.1; se considera terminado cuando la sección está presente y se muestra correctamente en la versión más reciente.
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
- 4/5
- Tiempo estimado
- 3-5 días
- Estado de actividad
- Estancado
- Claridad
- Necesita aclaración
- Aptitud para principiantes
- 38/100