-
Notifications
You must be signed in to change notification settings - Fork 266
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Setup and introduce visual testing tools and CI #9057
Comments
We can do a quick spike about the framework for Q3 but realistically, this is a Q4 project. |
We have to define it too, because it's not written in the issue. |
@a-arias has started to look at visual testing with @rancher-max so do sync up and see if there's any double effort to watch out for. |
I guess we missed track of my work since November 😅 I also have a full report of the research of several pages where I'm tracking all the options and issues. PS: This ticket is almost ready for PR, so it may be worth to get an update here of new requirements, since I see nothing written. |
Description
Avoid the need for manual tests as in the current state, almost 400 issues have been created.
Define tools, setup and configure CI for visual testing. The goal is to track visual changes on components which are added in Storybook as style guide.
This tracks down to typography and spacing, as well as basic components, aspects which should be consistent and not possible to test in other ways than visually.
More about Storybook visual testing: https://storybook.js.org/tutorials/visual-testing-handbook/
Example Issues
Other cases which may not be required in the style guide have to be considered in somehow:
Finally we may think about an automation to match the provided design, e.g.:
The text was updated successfully, but these errors were encountered: