test(staging): feature-level verification of closed issues + seeded test users #119

Merged

shad0w merged 1 commit from feat/staging-issue-verification into master

2026-06-24 06:46:18 +00:00

shad0w commented

2026-06-24 06:20:31 +00:00

Owner

What

A feature-level Playwright suite (App/tests/staging/) that logs into the running staging instance (ppms-staging, port 3200) and verifies each closed portal issue is actually fixed — one spec per issue, driving the real UI through credential login.

To make credential login possible against pelagia_test (a prod mirror with only real, mostly SSO-only users), prisma/seed-test-users.ts idempotently seeds one known-password @pelagia.local user per role, and automation/refresh-test-db.sh runs it after every daily refresh so the logins always exist on staging.

Result against staging

41 passed, 1 skipped, 0 failed. Two closed issues were found NOT fixed and are recorded as documented test.fail() so the suite stays green while flagging the gap:

#13 — Accounts dashboard has no "Payments completed this month" card.
#24 / #40 — logout tooltip still reads "Sign out", not "Log out" (both were pipeline/button-sim test issues).
Skipped: #10 (attachment grouping) — the staging mirror currently has zero PO attachments to exercise.

Issue → script mapping

Full table + run instructions in Docs/TESTING.md. One spec file per issue (the filename is the mapping). Crewing epics (#75/#76/#79/#81/#83/#86) are smoke-checked for surface render; deep crewing flows remain covered by the existing integration suites.

Notes

Test-presence gate: this PR adds tests and touches no app|lib|components|hooks code.
pnpm type-check clean; the staging suite is opt-in (separate playwright.staging.config.ts, not part of pnpm test).
Seeded users are on the throwaway @pelagia.local domain — no collision with production accounts.

🤖 Generated with Claude Code

## What A feature-level Playwright suite (`App/tests/staging/`) that logs into the **running staging instance** (`ppms-staging`, port 3200) and verifies each closed portal issue is actually fixed — one spec per issue, driving the real UI through credential login. To make credential login possible against `pelagia_test` (a prod mirror with only real, mostly SSO-only users), `prisma/seed-test-users.ts` idempotently seeds one known-password `@pelagia.local` user **per role**, and `automation/refresh-test-db.sh` runs it after every daily refresh so the logins always exist on staging. ## Result against staging **41 passed, 1 skipped, 0 failed.** Two closed issues were found **NOT fixed** and are recorded as documented `test.fail()` so the suite stays green while flagging the gap: - **#13** — Accounts dashboard has no "Payments completed this month" card. - **#24 / #40** — logout tooltip still reads "Sign out", not "Log out" (both were pipeline/button-sim test issues). - *Skipped:* **#10** (attachment grouping) — the staging mirror currently has zero PO attachments to exercise. ## Issue → script mapping Full table + run instructions in **`Docs/TESTING.md`**. One spec file per issue (the filename is the mapping). Crewing epics (#75/#76/#79/#81/#83/#86) are smoke-checked for surface render; deep crewing flows remain covered by the existing integration suites. ## Notes - Test-presence gate: this PR adds tests and touches no `app|lib|components|hooks` code. - `pnpm type-check` clean; the staging suite is opt-in (separate `playwright.staging.config.ts`, not part of `pnpm test`). - Seeded users are on the throwaway `@pelagia.local` domain — no collision with production accounts. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

shad0w added 1 commit 2026-06-24 06:20:31 +00:00

test(staging): feature-level verification of closed issues + seeded test users

PR checks / checks (pull_request) Successful in 46s

Details

PR checks / integration (pull_request) Successful in 32s

Details

a72e980558

Adds a Playwright suite (App/tests/staging/) that logs into the running staging
instance (ppms-staging, :3200) and verifies each closed portal issue is actually
fixed — feature level, driving the real UI, one spec per issue.

To make credential login possible against the prod-mirror pelagia_test (which only
holds real, mostly SSO-only users), prisma/seed-test-users.ts idempotently seeds one
known-password @pelagia.local user per role, and automation/refresh-test-db.sh runs
it after every daily refresh so the logins persist on staging.

Result against staging: 41 passed, 1 skipped (#10 — no attachment data on staging).
Two closed issues were found NOT fixed and are recorded as documented test.fail():
  - #13 Accounts "payments completed this month" card is absent.
  - #24/#40 logout tooltip still reads "Sign out" (pipeline test issues).

Docs/TESTING.md documents the suite, the seeded users, how to run it against
staging, and the full issue -> script mapping.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>