flutter_gherkin

[3.0.0-rc.17] - 25/07/2022

• Fix #257 - fixed issue when generating a step with a '$' sign in
• Fix #256 - Ensure all exceptions generated when running a step are logged
• Fix #253 - Ensure features with descriptions that span more than one line are parsed correctly
• Fix #252 - Ensure all async code is awaited
• When taking a screenshot on the web use the render element rather than relying on native code that does not work

[3.0.0-rc.16] - 01/07/2022

• Fix #231 - using local coordinate system when taking a screenshot on Android (thanks to @youssef-t for the solution)
• Fix #216 - ensure step exceptions and expect failure results are added as errors to the json report
• Scenarios can now have descriptions which also appear in the json reporter output

NOTE: Due to the above changes generated files will need to be re-generated

flutter pub run build_runner clean
flutter pub run build_runner build --delete-conflicting-outputs

[3.0.0-rc.15] - 28/06/2022

• Exposed frameBindingPolicy on the test runner when running tests which can affect how frames are painted and the speed of the test run, I've removed the default value which might be responsible for #231

[3.0.0-rc.14] - 28/06/2022

• Fix #237 - Ensure everything works on the web

[3.0.0-rc.13] - 27/06/2022

• Fix #235 - fix issue taking a screenshot on an Android device
• Resolved #170: Added example code to ensure json report is save to disk even when the test run fails. Also added script to generate a HTML report from a JSON report

[3.0.0-rc.12] - 24/06/2022

• Fix #222 - escape single quotation marks in data tables

[3.0.0-rc.11] - 24/06/2022

• Fix #231 - Removed the use of explicitly calling pumpAndSettle in the pre-defined steps in favour of the implicit pumpAndSettle calls used in the WidgetTesterAppDriverAdapter.
• Added ability to add a appLifecyclePumpHandler to override the default handler that determines how the app is pumped during lifecycle events. Useful if your app has a long splash screen etc. Parameter is on executeTestSuite.
• Added ability to ensure feature paths are relative when generating reports useAbsolutePaths on the GherkinTestSuite attribute

• BREAKING CHANGE: The parameters on executeTestSuite are now keyed to allow for the above changes

A lot of new changes in this update.

• Test scenario's can be retried, in the configuration it is possible to specify the amount of step retries. (#218).
• It is now possible to the see if the scenario has passed in the JSON report and in the afterScenario hook (#201).
• When a test fails, it does not automatically fail in the test framework. The other steps will be skipped and show up in the JSON report. This will now not cause any app inconsistencies with error pop-ups (#182).
• Steps that have been skipped, are now also being recorded through the reporters and hooks (#179).
• Documentation on the feature folder location has been improved (#174).

• Fix: #172: Fix for the StdoutReporter when running against the web