Skip to content

Latest commit

 

History

History
174 lines (106 loc) · 7.34 KB

CHANGES.rst

File metadata and controls

174 lines (106 loc) · 7.34 KB
Raw

Version History

Version: 3.2.0

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 by fixing deprecation warning when using latest Behave version (1.2.6) PR 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)

Version: 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
  • 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
  • Improvement done when parallel execution cannot be launched due to duplicated scenario names, by throwing an error exit code Issue #86

FIXES:

  • Fix done when logging exceptions in environment.py module
  • Fix done when processing the tags associated to scenario outline examples. Issue #85
  • Fix done to detect and process scenarios written in different languages (Scenario detection does not work for Non-English languages). Issue #77
  • Fix done to properly render step.text in HTML report. Issue #79
  • Fix done when parsing empty feature files.

CONTRIBUTORS:

  • Contribution from seb providing the fix to an issue when parsing tags associated to scenario outline examples (Thanks!!)

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

Version: 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

Version: 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

Version: 1.5.11

ENHANCEMENTS:

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

Version: 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

Version: 1.5.9

FIXES:

  • Another encoding fix applied to the HTML report to avoid breaking it on failing scenarios

NOTES:

  • We apologize for all the previous versions that were generated in such a short period of time. We have been working on including all requests from BehaveX users, and we were missing some of them (so we created new versions), and we did some mistakes in the meantime. We will organize to make it better next time

CONTRIBUTIONS:

Version: 1.5.8

FIXES:

  • Adding pending encoding fix to leave everything up and running smoothly

Version: 1.5.7

FIXES:

  • Reverting back implementation to normalize scenario names to be backward compatible
  • Fixing additional encoding issues reported by customers

Version: 1.5.6

FIXES:

  • Fixing side efect with "--rerun-failures (or -rf)" argument that was not considered in local tests

Version: 1.5.5

ENHANCEMENTS:

  • Small refactoring over the "--rerun-failures (or -rf)" argument functionality, to store the file with failures into the root folder instead of the output folder, avoiding the file to get deleted after a re-execution.

DOCUMENTATION:

  • Adding documentation to re-execute failing scenarios.

Version: 1.5.4

ENHANCEMENTS:

  • Fixed issue with scenario outlines containing quotes in description (scenario name not properly parsed)
  • Fixed encoding issues with step descriptions in HTML report
  • Enabled wrapper to run with latest python versions

Version: 1.5.3

ENHANCEMENTS:

  • Added support for examples arguments in scenario outline descriptions

DOCUMENTATION:

  • Adding HTML report screenshots to documentation