Behavex

Latest version: v4.1.2

Safety actively analyzes 724352 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 4 of 6

3.0.0

-------------------------------------------------------------------------------
ENHANCEMENTS:

* Enable Behavex to execute features located in different paths (behavex <features_path1> <features_path2> ... <features_pathN>)
* Printing the HTML output report path in the console at the end of the test execution
* Printing the paths where the features are located when behavex execution is started `Issue 88 <https://github.com/hrcorval/behavex/issues/88>`_
* Printing the execution summary when running tests in parallel
* Major improvement done to enable re-executing all failing scenarios in parallel
* Enable scenario outlines to be executed in parallel (running the outline examples in parallel)
* HTML Report layout improvements to properly render long gherkin steps and long failure messages. `Issue 81 <https://github.com/hrcorval/behavex/issues/81>`_
* Improvement done when parallel execution cannot be launched due to duplicated scenario names, by throwing an error exit code `Issue 86 <https://github.com/hrcorval/behavex/issues/86>`_

FIXES:

* Fix done when logging exceptions in environment.py module
* Fix done when processing the tags associated to scenario outline examples. `Issue 85 <https://github.com/hrcorval/behavex/issues/85>`_
* Fix done to detect and process scenarios written in different languages (Scenario detection does not work for Non-English languages). `Issue 77 <https://github.com/hrcorval/behavex/issues/77>`_
* Fix done to properly render step.text in HTML report. `Issue 79 <https://github.com/hrcorval/behavex/issues/79>`_
* Fix done when parsing empty feature files.

CONTRIBUTORS:

* Contribution from `seb <https://github.com/sebns>`__ providing the fix to an issue when parsing tags associated to scenario outline examples (Thanks!!)

2.0.1

-------------------------------------------------------------------------------
ENHANCEMENTS:

* Enabling Behavex to execute features located in a different path by specifying the Features Path (Behavex <features_path>)
* Displaying the number of features in the "Feature" column
* Showing the number of unique steps and total step executions in the "Steps" chart

FIXES:

* Fix implemented when parsing scenario outlines containing names in examples
* Adding missing webhooks related to tags (before_tag and after_tag)

1.6.0

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Improvement in the order in which the events are executed in environment.py. On every "before_<something>" event, the BehaveX event has precedence over the same event in testing solution, and the other way around should be on every "after_<something>" event
* Reusing FEATURES_PATH environment variable to indicate were features are located

FIXES:

* Fix implemented when scenarios are dynamically skipped or removed from the execution list
* Fix implemented in scenario outlines, as scenarios were not being published in execution reports when examples are part of scenario descriptions and contain white spaces

1.5.12

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Reporting the average reusability of test steps in metrics
* Consider not only the scenario description but also the feature description when creating the evidence path, to avoid issues with duplicated scenario names
* Improvement done in HTML report to consider line breaks in reported error messages in failing steps

FIXES:

* Fixed issue when executing scenarios using the "--include" argument

1.5.11

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Enable wrapper execution using the **main** method instead of the **behavex** executable: **"python -m behavex -t /<tag/> ..."**

1.5.10

-------------------------------------------------------------------------------

ENHANCEMENTS:

* Changes done to **rerun-failures** argument, to request the **failing_scenarios.txt** path as argument value

FIXES:

* Enable re-executing failing scenarios that contain blank spaces in path or filename

Page 4 of 6

© 2025 Safety CLI Cybersecurity Inc. All Rights Reserved.