-
**Describe the bug**
Scenario versus ScenarioOutline detection logic in `behave/runner.py` is extremely brittle
because it relies on English keyword "Scenario".
This solution will not work in other…
-
** Description **
All the steps in the scenario are passed, however, feature status got failed.
**To Reproduce**
Steps to reproduce the behavior:
1. We have a repository with a bunch of tests
…
-
**Describe the bug**
Features and Scenarion what are using the # language: de in the feature files are not added to the reports enlisch ones will. even if they passed.
I also saw resently you chan…
-
**Describe the bug**
If a scenario contains steps with `step.text` (multi-line docstring), the output of this scenario contains `` HTML elements that are not part of the original output.
* MAYBE:…
-
**Describe the bug**
If a scenario fails and a stack trace is shown in the HTML report, it is in nearly cases mostly unreadable.
REASONS:
* Textual output needs 80 columns and more
* Stack tra…
-
**Is your feature request related to a problem? Please describe.**
1. Display Input Folder Location / RegEx whichever available
**Describe the solution you'd like**
In the summary table when it …
-
**Describe the bug**
Having duplicate scenario names when running with parallel test exceution by scenario causes this error in the output:
```
***************************************************…
-
My Behave framework uses Python 3.10 and behave 1.2.6
I have UI test in 1 feature file with 10 scenarios.
The command I run is:
behavex -t @{my_tag} --parallel-processes 10 --parallel-scheme sc…
-
Was trying to embed made screenshot into report but no luck. Is it possible? If yes then how? Can you update readme file with this information?
-
**Describe the bug**
The runner tries to run feature-files that where not provided as command-line args (but only reside in the the same directory).
RELATED TO: #80
**To Reproduce**
Steps to r…