testing-patterns

Playwright E2E tests with Firebase emulator integration require isolated backend environments for user flows. This Skill specifies tooling and configurations to automate Playwright setup alongside Firebase emulator usage, establishing repeatable quality gates across frontend and backend layers.

Testing Zustand store state with Vitest involves unit and component tests using Testing Library to validate state management logic. This Skill provides structured test layouts with fixtures, mocks, and clear data contracts to enforce consistent Zustand store validation within CI pipelines.

Accessibility audits and performance checks can run in CI pipelines through automated QA testing patterns. This Skill automates performance testing patterns for CI metrics and accessibility audits, enforcing repeatable quality gates across development workflows and continuous integration environments.

API route testing for e-commerce codebases is supported through consolidated QA testing patterns. This Skill automates API route testing alongside Vitest unit tests and Playwright E2E, enforcing repeatable quality gates across frontend, backend, and store layers.

Firebase emulator for isolated backend testing prevents data conflicts and ensures reliable API route validation. This Skill specifies Firebase emulator usage to create isolated testing scenarios, establishing clear data contracts and structured mocks for backend layers.

Vitest with Testing Library may not suit tests requiring real browser environments or E2E user flow validation. This Skill addresses those limitations by specifying Playwright E2E for reliability scenarios where Vitest unit and component tests alone are insufficient.