anchor.diff:    /// 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]).
  +  ///
  +  /// This allows all frame requests from the engine to be serviced, and allows
  +  /// all frame requests that are artificially triggered to be serviced, but
  +  /// ignores [scheduleFrame] requests from the framework.
  +  /// Therefore animation won't run for this mode because the framework
  +  /// generates an animation by requesting new frames.
     ///
     /// The [SchedulerBinding.hasScheduledFrame] property will never be true in
     /// this mode. This can cause unexpected effects. For instance,
  
positive.code: /// frames.
  ///
  /// These values are set on the binding's
  /// [LiveTestWidgetsFlutterBinding.framePolicy] property. The default is
  /// [fadePointers].
  enum LiveTestWidgetsFlutterBindingFramePolicy {
    /// Strictly show only frames that are explicitly pumped. This most closely
    /// matches the behavior of tests when run under `flutter test`.
    onlyPumps,
  
    /// 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.
    fadePointers,
  
    /// 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
  
negative.code:   bool _viewNeedsPaint = false;
    bool _runningAsyncTasks = false;
  
    /// The strategy for [pump]ing and requesting new frames.
    ///
    /// The policy decides whether [pump] (with a duration) pumps a single frame
    /// (as would happen in a normal test environment using
    /// [AutomatedTestWidgetsFlutterBinding]), or pumps every frame that the
    /// system requests during an asynchronous pause (as would normally happen
    /// when running an application with [WidgetsFlutterBinding]).
    ///
    /// {@macro flutter.flutter_test.frame_policy}
    ///
    /// See [LiveTestWidgetsFlutterBindingFramePolicy].
    LiveTestWidgetsFlutterBindingFramePolicy framePolicy = LiveTestWidgetsFlutterBindingFramePolicy.fadePointers;
  
    @override
  