Todd Volkert 2ba0deb77a Make runAsync() run in child zone, not root zone (#17359) ... Some APIs (such as the ones in package:test) assume you're running in a child zone of the test zone by attempting to extract information from the zone values. When we run runAsync() in the root zone, those zone values are lost, and such API methods don't work. The solution is to run in a child zone, but with a specification that says to use the Root zone for task scheduling (both timers and microtakss).		2018-05-07 18:33:44 -07:00
..
test_config	Add support for flutter_test_config.dart (#17141)	2018-05-01 12:36:22 -07:00
finders_test.dart	Replace usage of FractionalOffset with Alignment (#12348)	2017-10-02 00:06:24 -07:00
goldens_test.dart	Expose generateTestBootstrap() as public API in test harness (#17290)	2018-05-04 10:31:53 -07:00
matchers_test.dart	Golden file fixes (#17299)	2018-05-07 11:33:41 -07:00
stack_manipulation_test.dart	Declare locals final where not reassigned (flutter_test) (#8569)	2017-03-03 17:51:01 -08:00
test_async_utils_test.dart	Do not swallow exceptions in guarded functions. (#9064)	2017-03-30 09:50:30 -07:00
widget_tester_test.dart	Make runAsync() run in child zone, not root zone (#17359)	2018-05-07 18:33:44 -07:00