- 21 Feb, 2019 1 commit
-
-
Alexandre Ardhuin authored
-
- 05 Oct, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 20 Sep, 2018 1 commit
-
-
Greg Spencer authored
This changes the compiler output for gradle to be less verbose and more easily read. This only applies to compilation error messages: other gradle messages will continue to print as before. It also fixes a small problem with the performance measurement printing (see that "7.1s" on it's own line in the original?) so that if something is expected to have multiple lines of output, it prints an initial line, and a "Done" line with the elapsed time, so that it's possible to know what the time applies to. It also updates the spinner to be fancier, at least on platforms other than Windows (which is missing a lot of symbols in its console font). Addresses #17307
-
- 12 Sep, 2018 1 commit
-
-
Alexandre Ardhuin authored
* enable lint unnecessary_new * fix tests * fix tests * fix tests
-
- 16 Aug, 2018 1 commit
-
-
Mikkel Nygaard Ravn authored
-
- 15 Aug, 2018 1 commit
-
-
Ian Hickson authored
* Upgrade everything except matcher. * Roll matcher (and test) * Adjust tests that depend on flutter:test directly to depend on a shim * Require use of package:test shim and remove other references to package:test
-
- 05 Jun, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 02 Feb, 2018 1 commit
-
-
Alexandre Ardhuin authored
-
- 18 Jan, 2018 2 commits
-
-
jcollins-g authored
* Ignore extraneous error messages outside of one skipped test * Fix analysis error
-
Michael Goderbauer authored
-
- 09 Dec, 2017 1 commit
-
-
Ian Hickson authored
...instead of the engine.
-
- 08 Nov, 2017 1 commit
-
-
Alexandre Ardhuin authored
* enable lint prefer_asserts_in_initializer_lists * enable --assert-initializer
-
- 04 Aug, 2017 1 commit
-
-
Ian Hickson authored
Also, add tests to verify that our coverage is actually being tested!
-
- 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'.)
-
- 12 May, 2017 1 commit
-
-
Ian Hickson authored
-
- 13 Apr, 2017 1 commit
-
-
Ian Hickson authored
-
- 22 Mar, 2017 1 commit
-
-
Ian Hickson authored
-
- 13 Mar, 2017 1 commit
-
-
Jason Simmons authored
-
- 10 Mar, 2017 1 commit
-
-
Todd Volkert authored
`all.dart` is no longer needed. Furthermore, it causes tests to be skipped, or to silently fail to run anything. Fixes #7941
-
- 23 Feb, 2017 1 commit
-
-
Phil Quitslund authored
* Bump to test `0.12.20`. Some test `0.12.20` highlights: * introduces `expectLater()` that returns a `Future` that completes when the matcher has finished running * deprecates the `verbose` parameter to `expect()` and the `formatFailure()` (to be removed in `0.13.0`) Otherwise: * to keep up w/ the deprecation of `verbose`, removes `widget_tester` API to pass `verbose` flag (alternatively we could suppress the warning for now) * Update stack manipulation. * Fix framecount.
-
- 14 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 06 Feb, 2017 1 commit
-
-
Michael Goderbauer authored
-
- 03 Feb, 2017 1 commit
-
-
Ian Hickson authored
...and fix bugs that the tests uncovered. WRITE TEST FIND BUG
-
- 31 Jan, 2017 1 commit
-
-
Ian Hickson authored
It was causing the flakiness because it was too short. The default timeout is better.
-
- 10 Jan, 2017 1 commit
-
-
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
-
- 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.
-
- 14 Jun, 2016 1 commit
-
-
Ian Hickson authored
This prevents multiple simultaneous runs of the analyzer from stomping over each other (e.g. multiple runs of 'update-packages'). Certain long-lived commands (like analyze, run, logs) are exempted once they've done enough work to be safe from most stomping action. This still doesn't make us entirely safe from craziness, e.g. if you're half way through an 'update-packages' run and you call 'git pull', who knows what state you'll end up in. But there's only so much one can do. Fixes https://github.com/flutter/flutter/issues/2762
-
- 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.
-