Isn't ListTile a Material widget? Should the equivalent in Cupertino be based on CupertinoListTile instead?

Done, simplified the doc comment. Thank you!

Good question! TestListTile is not actually a Material ListTile — it is a minimal widget (only depends on package:flutter/widgets.dart) that was created specifically as a lightweight tap target for semantics testing (see #177415). The test here checks MergeSemantics + CupertinoSwitch behavior, not list tile behavior itself.

Replacing it with CupertinoListTile would introduce a heavier StatefulWidget with animations and background color changes, which could make this unrelated semantics test more fragile. So I think keeping the minimal TestListTile is the safer choice here.

I think you should replace the words "ListTile" with "CupertinoListTile" here in the docs, even though it's not based on either. That's what this class should be approximating here in Cupertino.

Nit: Link [CupertinoListTile].

The current implementation uses unsafe casts which could throw a TypeError or RangeError if the MethodCall arguments do not match the expected structure. Using Dart 3 pattern matching provides a more robust and readable way to extract these arguments, adhering to the principle of optimizing for readability.

To be consistent with other methods in TestBorder (like getInnerPath, getOuterPath, and paint), the scale method should log its call. This ensures that tests can verify if the border was scaled as expected, following the principle of doing things right when they are written.

  ShapeBorder scale(double t) {
    onLog('scale $t');
    return TestBorder(onLog);
  }