testing-strategist

Name: testing-strategist
Availability: InStock
Author: Sammykins

Integrates Vitest and Playwright to create balanced unit and end-to-end testing strategies.

Updated Oct 31, 2024

Search Tags:#vitest #testing #playwright #unit-testing #e2e-testing #test-strategy

Ready to run

npx skills add https://github.com/thesammykins/dotfiles --skill testing-strategist-thesammykins

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing-strategist
Source: https://github.com/thesammykins/dotfiles/tree/main/.agents/skills/testing-strategist
Command: npx skills add https://github.com/thesammykins/dotfiles --skill testing-strategist-thesammykins

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps teams design and implement a resilient testing strategy by combining fast unit tests with reliable end-to-end coverage, avoiding brittle tests that depend on internal implementation.

Core Features & Use Cases

Unit testing with Vitest for pure functions and hooks.
End-to-end testing with Playwright for critical user flows.
Guidance on when to apply unit vs E2E tests and how to structure tests to avoid implementation-detail testing.

Quick Start

Run the starter setup to initialize Vitest and Playwright and begin writing strategy-aligned tests.

Frequently Asked Questions about testing-strategist

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

What's the best way to combine Vitest and Playwright for a full-stack testing strategy?▼

A resilient testing strategy combines Vitest for fast unit tests on pure functions and hooks with Playwright for reliable end-to-end coverage of critical user flows. This integration provides fast feedback loops while avoiding brittle tests that depend on internal implementation details.

When should I use unit testing versus end-to-end testing in my frontend project?▼

Unit testing with Vitest should be applied to pure functions and hooks, while end-to-end testing with Playwright is reserved for critical user flows. This separation ensures fast feedback loops and reliable coverage without testing implementation details.

How do I avoid brittle tests that depend on internal implementation details?▼

To avoid brittle tests, structure tests by specifying clear guidance on test levels and project structure. By separating unit tests for pure functions from E2E tests for user flows, the strategy ensures tests validate behavior rather than internal implementation details.

Does this testing strategy work for both frontend and backend projects?▼

Yes, the testing strategy applies to frontend, backend, and full-stack projects. It integrates Vitest for unit testing with Playwright for end-to-end testing, providing fast feedback loops and reliable coverage across diverse project structures.

How do I initialize Vitest and Playwright to start writing strategy-aligned tests?▼

Run the starter setup to initialize Vitest and Playwright. This quick start approach configures the tooling and specifies project structure best practices, allowing you to immediately begin writing tests aligned with the testing strategy.