flutter/dev/benchmarks/platform_views_layout
Greg Spencer ab2b0851a2
Add smoke tests for all the examples, fix 17 broken examples. (#89021)
This adds a smoke test for every single API example. It also fixes 17 tests that had bugs in them, or were otherwise broken, and even fixes one actual bug in the framework, and one limitation in the framework.

The bug in the framework is that NetworkImage's _loadAsync method had await response.drain<List<int>>();, but if the response is null, it will throw a cryptic exception saying that Null can't be assigned to List<int>. The fix was just to use await response.drain<void>(); instead.

The limitation is that RelativePositionedTransition takes an Animation<Rect> rect parameter, and if you want to use a RectTween with it, the value emitted there is Rect?, and one of the examples was just casting from Animation<Rect> to Animation<Rect?>, which is invalid, so I modified RelativePositionedTransition to take a Rect? and just use Rect.zero if the rect is null.
2021-09-28 09:32:06 -07:00
..
android [gradle] Unlock all configurations if a local engine is used (#83635) 2021-06-01 13:19:03 -07:00
ios Migrate iOS project to Xcode 13 compatibility (#90304) 2021-09-22 13:23:05 -07:00
lib Enable library_private_types_in_public_api lint (#81578) 2021-05-10 16:26:16 -07:00
test_driver Reland eliminate timeouts from integration tests (#85141) 2021-06-23 13:08:51 -07:00
pubspec.yaml Add smoke tests for all the examples, fix 17 broken examples. (#89021) 2021-09-28 09:32:06 -07:00
README.md ✒ Spell Check All .md Files Related to Flutter 💙 (#61564) 2020-07-22 18:23:47 -07:00

platform_views_layout

Scrolling benchmark

To run the scrolling benchmark on a device:

flutter drive --profile test_driver/scroll_perf.dart

Results should be in the file build/platform_views_scroll_perf.timeline_summary.json.

More detailed logs should be in build/platform_views_scroll_perf.timeline.json.

Startup benchmark

To measure startup time on a device:

flutter run --profile --trace-startup

The results should be in the logs.

Additional results should be in the file build/start_up_info.json.