Testing
Testing is split between fast app-level Vitest suites and browser-based QA checks.
| Area | Tooling | Location |
|---|---|---|
| Strapi | Vitest | apps/strapi/tests |
| UI | Vitest | apps/ui/**/*.test.ts |
| E2E | Playwright | qa/tests/playwright/e2e |
| Accessibility | Playwright + axe-core | qa/tests/playwright/axe |
| SEO | Playwright | qa/tests/playwright/seo |
| Visual | Playwright screenshots | qa/tests/playwright/visual |
| Performance | Lighthouse CI | qa/tests/playwright/perfo |
| Load | k6 (TypeScript) | qa/tests/playwright/load |
References
- Unit Testing — Vitest tests for Strapi and UI code.
- Playwright Testing — E2E, accessibility, SEO, visual regression, and Lighthouse CI.
- Load Testing (k6) — simulated visitor traffic: does the site hold, where does it break, does it recover.
- GitHub Actions QA Pipeline — how the
qa.ymlworkflow triggers, runs, and reports. - Page Object Model and Smoke vs Mock — POM conventions and when to use a mocked backend.
- Test Cases — Gherkin-style test case docs with a live Pass/Fail checklist and one-click results export.
- Common Knowledge — QA tribal knowledge: environment quirks, known issues, and workarounds worth not forgetting.
What To Test Where
- Use Vitest for fast logic and API utility coverage.
- Use Playwright E2E for user flows and route-level behavior.
- Use axe tests for accessibility regressions.
- Use SEO tests for metadata, robots, sitemap, and page structure.
- Use visual tests for layout/component regressions.
- Use Lighthouse CI for performance budgets and high-level page quality.
- Use k6 load tests to check that the site holds expected traffic, on STG before a launch with a traffic peak.