UI components can change appearance unexpectedly after refactors. Visual regression testing with Chromatic (or Percy) catches these changes before they ship to users.
Requirements and context
- Set up Storybook for key UI components
- Configure Chromatic for visual snapshot testing
- Create stories for:
<InvoiceMarketplaceCard />, <LPStatsCards />, <ProposalCard />, <ReputationCard />, <InvoiceStatusTimeline />, <TokenSelector />
- Integrate Chromatic into CI — fail on unexpected visual changes
- Document the approval process for intentional design changes
Suggested execution
git checkout -b test/chromatic-visual-regression
- Install and configure Storybook
- Write stories for key components
- Connect Chromatic to CI
- Document approval workflow in
CONTRIBUTING.md
Example commit message
test: set up Chromatic visual regression testing for UI components
UI components can change appearance unexpectedly after refactors. Visual regression testing with Chromatic (or Percy) catches these changes before they ship to users.
Requirements and context
<InvoiceMarketplaceCard />,<LPStatsCards />,<ProposalCard />,<ReputationCard />,<InvoiceStatusTimeline />,<TokenSelector />Suggested execution
CONTRIBUTING.mdExample commit message
test: set up Chromatic visual regression testing for UI components