Riddy21 / Riddy21/Friday_Budgeting_Pro

Visual regression baseline — screenshot diffs on PR

Open
#307 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

frontend testing
Dominant language
Python
Stars
1
Forks
1
PR merge metrics
No merged PRs in 30d

Description

Summary

Establish a visual regression testing workflow using Playwright screenshots as the baseline.

Approach

After the Tailwind migration stabilizes, capture screenshot baselines for each page × viewport and diff against them on every PR to catch unintended visual changes.

Tasks

  • Choose a visual diff tool: pytest-playwright + pixelmatch, or percy.io, or BackstopJS
  • Capture baseline screenshots (desktop/tablet/mobile) for: login, dashboard, accounts, ledgers, settings, profile
  • Commit baselines to tests/ui_functional/snapshots/
  • Add CI step: diff screenshots vs baselines, fail on > 0.5% pixel difference
  • Add --update-snapshots flag workflow for intentional UI changes
  • Document snapshot update process in CONTRIBUTING.md

Acceptance criteria

  • Unintentional CSS regressions caught on PR
  • Snapshot update is a deliberate, documented action

Part of epic #299. Closes #291 (visual regression testing).

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the existing UI tests and the target path tests/ui_functional/snapshots/, then confirm the Tailwind migration is stable. Resolve the visual diff tool choice, capture baselines for the six listed pages across desktop, tablet, and mobile, and wire the PR comparison and deliberate snapshot-update workflow. Document the update process in CONTRIBUTING.md and verify that the acceptance criteria are met.

Written by the indexing model from the issue text.

Assessment

Tech stack
playwright, python, tailwindcss
Domain
ci-cd, frontend, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.