Skip to content

fix(test): isolate the seeded browser stack from local data (T-117) - #334

Open
Reet24-del wants to merge 3 commits into
mainfrom
test/T-117-seeded-playwright-main
Open

Reet24-del wants to merge 3 commits into
mainfrom
test/T-117-seeded-playwright-main

Conversation

@Reet24-del

@Reet24-del Reet24-del commented Nov 22, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Recover the verified isolated browser stack after #330 landed its parallel E2E suite. The new setup uses a dedicated Compose project, temporary credentials and scratch volumes. It rejects shared project names before starting or removing anything.

Changes

  • Preserve the existing Chromium journey and accessibility specs, and run the seeded Bench smoke in both Chromium and Firefox.
  • Inject the disposable API session into browser fixtures and run Lighthouse through the same safe stack lifecycle.
  • Keep CI failure artifacts and include setup output when Compose fails. Fix Node 24 JSON imports so the existing specs can load.

This follows up on #186 and the browser test code in #330 and #332. GitHub records #186 as manually closed before these fixes reached main.

Test evidence

  • Real seeded Chromium and Firefox smoke tests passed on the reconciled stack in 2m28s, including axe, CSP and keyboard Console navigation.
  • Strict TypeScript and web lint passed. The isolated wrapper rejects the default Compose project before executing Docker.
  • The preserved Chromium sweep passed eight routes, then exposed an ARIA violation on the Run page and a focus assertion failure on Trials. These gates remain enabled while the failures are addressed.

Rollback

The production stack and its runtime files are outside this change. The browser test runner owns its Compose resources and removes them after the run.

@cursor
cursor Bot force-pushed the test/T-117-seeded-playwright-main branch from 24e3fe6 to eb665eb Compare November 22, 2026 19:43
@Reet24-del Reet24-del changed the title test(web): add the seeded Playwright Compose harness (T-117) fix(test): isolate the seeded browser stack from local data (T-117) Nov 22, 2026
@cursor
cursor Bot force-pushed the test/T-117-seeded-playwright-main branch 5 times, most recently from d9f2486 to 5e618bb Compare November 22, 2026 20:37
CodewithJha added 3 commits November 22, 2026 20:39
Document the seeded browser harness and E2E settings. Extend the API
healthcheck for cold CI starts, isolate compose projects, make seeded
artefacts writable for UID 10001, and wait on the published web port only.
@cursor
cursor Bot force-pushed the test/T-117-seeded-playwright-main branch from 5e618bb to d778ccc Compare November 22, 2026 20:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant