forked from allure-framework/allure-python
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Allure test plan support for behave (via allure-framework#531)
- Loading branch information
1 parent
4fa3e3a
commit e262568
Showing
7 changed files
with
160 additions
and
20 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,86 @@ | ||
Feature: Test plan | ||
Scenario: Select scenarios by fullname | ||
Given feature definition | ||
""" | ||
Feature: Test plan example | ||
Scenario: Scenario with passed step | ||
Given passed step | ||
Scenario: Ignored scenario | ||
Given passed step | ||
""" | ||
Given feature definition | ||
""" | ||
Feature: Another Test plan example | ||
Scenario: Another scenario with passed step | ||
Given passed step | ||
Scenario: Another ignored scenario | ||
Given passed step | ||
""" | ||
Given test plan | ||
""" | ||
{ | ||
"version":"1.0", | ||
"tests": [ | ||
{ | ||
"selector": "<string>:Scenario with passed step" | ||
}, | ||
{ | ||
"selector": "<string>:Another scenario with passed step" | ||
} | ||
] | ||
} | ||
""" | ||
When I run behave with allure formatter | ||
Then allure report has a scenario with name "Scenario with passed step" | ||
Then allure report has not a scenario with name "Ignored scenario" | ||
Then allure report has a scenario with name "Another scenario with passed step" | ||
Then allure report has not a scenario with name "Another ignored scenario" | ||
|
||
Scenario: Select scenarios by allureid | ||
Given feature definition | ||
""" | ||
Feature: Test plan example | ||
@allure.as_id:1 | ||
Scenario: Scenario with passed step | ||
Given passed step | ||
@allure.as_id:2 | ||
Scenario: Ignored scenario | ||
Given passed step | ||
""" | ||
Given feature definition | ||
""" | ||
Feature: Another Test plan example | ||
@allure.as_id:3 | ||
Scenario: Another scenario with passed step | ||
Given passed step | ||
@allure.as_id:4 | ||
Scenario: Another ignored scenario | ||
Given passed step | ||
""" | ||
Given test plan | ||
""" | ||
{ | ||
"version":"1.0", | ||
"tests": [ | ||
{ | ||
"id": "1" | ||
}, | ||
{ | ||
"id": "3" | ||
} | ||
] | ||
} | ||
""" | ||
When I run behave with allure formatter | ||
Then allure report has a scenario with name "Scenario with passed step" | ||
Then allure report has not a scenario with name "Ignored scenario" | ||
Then allure report has a scenario with name "Another scenario with passed step" | ||
Then allure report has not a scenario with name "Another ignored scenario" |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters