Available policies for how a LiveTestWidgetsFlutterBinding should paint frames.
- benchmark → const LiveTestWidgetsFlutterBindingFramePolicy
Ignore any request to schedule a frame.
This is intended to be used by benchmarks (hence the name) that drive the pipeline directly. It tells the binding to entirely ignore requests for a frame to be scheduled, while still allowing frames that are pumped directly to run (either by using WidgetTester.pumpBenchmark or invoking Window.onBeginFrame and Window.onDrawFrame).
The SchedulerBinding.hasScheduledFrame property will never be true in this mode. This can cause unexpected effects. For instance, WidgetTester.pumpAndSettle does not function in this mode, as it relies on the SchedulerBinding.hasScheduledFrame property to determine when the application has "settled".
- fadePointers → const LiveTestWidgetsFlutterBindingFramePolicy
Show pumped frames, and additionally schedule and run frames to fade out the pointer crosshairs and other debugging information shown by the binding.
This can result in additional frames being pumped beyond those that the test itself requests, which can cause differences in behavior.
- fullyLive → const LiveTestWidgetsFlutterBindingFramePolicy
Show every frame that the framework requests, even if the frames are not explicitly pumped.
This can help with orienting the developer when looking at heavily-animated situations, and will almost certainly result in additional frames being pumped beyond those that the test itself requests, which can cause differences in behavior.
- onlyPumps → const LiveTestWidgetsFlutterBindingFramePolicy
Strictly show only frames that are explicitly pumped. This most closely matches the behavior of tests when run under
→ const List<
A constant List of the values in this enum, in order of their declaration.