CopilotKit / CopilotKit/outpost

Quality Gate 4 (Playwright visual verification) has never existed — no Playwright in the repo

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

Nobody has claimed this yet.

area: infrastructure roadmap roadmap: later
Dominant language
TypeScript
Stars
7
Forks
3
Avg merge
7d 16h
Merged PRs (30d)
15

Description

Quality Gate 4 in the Build Plan requires, for every UI phase:

Playwright screenshots at iPhone SE (375x667), iPhone 14 Pro Max (430x932), Desktop (1440x900). Never trust DOM measurements — always visual inspection of actual screenshots.

There is no Playwright dependency in any package.json, and no e2e or browser-test directory anywhere in the repo. The gate has never been enforceable.

Why it is worth more than it looks

Phases 1D, 2A, 3A–3G were all UI work that passed this gate on paper. The dashboard has never been verified at a mobile viewport by anything other than a person looking at it, if that.

This is low urgency — nothing is on fire — but it is the gate most likely to be quietly dropped from the standard entirely, and the Build Plan still lists it as mandatory. Either install it or amend the standard, so the written process matches what we actually do.

Cheapest useful version

Playwright with three viewport projects, one smoke spec per top-level route that loads the page and captures a screenshot. Not visual-diff assertions to begin with — just artifacts on CI so a reviewer can look. Visual regression baselines can come later if they earn their keep.

Related: #185 asks CI to build the Docker images and test on the runtime they ship. Both are "CI does not exercise the thing we actually deploy."

Contributor guide

No contributing guide indexed for this repository

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 inspecting the package.json files and the existing route entry points; the issue says no e2e or browser-test directory exists. Add the smallest Playwright setup with projects for 375x667, 430x932, and 1440x900, plus one smoke screenshot spec per top-level route. Done means the checks run in CI and expose screenshot artifacts for review.

Written by the indexing model from the issue text.

Assessment

Tech stack
playwright, typescript
Domain
ci-cd, testing-qa, web-dev
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
64/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.