ogurets is a Gherkin + Cucumber implementation in Dart, focused on making your life writing tests as easy as possible, with the minimum of boilerplate fuss. ogurets_flutter is a flutter extension to ogurets which adds support for:
dev_dependencies section in your
or whichever is the higher version you see on this page.
If you wish to control the flutter run via your own command line build, then the important environment variables are the same as ogurets but with the extension of:
ogurets flutter cannot be used from the command line tool
flutter driver because it needs to know what
the observatory port is. If you wish to include it in your test runs, just use Dart itself and run your
_test.dart runner, it will start your main app and control it.
If you wish to use the
flutter driver command line tool, use ogurets directly and just enable the driver in
an instance of your own to make it available to your steps.
The other reason you may not need to use this mechanism is if you want to keep your app
running while you are writing your test, in which case start it with
flutter run, take note of the Observatory
Port and set it in an environment variable:
VM_SERVICE_URL. If ogurets_flutter sees that when it starts, it will
simply use it, but restart functionality will be turned off. Only use this when testing scenario by scenario and
you are writing and changing code and restarting the app yourself or where the state isn't important.
We also thank Jon Samwell of Flutter Gherkin for his idea (and core code) for managing the run of the the application.
Added in support for additional parameters for flutter build runs (flavours, device ids and generic additional parameters).
Added in override support for which file to actually run
This is the first release of
ogurets_flutter. As per documentation.
Add this to your package's pubspec.yaml file:
dependencies: ogurets_flutter: ^1.2.1
You can install packages from the command line:
$ flutter pub get
Alternatively, your editor might support
flutter pub get.
Check the docs for your editor to learn more.
Now in your Dart code, you can use:
Describes how popular the package is relative to other packages. [more]
Code health derived from static analysis. [more]
Reflects how tidy and up-to-date the package is. [more]
Weighted score of the above. [more]
We analyzed this package on Aug 18, 2019, and provided a score, details, and suggestions below. Analysis was completed with status completed using:
Detected platforms: Flutter
References Flutter, and has no conflicting libraries.
Document public APIs. (-0.23 points)
37 out of 38 API elements have no dartdoc comment.Providing good documentation for libraries, classes, functions, and other API elements improves code readability and helps developers find and use your API.
lib/flutter_autorun.dart. (-0.50 points)
lib/flutter_autorun.dart reported 1 hint:
line 106 col 24: Avoid using braces in interpolation when not needed.
lib/ogurets_flutter.dart. (-0.50 points)
lib/ogurets_flutter.dart reported 1 hint:
line 6 col 8: Unused import: 'dart:math'.
flutter format to format
The package description is too short. (-20 points)
Add more detail to the
description field of
pubspec.yaml. Use 60 to 180 characters to describe the package, what it does, and its target use case.
Maintain an example. (-10 points)
Create a short demo in the
example/ directory to show how to use this package.
Common filename patterns include
ogurets_flutter.dart. Packages with multiple examples should provide
For more information see the pub package layout conventions.
|Dart SDK||>=2.2.0 <3.0.0|