Test County Setup

How to stand up and tear down a test session against CivicLoop County OS. On-demand, no standing .test accounts on production.

Demo staff (production)

Password: CivicPulse2026! (canonical demo staff password; do not change). Seed/refresh with web/scripts/seed-staff.mjs (idempotent).

Reserved test data (do NOT reuse for new tests)

• report-flow main: (301) 555-0142
• report-flow photo: (301) 555-0143
• console hero-flow: (301) 555-0177
• track: (301) 555-0188
• MFA: mfatest@pgc.example.gov

Run the suites

cd web
npm test                         # Playwright feature/journey/rbac/mobile
node scripts/ui-sweep.mjs        # every-button per-role (add DEMO_APP_URL for prod)
node scripts/prod-smoke.mjs      # 20 prod checks (run from repo root)
node scripts/record-demo.mjs     # silent captioned QA recording
node scripts/make-walkthrough-video.mjs   # voiced EN/ES detailed + reel

Cleanup

• DELETE /api/test-verify?phone=<phone> removes a test resident + request + location.
• DELETE /api/test-verify?mfauser=<email> removes MFA factors for the MFA test account.
• County OS demo rows (vendors, permits, feeds, KB) are seeded data; delete junk created during a sweep from each module's Manage section.

Seeded demo content

• 220 realistic 311 requests (scripts/seed-demo-requests.mjs).
• County OS demo rows across all 9 modules (PG County county_id 11111111-...).
• 3 sample data feeds with 30 daily readings each (salt fleet, pavement vibration, attendance).
• Onboarding questionnaire seeded as answered county_kb rows.

Database

Supabase project fxhcphtwnicrypsznsxa. Schema source of truth: web/sql/civicpulse-schema.sql. Pull a fresh dump and check information_schema before writing new SQL.