Skip to content

fix(test): isolate browser runs and restore the report journey (T-117) - #347

Merged
cursor[bot] merged 11 commits into
mainfrom
fix/T-117-compose-isolation
Nov 22, 2026
Merged

cursor[bot] merged 11 commits into
mainfrom
fix/T-117-compose-isolation

Conversation

@Reet24-del

Copy link
Copy Markdown
Collaborator

Summary

Give seeded Playwright and Lighthouse runs dedicated Compose projects, temporary credentials, and scratch storage. Preserve the full Chromium suite and run the seeded Bench smoke in Chromium and Firefox.

The casebook journey also exercises report generation. Legacy JSON atlas artifacts are loaded with the same typed chart data as current NPZ artifacts, and the app fetches report preview and download bytes with its bearer session.

Changes

  • Run migrations, load the shared seed, and verify readiness through the authenticated production stack. Remove only containers and volumes belonging to the test project.
  • Keep the historical seeded campaign readable. Register the shipped warehouse definition through the API and use the returned version for new Wizard campaigns. Return a field-level validation error if an older registered version no longer matches its task files.
  • Exercise the Casebook medoid, every strategy in Trials, and the full export journey. Verify the sandboxed frame contains the generated campaign report and check the report HTML, the Run parameter graphic, and keyboard navigation.

References #186, #187, #188, #330, #332, and #334. GitHub recorded #186 closed before this patch.

Verification

  • All 36 Chromium tests passed against the isolated production stack, including the complete report export journey and 30 accessibility checks across light and dark themes.
  • Firefox seeded Bench smoke passed against the same production setup.
  • All 290 web unit tests passed with 83.6% line coverage. All 77 focused backend tests passed, including legacy report data and stale scenario versions. Strict Python and TypeScript checks passed.
  • The stack wrapper propagated a deliberate child failure and then left no containers or volumes in its test project. It rejected the default Compose project name before calling Docker.

@cursor
cursor Bot merged commit 750a40e into main Nov 22, 2026
22 checks passed
@cursor
cursor Bot deleted the fix/T-117-compose-isolation branch November 22, 2026 21:17
cursor Bot pushed a commit that referenced this pull request Nov 22, 2026
Document e2e.yml PR triggers after the seeded Playwright harness landed in #347.
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.

2 participants