Open nateshmbhat opened 4 years ago
We are thinking about something like generating tests for each widget annotated with @framyWidget for each screensize. Although at this point it is a very foggy idea in my head 😀.
Is this something you mean?
Yes this could greatly help :)
Copied commment of @kg551915 from another thread showing a great example of how it could work:
You know what would be super awesome, if Framy automatically displayed only screens that contain errors based on preset data. Such that, 'Okay, iPhone X overflows on WidgetX using PresetX'.
So that instead of having to manually walk-through all devices and all presets, Framy can just show you the information you care about. Allowing developers to quickly see where they need to go to focus their energy and time. Personally, such a feature would save even more time (on top of what Framy is already offering) and be invaluable to developers.
The hope was that device preview output errors somewhere and those could just be consumed by Framy.
Many screens have overflow issues which the devs realize only after they run the app on a smaller device. So grouping screens which can potentially cause overflow issues could be helpful.
I am not sure how you can implement this though. One way is to somehow pump the widget and expect for an overflow exception and parse the error string to check for ui errors.
blocked by #10 #9