allure-framework / allure-framework/allure-python

bug: When the check is placed in the parent step and the child step asserts, the check becomes invalid.

Ouverte
#824 2 commentaires 0 réactions 0 personnes assignées Voir sur GitHub
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
- [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?

```python
def validate_something(a, b, c, d):
with check, allure.step(f'some assertions'):
with allure.step('aa'):
assert a == 1
with allure.step('b'):
assert b == 2
with allure.step('cccc'):
assert c == 13
with allure.step('dddd'):
assert d == 4

def test_22():
with check, allure.step("setup step"):
assert 5 == 5
validate_something(1,2,3,4)
```
As above, the test report is:

![image](https://github.com/user-attachments/assets/afd66464-b100-4134-aee1-f3b9e15fab35)

the step dddd won't be executed, the effect of pytest-check is gone

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

PS:
if run, the step [some assertions] won't be marked as failed, but pass, and the four sub-steps will be executed, I hope if any sub step is failed, the parent should be failed:
```python
def validate_something(a, b, c, d):
with allure.step(f'some assertions'):
with check, allure.step('aa'):
assert a == 1
with check, allure.step('b'):
assert b == 2
with check, allure.step('cccc'):
assert c == 13
with check, allure.step('dddd'):
assert d == 4

def test_22():
with check, allure.step("setup step"):
assert 5 == 5
validate_something(1,2,3,4)
```

main.py run pytest (allure) and get the allure report

#### What is the expected behavior?
step dddd should be executed

#### What is the motivation / use case for changing the behavior?

#### Please tell us about your environment:

- Allure version: 2.13.5
- Test framework: pytest@8.2.2
- pytest-check: 2.3.1
- Allure adaptor: allure-pytest@2.13.5

#### 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

Commencez par la reproduction Python dans l’issue, en utilisant main.py et en exécutant pytest avec les versions d’Allure et de pytest-check indiquées. Suivez la façon dont le contexte de check externe interagit avec les blocs allure.step imbriqués. C’est terminé lorsque l’étape dddd s’exécute après un échec d’assertion antérieur et que l’étape parente some assertions est marquée comme ayant échoué lorsqu’une assertion enfant échoue.

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
45/100

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.