Skip to content
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

πŸ’Έ Tech Debt – Visual Testing #3376

Open
2 tasks
isaaclombardssw opened this issue Dec 5, 2024 · 0 comments
Open
2 tasks

πŸ’Έ Tech Debt – Visual Testing #3376

isaaclombardssw opened this issue Dec 5, 2024 · 0 comments

Comments

@isaaclombardssw
Copy link
Member

Description
See storybook – one great feature of that tool is automated visual testing against reference images.

The V2 components created as part of the epic #3306 were created modularly – as per the figma (as composites of subcomponents). This is great in some ways, but has the caveat that changing a component may have run-off changing to other components (as the underlying subcomponents might be changed). We want to avoid this.

Proposed solution
How would you fix it?

  • Implement visual testing with Storybook or another tool, testing consulting page components against the Figma designs.
  • Create a Rule on Storybook, since it's the tool we want to recommend for this type of work.
@github-project-automation github-project-automation bot moved this to πŸ€·β€β™‚οΈ Needs Triage in SSW.Website Dec 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: πŸ€·β€β™‚οΈ Needs Triage
Development

No branches or pull requests

1 participant