Replies: 1 comment
-
Hello, 'RosarioPulella! Thanks for submitting a new feature request. I've automatically added a vote 👍 reaction to help get things started. Other community members can vote to help us prioritize this feature in the future! |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the problem this feature would solve
As a maintainer, I want a way to quickly see the visual appearance of all the controls so that I can check for visual issues that are hard to find or catch threw automation.
Describe the solution
Add a script or tool in the repository that can be easily run ( maybe a cake script), that will initialize controls in as many relevant UI contexts as possible (In a window/ScrollViewe/Fullscreen/different container sizes?), with as many configurations of the control as possible, and take screen shots of every of every combination.
We can call these combinations Scenes.
The script can be run and once it is complete the screen shots of the Scenes would cover more UI scenarios per controls than any reviewer normally would "clicking around" and "trying things" and they can be viewed more quickly.
We would want to avoid having to manually write code describing these Scenes as it would be hard to have a lot of coverage and we would have to maintain every Scene we write.
We could use a combination of different methods to get Scenes. Listed from most preferred to least preferred.
We can choose to generate screen shots of the all or some of the Scenes in CI at different events (on commit in a PR, on merge, etc) or we can simply leave it as a tool in the repo.
Describe alternatives you've considered
Additional context & Screenshots
#4092 (comment)
Beta Was this translation helpful? Give feedback.
All reactions