Detailed Test Plan
Validation plan to ensure new project content renders correctly without regressions across routes, devices, and edge cases.
Goal
Ensure new projects render correctly on builders/resume pages and related project routes across content variants, viewport sizes, and failure modes, while preserving existing behavior.
Automated tests (prioritized)
- P0 schema checks: required fields, slug uniqueness, ordering key presence, non-empty titles/summaries, link integrity.
- P0 rendering smoke: project sections exist, cards render expected count, links include slug, image alt handling is valid.
- P0 routing: new slugs resolve, unknown slugs return expected not-found behavior.
- P1 accessibility: heading order, discernible link text, landmark/label health checks.
- P1 snapshots: stable snapshots for card + detail route when snapshot tooling exists.
- P2 performance guardrails: avoid unnecessary client bundle bloat from data imports.
E2E scenarios
- Happy path navigation from portfolio surfaces to each new project detail page.
- Error path validation for invalid slugs and partial-data fixtures.
- Responsive checks at mobile and desktop breakpoints.
Manual QA checklist
- Route checks for landing, builders/resume sections, project index/detail pages, and smoke checks for shared layout pages.
- Content stress tests for long titles, long summaries, many tags, and missing optional fields.
- Functional checks for navigation behavior, external link safety, and image loading quality.
- Accessibility checks for keyboard focus and basic screen-reader meaning.
- SEO checks for metadata presence and OpenGraph configuration.
Definition of done
- All new project entries pass schema checks.
- New routes render correctly with no console errors.
- Unknown slugs produce correct 404 behavior.
- Critical accessibility checks pass.
- CI/build/lint/typecheck/test commands pass.