* Revert "Remove references to BindingBase.window (#122119)" This reverts commitc7681f00cf. * Revert "Remove another reference to BindingBase.window (#122341)" This reverts commit6ec4445063. * Revert "Reland (2): Removes single window assumptions from `flutter_test` (#122233)" This reverts commiteb3d317ea0. * Revert "Remove single view assumption from TestViewConfiguration (#122352)" This reverts commit927289fb4e. * Revert "Updates `flutter/test/cupertino` to no longer use `TestWindow` (#122325)" This reverts commit67e17e45f0. * Revert "Updates `flutter/test/gestures` to no longer reference `TestWindow` (#122327)" This reverts commitc2a5111cc0. * Revert "Updates `flutter/test/rendering` to no longer use `TestWindow` (#122347)" This reverts commit28b65e089b. * Revert "Updates `flutter_localizations/test` to stop using `TestWindow` (#122321)" This reverts commit01367d52d7.
microbenchmarks
To run these benchmarks on a device, first run `flutter logs' in one window to see the device logs, then, in a different window, run any of these:
flutter run --release lib/gestures/velocity_tracker_bench.dart
flutter run --release lib/gestures/gesture_detector_bench.dart
flutter run --release lib/stocks/animation_bench.dart
flutter run --release lib/stocks/build_bench.dart
flutter run --release lib/stocks/layout_bench.dart
The results should be in the device logs.
Avoid changing names of the benchmarks
Each microbenchmark is identified by a name, for example, "catmullrom_transform_iteration". Changing the name of an existing microbenchmarks will effectively remove the old benchmark and create a new one, losing the historical data associated with the old benchmark in the process.