Behavex

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

* Improvement done when rendering feature background steps in HTML report
* Reporting scenarios that crashed during execution as "Untested" in HTML report (scenarios that crashed were not reported in previous BehaveX versions)
* Enhancement in HTML Report to add feature tags to scenarios
* Contribution from `Axel Furlan <https://github.com/AxelFurlanF>`__ by fixing deprecation warning when using latest Behave version (1.2.6) `PR 116 <https://github.com/hrcorval/behavex/pull/116>`_ (Thanks Axel!!)

FIXES:

* Fixed console summary, to properly report the number of scenarios executed
* Fix done when executing features in parallel, as not all features where considered for execution
* Fixed JUnit reports to properly report all executed scenarios (as some of them were missing)

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

* Updating license information

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

* First public version of behavex-images library


Version History
===============================================================================

-------------------------------------------------------------------------------
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!!)

-------------------------------------------------------------------------------
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)

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

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