amare/openspec/changes/build-public-site/specs/quality-gates/spec.md at cursor/c765e363

Files

Manoel Freitas 3dc1f449ee feat: ship public site with SEO and visuals (#3 )

* feat: ship public site with SEO and visuals

Publish CMS content on public routes with responsive media,
accessibility checks, and deterministic visual baselines.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix: make browser visual CI deterministic for media

Mount host public storage into FrankenPHP so seeded fixtures are served,
and replace PNG-as-JPG fixtures with real JPEGs so Chromium can render them.

Co-authored-by: Cursor <cursoragent@cursor.com>

* fix: serve public media on same-origin storage paths

Pest Browser hosts on 127.0.0.1:port while Storage::url used
http://localhost, so screenshots captured broken images. Use relative
/storage URLs for media and absolutize only OG tags via url().

Co-authored-by: Cursor <cursoragent@cursor.com>

* test: refresh visual baselines from CI Ubuntu screenshots

Media now loads on same-origin /storage paths, so baselines must
capture the rendered fixtures. Use full-page snapshots from the CI
runner to keep Pest's exact snapshot match stable across environments.

Co-authored-by: Cursor <cursoragent@cursor.com>

---------

Co-authored-by: Cursor <cursoragent@cursor.com>

2026-07-29 10:12:24 -03:00

1.1 KiB

Raw Permalink Blame History

MODIFIED Requirements

Requirement: Browser tests run against FrankenPHP-served application

The system SHALL execute browser tests using Pest Browser/Playwright against an application served by FrankenPHP in CI. The browser job MUST cover the E2E journeys available in the current phase, the visual regression assertions and the automated accessibility checks for public routes, and MUST run in assertion mode without regenerating baselines (SPEC §13.4, §13.5, §13.8, §14.1).

Scenario: Browser job validates served application

WHEN the browser CI job runs
THEN tests execute against the built application artifact or equivalent production-like image

Scenario: Browser job covers visual and accessibility assertions

WHEN the browser CI job runs
THEN it MUST execute the visual regression suite and the accessibility suite
AND a failing snapshot or a critical/serious accessibility issue MUST block merge

Scenario: Browser failures publish diagnostics

WHEN a browser test fails in CI
THEN the job MUST publish screenshots, snapshot diffs, application logs and browser logs as artifacts

1.1 KiB Raw Permalink Blame History