Integration_test package support and null-safety

.flutter-plugins

@@ -0,0 +1,2 @@
+# This is a generated file; do not edit or check into version control.
+integration_test=C:\\Google\\flutter\\packages\\integration_test\\

.flutter-plugins-dependencies

@@ -0,0 +1 @@
+{"info":"This is a generated file; do not edit or check into version control.","plugins":{"ios":[{"name":"integration_test","path":"C:\\\\Google\\\\flutter\\\\packages\\\\integration_test\\\\","dependencies":[]}],"android":[{"name":"integration_test","path":"C:\\\\Google\\\\flutter\\\\packages\\\\integration_test\\\\","dependencies":[]}],"macos":[],"linux":[],"windows":[],"web":[]},"dependencyGraph":[{"name":"integration_test","dependencies":[]}],"date_created":"2021-10-27 20:12:58.071212","version":"2.5.3"}

.gitignore

@@ -8,3 +8,6 @@ build/
 ios/.generated/
 ios/Flutter/Generated.xcconfig
 ios/Runner/GeneratedPluginRegistrant.*
+
+node_modules
+package-lock.json

.vscode/launch.json

@@ -5,16 +5,33 @@
   "version": "0.2.0",
   "configurations": [
     {
-      "name": "Flutter",
+      "name": "Debug integration_test app",
       "request": "launch",
-      "type": "dart"
+      "type": "dart",
+      "cwd": "example_with_integration_test/",
+    },
+    {
+      "name": "Debug integration_test example tests",
+      "program": "test_driver/integration_test_driver.dart",
+      "cwd": "example_with_integration_test/",
+      "request": "launch",
+      "type": "dart",
+      "args": [
+        "--target=integration_test/gherkin_suite_test.dart",
+      ],
     },
     {
-      "name": "Debug example tests",
-      "program": "app_test.dart",
-      "cwd": "example/test_driver",
+      "name": "Debug flutter_driver app",
       "request": "launch",
       "type": "dart",
-    }
+      "cwd": "example_with_flutter_driver/",
+    },
+    {
+      "name": "Debug flutter_driver example tests",
+      "program": "test_harness.dart",
+      "cwd": "example_with_flutter_driver/test_driver",
+      "request": "launch",
+      "type": "dart",
+    },
   ]
 }

.vscode/settings.json

@@ -0,0 +1,13 @@
+{
+    "cSpell.words": [
+        "Errored",
+        "Serializable",
+        "agnostically",
+        "microtask",
+        "multiline",
+        "pubspec",
+        "scrollable",
+        "todos",
+        "writeln"
+    ]
+}

CHANGELOG.md

@@ -1,3 +1,166 @@
+## [3.0.0-rc.6] - 27/10/2021
+
+- BREAKING CHANGE: Made `appMainFunction` return a `Future<void>` so it can be async
+- Fix: #159: Swipe step not working
+- Ensure Hook.onBeforeRun is called before the run starts
+- Set Frame policy- defaults to `LiveTestWidgetsFlutterBindingFramePolicy.benchmarkLive` to slightly improve performance
+
+## [3.0.0-rc.5] - 22/06/2021
+
+- Ensure scenario support files (world etc) as always disposed ensure when test throws error 
+
+## [3.0.0-rc.4] - 21/06/2021
+
+- Removed debug code
+
+## [3.0.0-rc.3] - 21/06/2021
+
+- POSSIBLE BREAKING CHANGE: Removed tap call before enterText is invoked in `WidgetTesterAppDriverAdapter` this was due to the fact that it opens the on-screen keyboard which is not closed after the text is entered so it could be blocking further controls from view.
+- Fix: #150: Better handling of JSON strings in multiline string segments in feature files
+- Fix: #141 & #128: Added example of how to generate html report from json report output and fixed all scenarios ending up in the last feature section of the json report
+
+## [3.0.0-rc.2] - 21/06/2021
+
+- Fixed late initialization error when invoking hooks
+- Updated float parameter parser so an exception is not thrown during parsing
+
+## [3.0.0-rc.1] - 25/05/2021
+
+  HUGE update so that the library now works and favours the flutter integration_test package over flutter_driver.  Unfortunately, this will be breaking change to existing users but it has many benefits such as a huge speed and stability improvements.
+
+# BREAKING CHANGES
+
+- `Table` has been renamed to `GherkinTable` to avoid naming clashes
+
+In order to progress this library and add support for the new integration_test package various things have had to be changed to enable this will still supporting Flutter Driver.  The big of which is removing Flutter Driver instance from the `FlutterWorld` instance in favour of an adapter approach whereby driving of the app (whether that is via `flutter_driver` or `WidgetTester`) becomes agnostic see `https://github.com/jonsamwell/flutter_gherkin/blob/f1fb2d4a632362629f5d1a196a0c055f858ad1d7/lib/src/flutter/adapters/app_driver_adapter.dart`.
+
+- `FlutterDriverUtils` has been removed, use `world.appDriver` instead.  You can still access the raw driver if needed via `world.appDriver.nativeDriver`
+- If you are using a custom world object and still want to use Flutter Driver it will need to extend `FlutterDriverWorld` instead of `FlutterWorld` this will give you type safety on the `world.appDriver.nativeDriver` property
+
+The change to use the `integration_test` package is a fundamentally different approach.  Where using the `flutter_driver` implementation your app is launch in a different process and then controlled by remote RPC calls from flutter driver in a different process.  Using the new `integration_test` package your tests surround your app and become the app themselves.  This removes the need for RPC communication from an external process into the app as well as giving you access to the internal state of your app.  This is an altogether better approach, one that is quicker, more maintainable, scalable to device testing labs.  However, it brings with it, its own set of challenges when trying to make this library work with it.  Traditionally this library has evaluated the Gherkin feature files at run time, then used that evaluation to invoke actions against the app under test.  However, as the tests need to surround the app in the `integration_test` view of the world the Gherkin tests need to be generated at development time so they can be complied in to a test app.  Much like `json_serializable` creates classes that are able to work with json data.
+
+### Steps to get going
+
+1. Add the following `dev_dependencies` to your app's `pubspec.yaml` file
+  - integration_test
+  - build_runner
+  - flutter_gherkin
+2. Add the following `build.yaml` to the root of your project. This file allows the dart code generator to target files outside of your application's `lib` folder
+```yaml
+targets:
+  $default:
+    sources:
+      - lib/**
+      - pubspec.*
+      - $package$
+      # Allows the code generator to target files outside of the lib folder
+      - integration_test/**.dart
+```
+3. Add the following file (and folder) `\test_driver\integration_test_driver.dart`.  This file is the entry point to run your tests.  See `https://flutter.dev/docs/testing/integration-tests` for more information.
+```dart
+import 'package:integration_test/integration_test_driver.dart' as integration_test_driver;
+
+Future<void> main() {
+  // The Gherkin report data send back to this runner by the app after
+  // the tests have run will be saved to this directory
+  integration_test_driver.testOutputsDirectory = 'integration_test/gherkin/reports';
+
+  return integration_test_driver.integrationDriver(
+    timeout: Duration(minutes: 90),
+  );
+}
+```
+4. Create a folder call `integration_test` this will eventually contain all your Gherkin feature files and the generated test files.
+5. Add the following file (and folder) `integration_test\features\counter.feature` with the following below contents.  This is a basic feature file that will be transform in to a test file that can run a test against the sample app.
+```
+Feature: Counter
+
+Scenario: User can increment the counter
+  Given I expect the "counter" to be "0"
+  When I tap the "increment" button
+  Then I expect the "counter" to be "1"
+```
+6. Add the following file (and folder) `integration_test\gherkin_suite_test.dart`.  Notice the attribute `@GherkinTestSuite()` this indicates to the code generator to create a partial file for this file with the generated Gherkin tests in `part 'gherkin_suite_test.g.dart';`.  Don't worry about the initial errors as this will disappear when the tests are generated.
+```dart
+import 'package:flutter_gherkin/flutter_gherkin_integration_test.dart'; // notice new import name
+import 'package:flutter_test/flutter_test.dart';
+import 'package:gherkin/gherkin.dart';
+
+// The application under test.
+import 'package:example_with_integration_test/main.dart' as app;
+
+part 'gherkin_suite_test.g.dart';
+
+@GherkinTestSuite()
+void main() {
+  executeTestSuite(
+    FlutterTestConfiguration.DEFAULT([])
+      ..reporters = [
+        StdoutReporter(MessageLevel.error)
+          ..setWriteLineFn(print)
+          ..setWriteFn(print),
+        ProgressReporter()
+          ..setWriteLineFn(print)
+          ..setWriteFn(print),
+        TestRunSummaryReporter()
+          ..setWriteLineFn(print)
+          ..setWriteFn(print),
+        JsonReporter(
+          writeReport: (_, __) => Future<void>.value(),
+        ),
+      ],
+    (World world) => app.main(),
+  );
+}
+```
+7. We now need to generate the test by running the builder command from the command line in the root of your project.  Much like `json_serializable` this will create a `.g.dart` part file that will contain the Gherkin tests in code format which are able to via using the `integration_test` package.
+```
+flutter pub run build_runner build
+```
+8. The errors in the `integration_test\gherkin_suite_test.dart` file should have not gone away and it you look in `integration_test\gherkin_suite_test.g.dart` you will see the coded version of the Gherkin tests described in the feature file `integration_test\features\counter.feature`.
+9. We can now run the test using the below command from the root of your project.
+```
+flutter drive --driver=test_driver/integration_test_driver.dart --target=integration_test/gherkin_suite_test.dart
+```
+10. You can debug the tests by adding a breakpoint to line 12 in `integration_test\gherkin_suite_test.dart` and adding the below to your `.vscode\launch.json` file:
+```json
+{
+  "name": "Debug integration_test",
+  "program": "test_driver/integration_test_driver.dart",
+  "cwd": "example_with_integration_test/",
+  "request": "launch",
+  "type": "dart",
+  "args": [
+    "--target=integration_test/gherkin_suite_test.dart",
+  ],
+}
+```
+11. Custom world need to extend `FlutterWorld` note `FlutterDriverWorld`.
+12. If you change any of the feature files you will need to re-generate the tests using the below command
+```
+# you might need to run the clean command first if you have just changed feature files
+flutter pub run build_runner clean
+
+flutter pub run build_runner build
+```
+
+## [2.0.0] - 25/05/2021
+ * null-safety migration, thanks to @tshedor
+
+## [1.2.0] - 02/05/2021
+
+* Upgraded to the null-safety version of dart_gherkin, as such there are some breaking changes to be aware of (see https://github.com/jonsamwell/dart_gherkin/blob/master/CHANGELOG.md for the full list):
+  - BREAKING CHANGE: Table has been renamed to GherkinTable to avoid naming clashes
+  - BREAKING CHANGE: exitAfterTestRun configuration option has been removed as it depends on importing dart:io which is not available under certain environments (dartjs for example).
+  - BREAKING CHANGE: Reporter->onException() exception parameter is now an object rather than an exception
+  - POSSIBLE BREAKING CHANGE: Feature file discovery has been refactored to abstract it from the external Glob dependency. It now support the three native dart Patterns (String, RegExp & Glob). There is potential here for your patterns to not work anymore due as the default IoFeatureFileAccessor assumes the current directory is the working directory to search from. For the most part this simple regex is probably enough to get you going.
+
+  ```
+  RegExp('features/*.*.feature')
+  ```
+
+* Allow dart-define to be passed to the Flutter build (thanks @Pholey)
+
 ## [1.1.9] - 24/11/2020
 * Fixes #93 & #92 - Error waiting for no transient callbacks from Flutter driver
 * Added option to leave Flutter app under test running when the tests finish see `keepAppRunningAfterTests` configuration property
@@ -258,4 +421,4 @@ When I long press "controlKey" icon for 1500 milliseconds
 
 ## [0.0.1] - 29/10/2018
 
-* Initial working release
+* Initial working release