fix scenario status reporting (allure-framework#226)

beckerGil · Apr 10, 2023 · 5deb0f1 · 5deb0f1
1 parent b892f69
commit 5deb0f1
Show file tree

Hide file tree

Showing 2 changed files with 26 additions and 2 deletions.
diff --git a/allure-behave/features/scenario.feature b/allure-behave/features/scenario.feature
@@ -22,6 +22,30 @@ Feature: Scenario
             | undefined | broken |
 
 
+  Scenario: Skip steps after fail step
+    Given feature definition
+        """
+        Feature: Scenario
+
+        Scenario: Scenario with failed step in chain
+          Given passed step
+          Given failed step
+          Given broken step
+        """
+      When I run behave with allure formatter
+     Then allure report has a scenario with name "Scenario with failed step in chain"
+      And this scenario has "failed" status
+
+      And this scenario contains step "Given passed step"
+      And this step has "passed" status
+
+      And this scenario contains step "Given failed step"
+      And this step has "failed" status
+
+      And this scenario contains step "Given broken step"
+      And this step has "skipped" status
+
+
   Scenario: Scenario without name
     Given feature definition
         """

diff --git a/allure-behave/src/utils.py b/allure-behave/src/utils.py
@@ -54,14 +54,14 @@ def scenario_tags(scenario):
 
 def scenario_status(scenario):
     for step in scenario.all_steps:
-        if step.status != 'passed':
+        if step_status(step) != 'passed':
             return step_status(step)
     return Status.PASSED
 
 
 def scenario_status_details(scenario):
     for step in scenario.all_steps:
-        if step.status != 'passed':
+        if step_status(step) != 'passed':
             return step_status_details(step)