- 22 Oct, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 21 Sep, 2017 1 commit
-
-
xster authored
* round 3 * partially address comments * merge * review notes * review * review * review
-
- 14 Jul, 2017 1 commit
-
-
Phil Quitslund authored
* Quiet debug test runner output when in machine mode. See: https://github.com/flutter/flutter-intellij/issues/1176 * json => machine
-
- 30 Jun, 2017 1 commit
-
-
Brian Slesinsky authored
This adds a way to run only a subset of the tests. (The new flags do the same thing as 'pub run test'.)
-
- 23 Jun, 2017 1 commit
-
-
Ian Hickson authored
The main purpose of this PR is to make it so that when you set the initial route and it's a hierarchical route (e.g. `/a/b/c`), it implies multiple pushes, one for each step of the route (so in that case, `/`, `/a`, `/a/b`, and `/a/b/c`, in that order). If any of those routes don't exist, it falls back to '/'. As part of doing that, I: * Changed the default for MaterialApp.initialRoute to honor the actual initial route. * Added a MaterialApp.onUnknownRoute for handling bad routes. * Added a feature to flutter_driver that allows the host test script and the device test app to communicate. * Added a test to make sure `flutter drive --route` works. (Hopefully that will also prove `flutter run --route` works, though this isn't testing the `flutter` tool's side of that. My main concern is over whether the engine side works.) * Fixed `flutter drive` to output the right target file name. * Changed how the stocks app represents its data, so that we can show a page for a stock before we know if it exists. * Made it possible to show a stock page that doesn't exist. It shows a progress indicator if we're loading the data, or else shows a message saying it doesn't exist. * Changed the pathing structure of routes in stocks to work more sanely. * Made search in the stocks app actually work (before it only worked if we happened to accidentally trigger a rebuild). Added a test. * Replaced some custom code in the stocks app with a BackButton. * Added a "color" feature to BackButton to support the stocks use case. * Spaced out the ErrorWidget text a bit more. * Added `RouteSettings.copyWith`, which I ended up not using. * Improved the error messages around routing. While I was in some files I made a few formatting fixes, fixed some code health issues, and also removed `flaky: true` from some devicelab tests that have been stable for a while. Also added some documentation here and there.
-
- 20 Jun, 2017 1 commit
-
-
Brian Slesinsky authored
(The Flutter plugin will use this to update the UI with test progress.)
-
- 15 Jun, 2017 1 commit
-
-
Brian Slesinsky authored
- remove unused collector parameter - clarify a comment - inline _currentPackageTestDir
-
- 13 Jun, 2017 2 commits
-
-
Brian Slesinsky authored
And add comments explaining why.
-
Brian Slesinsky authored
Currently this just prints the observatory URL as a JSON event. Refactored the code to make this fit in.
-
- 05 May, 2017 1 commit
-
-
Todd Volkert authored
Builds on engine fixes to #9813 Also fixes #7366
-
- 04 May, 2017 1 commit
-
-
Todd Volkert authored
-
- 03 May, 2017 2 commits
-
-
Todd Volkert authored
This reverts commit 9f5fa31e.
-
Todd Volkert authored
-
- 04 Apr, 2017 1 commit
-
-
Todd Volkert authored
-
- 31 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
* add @required when there's an assert not null * address review comments
-
- 28 Mar, 2017 1 commit
-
-
Phil Quitslund authored
* Bump to Dart SDK 1.23.0-dev.10 * allows us to understand flutter usage via telemetry * brings in `@immutable` Fixes: #9042 * completer fix * Update to platform 1.1.1.
-
- 15 Mar, 2017 1 commit
-
-
Alexandre Ardhuin authored
-
- 04 Mar, 2017 1 commit
-
-
Chris Bracken authored
-
- 16 Feb, 2017 1 commit
-
-
Ian Hickson authored
This assumes a fix to https://github.com/dart-lang/test/issues/542 The timeout added in this patch is a workaround for https://github.com/dart-lang/coverage/issues/165
-
- 14 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 06 Feb, 2017 1 commit
-
-
Jacob Richman authored
* Small Flutter strong mode cleanup fixes. These are cases where strong mode down cast composite errors generally indicated cases that would performance or correctness issues if Flutter code was run in a strong mode VM. * Fix Command API so that it is always in terms of Map<String,String>. * Fix typedef
-
- 28 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 24 Jan, 2017 1 commit
-
-
Todd Volkert authored
-
- 23 Jan, 2017 2 commits
-
-
Ian Hickson authored
Make debugging tests in a debugger easier. Fixes https://github.com/flutter/flutter/issues/163
-
Ian Hickson authored
...now that we have generic methods, their types need to be specified too.
-
- 21 Jan, 2017 1 commit
-
-
Ian Hickson authored
-
- 20 Jan, 2017 1 commit
-
-
Ian Hickson authored
This brings the feature back, since removing it broke one of our more exotic sets of customers.
-
- 19 Jan, 2017 2 commits
-
-
Ian Hickson authored
Also, defer to test package for throttling (this will require a test package update as well). Also, add a lot more instrumentation to --verbose mode for tests, and fix minor trivial things here and there, and add error handling in more places. Also, refactor how coverage works to be simpler and not use statics.
-
Todd Volkert authored
When a machine is heavily loaded, it can severely delay the time it takes for the OS to start a process once it's asked to do so. Our 5 second timeout that we were giving the test process to connect to the test harness seemed like plenty of time, were it not for the fact that the test process itself was not being started in time when CPU throttling was in effect. This change updates the test timeout to begin counting only once the test process has been started. We keep the original timeout in play in the event that the test process *never* starts up for some reason, but we up that timeout value to 5 minutes.
-
- 12 Jan, 2017 1 commit
-
-
Todd Volkert authored
Previously, it was possible for the test harness to bail and the test runner to complete before the platform plugin triggered the collection of coverage data. This fixes the race condition such that the pending coverage collection task is recorded immediately after starting the process.
-
- 10 Jan, 2017 2 commits
-
-
Adam Barth authored
We now produce a more reasonable error message when we're missing the flutter_test dependency in a test. Also, remove the flutter_tools stack traces when the engine dies. Fixes #6187
-
Jason Simmons authored
Fixes https://github.com/flutter/flutter/issues/7351 When a test runs to completion, the test harness closes the stream side of the StreamChannel, causing the sink side to be closed as well. So by the time we receive a test result of completed/harnessBailed, the controller sink has been closed.
-
- 09 Jan, 2017 1 commit
-
-
Todd Volkert authored
This ensures that accidental usages of dart:io's file API don't creep in over time.
-
- 07 Jan, 2017 1 commit
-
-
Todd Volkert authored
This removes direct file access from within flutter_tools in favor of using `package:file` via a `FileSystem` that's accessed via the `ApplicationContext`. This lays the groundwork for us to be able to easily swap out the underlying file system when running Flutter tools, which will be used to provide a record/replay file system, analogous to what we have for process invocations.
-
- 15 Dec, 2016 2 commits
-
-
Ian Hickson authored
-
Ian Hickson authored
-
- 13 Dec, 2016 1 commit
-
-
Chinmay Garde authored
-
- 05 Dec, 2016 1 commit
-
-
Chinmay Garde authored
It is not enabled by default in the VM because applications not launched via the tools may try to connect with the debugger. This causes the debugger and the IDE to hang on Mac.
-
- 30 Nov, 2016 1 commit
-
-
Todd Volkert authored
With this change, they're run via instance methods on an object obtained through the context. This will allow us to substitute that object in tests with replay/record versions to allow us to mock out the os-layer in tests.
-
- 18 Nov, 2016 1 commit
-
-
Todd Volkert authored
-