Testing
How we ensure quality and reliability across the Riverside Herald codebase.
📊 Coverage (Last Run)
Loading coverage…
🔄 What Happens During Testing
1
Unit Tests
Vitest + React Testing Library
Individual components and functions are tested in isolation. Mocks replace external dependencies.
- •Components render correctly with given props
- •User interactions trigger expected handlers
- •Conditional rendering based on state
2
Coverage Report
Vitest + v8
Code coverage measures which lines, branches, and functions are exercised by tests.
- •Statements: % of executable statements run
- •Branches: % of conditional paths taken
- •Functions: % of functions called
- •Lines: % of lines executed
3
End-to-End (E2E)
Cypress
Real browser tests against a running app. Tests full user journeys.
- •Login, register flows
- •Article browsing and business directory
- •Form submissions and API round-trips
Commands
$ npm run test— Single run
$ npm run test:watch— Watch mode
$ npm run test:coverage:public— Generate coverage and copy to Testing page
$ npm run test:e2e— Cypress E2E (headless)
$ npm run test:e2e:open— Cypress E2E (interactive)