Testing

Testing

From the app repo root (Node/npm versions in .nvmrc / package.json engines):

Command	What it covers
npm test	Jest unit/integration tests (components, hooks, utils, scripts)
npm run test:watch	Jest watch mode
npm run test:rules-parity	Firestore emulator + report-access rules tests
npm run verify:agency-rules	Emulator check for agency-related rules
npm run lint	ESLint
npm run build	Next production build (CI / App Hosting)
npm run lockfile:ci	Lockfile CI helper
npm run lockfile:regen / lockfile:regen:fresh	Regenerate lockfile when deps change

Before opening a PR

1. npm run lint
2. npm test
3. npm run build if you touched app code, Next config, or lockfile-sensitive deps
4. If you changed firestore.rules or report access helpers: npm run test:rules-parity (and agency verify when relevant)

Manual smoke (local)

Prefer npm run dev (emulators) with seeded accounts (user@user.com, agency@user.com, admin@user.com, password devPassword):

• Log in as each role and open the dashboard tabs you changed
• Create or view a report if you touched reporting / agency / rules
• Confirm login still works after Auth or App Check changes

Study deploy smoke checks and agency ids are not documented here — private misinfo-dashboard-ops.

Related

• CONTRIBUTING
• Architecture