-
Notifications
You must be signed in to change notification settings - Fork 21
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Adding scenarios to validate the rerun command works properly
- Loading branch information
Showing
4 changed files
with
35 additions
and
3 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 @@ | ||
tests/features/secondary_features/passing_tests.feature:8,tests/features/secondary_features/passing_tests.feature:29,tests/features/secondary_features/failing_tests.feature:3 |
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,19 @@ | ||
Feature: Failing Scenarios | ||
|
||
@FAILING | ||
Scenario Outline: Performing rerun of failing scenarios using the -rf option | ||
Given I have installed behavex | ||
When I setup the behavex command with "<parallel_processes>" parallel processes and parallel scheme set as "<parallel_scheme>" | ||
When I run the behavex command with a file of failing tests | ||
Then I should see the following behavex console outputs and exit code "1" | ||
| output_line | | ||
| 2 scenarios passed, 1 failed | | ||
| Exit code: 1 | | ||
And I should not see exception messages in the output | ||
And I should see the same number of scenarios in the reports not considering the skipped scenarios | ||
And I should see the generated HTML report does not contain internal BehaveX variables and tags | ||
Examples: | ||
| parallel_scheme | parallel_processes | | ||
| scenario | 1 | | ||
| scenario | 3 | | ||
| feature | 2 | |
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