Provide testing extension API that matches widgets and returns matched widget information #29375

Activity

1. tvolkert

   added

   customer: espresso

   on Mar 14, 2019
2. jonahwilliams commented on Mar 15, 2019

   

   jonahwilliams

   on Mar 15, 2019

   Contributor

   More actions

   For testing, you likely want information from the semantics tree, this can tell you things such as where to tap/available actions/labels. Example:

   flutter:      └─SemanticsNode#6
   flutter:        │ Rect.fromLTRB(0.0, 100.0, 414.0, 896.0)
   flutter:        │ flags: scopesRoute, namesRoute
   flutter:        │ label: "categories"
   flutter:        │ textDirection: ltr
   flutter:        │ elevation: 12.0
   flutter:        │
   flutter:        └─SemanticsNode#7
   flutter:          │ Rect.fromLTRB(0.0, 0.0, 414.0, 552.0)
   flutter:          │ flags: hasImplicitScrolling
   flutter:          │ scrollExtentMin: 0.0
   flutter:          │ scrollPosition: 0.0
   flutter:          │ scrollExtentMax: 0.0
   flutter:          │
   flutter:          ├─SemanticsNode#8
   flutter:          │   Rect.fromLTRB(0.0, 0.0, 207.0, 184.0)
   flutter:          │   actions: tap
   flutter:          │   flags: isButton, hasEnabledState, isEnabled
   flutter:          │   label: "Studies"
   flutter:          │   textDirection: ltr
   flutter:          │
   

   The semantics tree doesn't correspond 1-1 with Widgets though. And since a Widget is an arbitrary user defined class, we do not have the capability to reflect on or serialize them.
3. goderbauer

   added

   frameworkflutter/packages/flutter repository. See also f: labels.flutter/packages/flutter repository. See also f: labels.

   a: tests"flutter test", flutter_test, or one of our tests"flutter test", flutter_test, or one of our tests

   severe: customer critical

   on Mar 18, 2019
4. Hixie commented on Mar 19, 2019

   

   Hixie

   on Mar 19, 2019

   Contributor

   More actions

   @jacob314's inspector API exposes much of this, would it be sufficient?
5. Hixie

   added this to the GoalsThis milestone has been deleted milestone on Mar 19, 2019
6. goderbauer

   modified the milestones: GoalsThis milestone has been deleted, July 2019 on Mar 20, 2019
7. Hixie

   assigned

   goderbauer

   on Mar 26, 2019
8. adazh commented on May 22, 2019

   

   adazh

   on May 22, 2019

   ContributorAuthor

   More actions

   As discussed with @goderbauer yesterday, for the first version, the matching API will possibly be something like this:
   WidgetInfo matchWidget(SerializableFinder finder), which finds a widget (RenderObject to be accurate?) that matches exactly with the finder, and returns an object containing its properties (we could even start with a minimum set of properties, e.g. runtimeType, valueKey, text, tooltip).

   • How does the matching work?
     First version: it won't be able to match a composite widget. Rather it does exact matching on a widget.
     For example, a Flutter button could be composed by an icon, a Text widget, and may also have multiple layers of widget containers, decorators. Users cannot express "matching a (composite) button widget for me" with the matching API, but could match the Text widget for example.

   Michael, feel free to correct if I'm wrong.

   👍React with 👍1Reacted by Mark Han
9. goderbauer

   closed this as completedin #34440on Jun 19, 2019
10. github-actions commented on Aug 29, 2021

    

    github-actionsbot

    on Aug 29, 2021

    More actions

    This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of flutter doctor -v and a minimal reproduction of the issue.
11. github-actions

    locked as resolved and limited conversation to collaborators on Aug 29, 2021