Visual regression testing for critical claim-flow UI states

[phertyameen]

Location

frontend/e2e/ or frontend/visual-tests/ (new)

Problem

The claim flow's distinct states (pending, success, error, expired, already-claimed) are exactly the kind of UI where a subtle unintended visual regression (e.g. a broken layout hiding the actual claim amount, or an error state that doesn't visually read as an error) could go unnoticed by functional tests alone while still meaningfully harming a real recipient's experience.

Acceptance Criteria

• Visual regression tooling (e.g. Playwright's screenshot comparison, Chromatic, or equivalent) covers each distinct claim-flow UI state
• Wired into CI, flagging (not necessarily hard-blocking without review) any pixel-level diff for human confirmation
• Baseline update process documented so legitimate intentional design changes don't cause permanent CI friction

[oyinade247]

Can I work on this pleaseee

[Horlarmmy]

@Horlarmmy has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hi, I'd like to work on this issue. Kindly assign

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Horlarmmy to this issue.

[Fathia-tech14]

@Fathia-tech14 has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello, I’m interested in working on this issue. I would appreciate it if you could assign it to me. Thank you!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fathia-tech14 to this issue.