anchor.diff:    /// system identifies the gesture as a fling, consider using [fling] instead.
     ///
     /// {@template flutter.flutter_test.drag}
  -  /// By default, if the x or y component of offset is greater than [kTouchSlop], the
  -  /// gesture is broken up into two separate moves calls. Changing 'touchSlopX' or
  -  /// `touchSlopY` will change the minimum amount of movement in the respective axis
  -  /// before the drag will be broken into multiple calls. To always send the
  -  /// drag with just a single call to [TestGesture.moveBy], `touchSlopX` and `touchSlopY`
  -  /// should be set to 0.
  +  /// By default, if the x or y component of offset is greater than
  +  /// [kDragSlopDefault], the gesture is broken up into two separate moves
  +  /// calls. Changing `touchSlopX` or `touchSlopY` will change the minimum
  +  /// amount of movement in the respective axis before the drag will be broken
  +  /// into multiple calls. To always send the drag with just a single call to
  +  /// [TestGesture.moveBy], `touchSlopX` and `touchSlopY` should be set to 0.
     ///
     /// Breaking the drag into multiple moves is necessary for accurate execution
     /// of drag update calls with a [DragStartBehavior] variable set to
     /// [DragStartBehavior.start]. Without such a change, the dragUpdate callback
     /// from a drag recognizer will never be invoked.
     ///
  -  /// To force this function to a send a single move event, the 'touchSlopX' and
  -  /// 'touchSlopY' variables should be set to 0. However, generally, these values
  +  /// To force this function to a send a single move event, the `touchSlopX` and
  +  /// `touchSlopY` variables should be set to 0. However, generally, these values
     /// should be left to their default values.
     /// {@endtemplate}
     Future<void> drag(
  
positive.code:   /// opposite direction of the fling (e.g. dragging 200 pixels to the right,
    /// then fling to the left over 200 pixels, ending at the exact point that the
    /// drag started).
    Future<void> fling(
      Finder finder,
      Offset offset,
  
negative.code:   /// If the middle of the widget is not exposed, this might send
    /// events to another object.
    ///
    /// {@template flutter.flutter_test.fling}
    /// This can pump frames.
    ///
    /// Exactly 50 pointer events are synthesized.
    ///
    /// The `speed` is in pixels per second in the direction given by `offset`.
    ///
    /// The `offset` and `speed` control the interval between each pointer event.
    /// For example, if the `offset` is 200 pixels down, and the `speed` is 800
    /// pixels per second, the pointer events will be sent for each increment
    /// of 4 pixels (200/50), over 250ms (200/800), meaning events will be sent
    /// every 1.25ms (250/200).
    ///
    /// To make tests more realistic, frames may be pumped during this time (using
    /// calls to [pump]). If the total duration is longer than `frameInterval`,
    /// then one frame is pumped each time that amount of time elapses while
    /// sending events, or each time an event is synthesized, whichever is rarer.
    ///
    /// See [LiveTestWidgetsFlutterBindingFramePolicy.benchmarkLive] if the method
    /// is used in a live environment and accurate time control is important.
    ///
    /// The `initialOffset` argument, if non-zero, causes the pointer to first
    /// apply that offset, then pump a delay of `initialOffsetDelay`. This can be
  