- 27 May, 2016 1 commit
-
-
Yegor authored
* modernize `flutter drive` w.r.t. debug/profil/release options * make error message prettier
-
- 09 May, 2016 1 commit
-
-
Devon Carew authored
-
- 04 May, 2016 1 commit
-
-
pq authored
@Hixie: as per our conversation, a little more concise.
-
- 03 May, 2016 1 commit
-
-
Devon Carew authored
* fix analysis errors * review comments; fix test * re-add an export for debugPrint
-
- 04 Apr, 2016 1 commit
-
-
Devon Carew authored
-
- 28 Mar, 2016 1 commit
-
-
Yegor Jbanov authored
Driver returns exit code 0 even when tests fail. This commit fixes it by propagating the exit code set by `package:test`.
-
- 11 Mar, 2016 1 commit
-
-
Hixie authored
Test that flutter analyze catches no error if two imported libraries have the same name. Also, make tests know how to find the flutter root and fix style in one test to be consistent with the rest of the file.
-
- 10 Mar, 2016 1 commit
-
-
Hixie authored
And fix a zillion omissions this uncovered.
-
- 26 Feb, 2016 1 commit
-
-
Yegor Jbanov authored
flutter start's method of finding devices to run the app on is not suitable for flutter drive. This commit also refactors several tool services to allow mocking in unit tests.
-
- 23 Feb, 2016 1 commit
-
-
yjbanov authored
"flutter create" adds option `--with-driver-test` that adds dependencies to `flutter_driver` in `pubspec.yaml` and creates a basic driver test runnable via `flutter drive --target=test_driver/e2e.dart` "flutter drive" new options: - `--keep-app-running` tells the driver to not stop the app after tests are done - `--use-existing-app` tells the driver to not start a new app but use an already running instance
-
- 20 Feb, 2016 1 commit
-
-
yjbanov authored
Runs a test app and a driver test simultaneously, then stops the app. Usage: ``` flutter drive --target=/path/to/test/app.dart ``` This command will look for `/path/to/test/app_test.dart` by convention. We will expand into other ways of discovering tests in the future.
-