testing

Standardize unit, integration, and E2E tests with Vitest, Testing Library, and Playwright.

Updated Apr 5, 2026

Search Tags:#vitest #testing #playwright #testing-library #unit-tests #integration-tests #e2e-tests

Ready to run

npx skills add https://github.com/harryy2510/dotclaude --skill testing-harryy2510

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/harryy2510/dotclaude/tree/main/plugins/dotclaude/skills/testing
Command: npx skills add https://github.com/harryy2510/dotclaude --skill testing-harryy2510

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides comprehensive guidance to standardize and accelerate software testing across unit, integration, and end-to-end levels, reducing flaky tests and improving coverage.

Core Features & Use Cases

Guided testing patterns: outlines recommended test types, naming conventions, and file organization for Vitest, Testing Library, and Playwright.
Quality assurance workflows: helps teams write robust unit and integration tests, component tests, and end-to-end scenarios with consistent practices.
Use Case: imagine a UI component library needing predictable tests and a Playwright end-to-end flow; this skill provides templates and examples to follow.

Quick Start

Place your first test following the conventions described above, e.g., create a simple unit test for a utility function using Vitest and place it next to the source file.

Frequently Asked Questions about testing

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

FAQPage Schema

How do I standardize unit and E2E testing practices with Vitest and Playwright?▼

Standardize unit and E2E testing by applying consistent file placement, naming conventions, and reusable templates across Vitest, Testing Library, and Playwright. This reduces flaky tests and improves coverage through example-driven patterns and structure rules.

What is the recommended file placement for component and integration tests?▼

The recommended file placement for component and integration tests is placing test files next to their corresponding source files. This co-location strategy accelerates software testing efficiency by keeping implementation and validation logic coupled.

Does this testing guidance work for both UI component libraries and end-to-end flows?▼

Yes, this testing guidance works for UI component libraries and end-to-end flows by providing predictable templates and examples. It covers component tests using Testing Library and end-to-end scenarios using Playwright within a unified workflow.

How do I write robust unit and integration tests without flaky results?▼

Write robust unit and integration tests without flaky results by enforcing test structure rules and utilizing standardized mocks. Implementing example-driven patterns across Vitest and Testing Library ensures consistent quality assurance workflows.

Can I use Testing Library with Vitest for component testing workflows?▼

Yes, you can use Testing Library with Vitest for component testing workflows. The guidance outlines recommended test types and standardized practices specifically for building robust component tests across these frameworks.