Skip to content

Add opt-in visual regression checks #2

@BAKUGOS1

Description

@BAKUGOS1

Goal

Add a basic visual regression workflow that compares screenshots from repeat runs and flags meaningful UI changes.

Scope ideas

  • Store baselines outside generated artifacts, or document where users should keep them
  • Compare current screenshots against a baseline with a simple threshold
  • Report visual differences in Markdown/Excel output
  • Keep it opt-in so smoke tests stay fast

Done criteria

  • Add a focused implementation or documented spike
  • Include a small fixture/test path
  • Run npm run quality:gate
  • Do not commit generated browser artifacts

Metadata

Metadata

Assignees

No one assigned

    Labels

    area: browserPlaywright browser engine, actions, state, and selectorsarea: reportsMarkdown, JSON, Excel, screenshots, and report previewsenhancementNew feature or requesthelp wantedExtra attention is neededpriority: mediumUseful improvement with moderate priority

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions