- 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
-
- 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
-
- 09 Sep, 2016 1 commit
-
-
Chinmay Garde authored
In that they never create a window with an OpenGL context and the works.
-
- 22 Aug, 2016 1 commit
-
-
Chris Bracken authored
If the input test script contains a bad import, sky_shell will fail to execute main(), in which case a connection to /runner is never established and the _ServerInfo.socket never completes. This change works around this by issuing a request on /shutdown when sky_shell exits.
-
- 05 Aug, 2016 1 commit
-
-
Chris Bracken authored
This reduces dependence on machine-specific font configuration, making tests a bit more reproducible.
-
- 04 Aug, 2016 1 commit
-
-
Chris Bracken authored
-
- 22 Jun, 2016 1 commit
-
-
Adam Barth authored
We need https://github.com/dart-lang/coverage/issues/100 to be fixed before this will be useful. Fixes #2342
-
- 09 Jun, 2016 1 commit
-
-
Adam Barth authored
Fixes #4059
-
- 07 Jun, 2016 1 commit
-
-
Devon Carew authored
* refactor the --resident run option into a separate file * update daemon to run --resident apps * re-plumbing daemon start * send app logs * update tests * review changes * fix test runner * remove PackageMap.createGlobalInstance; rely on the ctor * review comments
-
- 23 May, 2016 1 commit
-
-
Devon Carew authored
-
- 18 May, 2016 1 commit
-
-
Chinmay Garde authored
-
- 16 May, 2016 1 commit
-
-
Ian Hickson authored
This makes it possible to substitute 'flutter run' for 'flutter test' and actually watch a test run on a device. For any test that depends on flutter_test: 1. Remove any import of 'package:test/test.dart'. 2. Replace `testWidgets('...', (WidgetTester tester) {` with `testWidgets('...', (WidgetTester tester) async {` 3. Add an "await" in front of calls to any of the following: * tap() * tapAt() * fling() * flingFrom() * scroll() * scrollAt() * pump() * pumpWidget() 4. Replace any calls to `tester.flushMicrotasks()` with calls to `await tester.idle()`. There's a guarding API that you can use, if you have particularly complicated tests, to get better error messages. Search for TestAsyncUtils.
-
- 03 May, 2016 1 commit
-
-
Devon Carew authored
* fix analysis errors * review comments; fix test * re-add an export for debugPrint
-
- 28 Mar, 2016 1 commit
-
-
Adam Barth authored
The .packages file is replacing the packages directory of symlinks.
-
- 14 Mar, 2016 2 commits
-
-
Hixie authored
-
Ian Hickson authored
-
- 11 Mar, 2016 1 commit
-
-
Ian Hickson authored
Well, all the easy ones, anyway. For some reason `// ignore:` isn't working for me so I've disabled lints that need that. Also disabled those that require a ton of work (which I'm doing, but not in this PR, to keep it reviewable). This adds: - avoid_init_to_null - library_names - package_api_docs - package_names - package_prefixed_library_names - prefer_is_not_empty - sort_constructors_first - sort_unnamed_constructors_first - unnecessary_getters_setters
-
- 03 Mar, 2016 1 commit
-
-
Adam Barth authored
This patch switches us from using our previous hacking approach to integrating with package:test to using the new PlatformPlugin interface.
-