SSWConsulting / SSWConsulting/SSW.Website
💸 Tech Debt – Visual Testing
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 14
- Forks
- 10
- Avg merge
- 13h 51m
- Merged PRs (30d)
- 38
Description
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.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by reviewing the V2 components from epic #3306, the linked Storybook and Chromatic visual-testing references, and the corresponding Figma designs. Define the component set and reference-image checks, then document the recommended Storybook rule when the checks are established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- figma, storybook
- Domain
- design, frontend, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100