allure-framework / allure-framework/allure-python
Missing list of executed suites
- Langage dominant
- Python
- Étoiles
- 814
- Forks
- 260
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Description
[//]: # (
. 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?
Missing of executed tests in `SIUTES` on Overview page. Suites subtitles show correctly number of items, but missing list of executed suites.

#### If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
1) Run tests
2) Generate report
#### What is the expected behavior?
list of executed suites are displayed
#### Please tell us about your environment:
| Allure version | 2.12.1 |
| --- | --- |
| Test framework | behave@1.2.7 |
|Allure adaptor |allure-behave@2.6.4 |
| |allure-python-commons@2.6.4 |
#### Other information
[//]: # (
. e.g. detailed explanation, stacktraces, related issues, suggestions
. how to fix, links for us to have more context, eg. Stackoverflow, Gitter etc
)
Guide de contribution
Ouvrir le guide de contribution
Piste de recherche
Reproduire le rapport avec behave@1.2.7, allure-behave@2.6.4 et allure-python-commons@2.6.4 en exécutant les tests et en générant un rapport Allure. Comparer la page Overview avec les nombres indiqués dans les sous-titres des suites ; la tâche est terminée lorsque la liste des suites exécutées est affichée.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Évaluation
- Stack technique
- python
- Domaine
- testing
- Type d'issue
- Bug
- Difficulté
- 3/5
- Temps estimé
- 1-2 jours
- Activité
- À l'abandon
- Clarté
- Plutôt claire
- Accessibilité débutants
- 35/100