- 21 Feb, 2020 1 commit
-
-
Jason Simmons authored
The next engine roll will introduce --lazy-async-stacks, which affects the contents of stack traces. This updates test expectations to match both the old and new stack trace formats.
-
- 01 May, 2019 1 commit
-
-
Jacob Richman authored
Make FlutterError objects more structured so they can be displayed better in debugging tools such as Dart DevTools.
-
- 28 May, 2018 1 commit
-
-
Danny Tuppeny authored
-
- 18 Jan, 2018 1 commit
-
-
jcollins-g authored
* Ignore extraneous error messages outside of one skipped test * Fix analysis error
-
- 07 Oct, 2017 1 commit
-
-
Ian Hickson authored
Also: * Provide a better message when you lerp from infinity to finity constraints. * Make the striped marker support RTL. * By popular demand, dump a warning to the console the first time a particular Flex overflows. (Resets on hot reload.)
-
- 12 Apr, 2017 1 commit
-
-
Ian Hickson authored
* Fix tests to use Ahem, and helpful changes around that - Fix fonts that had metric-specific behaviours. - LiveTestWidgetsFlutterBinding.allowAllFrames has been renamed to LiveTestWidgetsFlutterBinding.framePolicy. - LiveTestWidgetsFlutterBinding now defaults to using a frame policy that pumps slightly more frames, to animate the pointer crosshairs. - Added "flutter run --use-test-fonts" to enable Ahem on devices. - Changed how idle() works to be more effective in live mode. - Display the test name in live mode (unless ahem fonts are enabled). - Added a toString to TextSelectionPoint. - Style nit fixes. * Roll engine to get Ahem changes. * Update tests for dartdoc changes. * Fix flutter_tools tests
-
- 31 Jan, 2017 1 commit
-
-
Ian Hickson authored
These tests would fail sometimes when run locally. Since they happen to also be the ones that are flaky on bots, maybe there's some relationship, even though the failure mode on bots is different. In any case, this removes a variable.
-
- 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.
-