Testing Strategy for Q1

created by Alice Johnson at Dec 1, 2025, 10:00 AM

Context

We need to establish a clear testing strategy for Q1. Currently our test coverage is inconsistent and we don't have clear guidelines on what to test and how.

Options Considered

  1. Jest + Cypress (industry standard)
  2. Vitest + Playwright (modern, faster)
  3. Custom testing setup

Recommendation

Vitest + Playwright with testing pyramid: 70% unit, 20% integration, 10% E2E.

Trade-offs

  • Vitest is newer, smaller community
  • But: Much faster, better ESM support, compatible API

Decision

Adopted testing pyramid with Vitest and Playwright. 80% coverage target for new code.

Resolution Summary

Adopted a testing pyramid approach: 70% unit tests, 20% integration tests, 10% E2E tests. Using Vitest for unit/integration and Playwright for E2E. Target 80% code coverage for new code. CI will run unit tests on every PR, E2E nightly.

Activity

TU
Test UserDec 1, 2025, 11:00 AM

I strongly advocate for Vitest over Jest. It's faster, has better ESM support, and the API is compatible enough that migration is easy.

BS
Bob SmithDec 1, 2025, 11:30 AM

+1 for Vitest. We used it at my previous company and the DX is noticeably better.

Alice Johnson changed status from open to resolved

Dec 5, 2025, 02:00 PM

Alice Johnson changed status from resolved to decision

Dec 15, 2025, 10:00 AM

Test User added label Bug

Feb 11, 2026, 10:53 PM

Test User changed assignee from no one to Alice Johnson

Feb 11, 2026, 10:53 PM

This discussion is resolved. To continue this topic, start a new discussion.