test-levels

Outline when to use unit, integration, and end-to-end tests with Playwright examples.

27|9|Updated Jan 4, 2026
One-click install
npx skills add https://github.com/georgekhananaev/claude-skills-vault --skill test-levels
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-levels
Source: https://github.com/georgekhananaev/claude-skills-vault/tree/main/.claude/skills/test-levels
Command: npx skills add https://github.com/georgekhananaev/claude-skills-vault --skill test-levels

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps teams design and document testing strategies by outlining when to use unit, integration, and end-to-end tests.

Core Features & Use Cases

  • Provides a clear decision framework for selecting the appropriate test level (Unit, Integration, E2E).
  • Includes guidelines and project-specific Playwright examples to illustrate practical application.
  • Helps onboarding by giving a runnable structure and recommended practices for test organization.

Quick Start

Explain the appropriate test level for a feature and generate a starter test layout (unit/integration/e2e) for a sample project.

Frequently Asked Questions about test-levels

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

FAQPage Schema
When should I write unit, integration, or E2E tests for my software project?

Use unit tests for isolated logic, integration tests for component interaction, and E2E tests for full user workflows. Selecting the right test level depends on the scope and boundaries of the software feature.

How do I structure my testing strategy using the test pyramid?

Structure your testing strategy by placing numerous fast unit tests at the base, fewer integration tests in the middle, and sparse E2E tests at the top, ensuring comprehensive software quality coverage.

How do I organize a Playwright E2E testing project layout?

Organize a Playwright E2E testing project by separating unit, integration, and E2E directories. This approach provides a runnable starter structure and recommended practices for test organization.

What is the best way to document test levels for team onboarding?

The best way to document test levels is providing a clear decision framework that defines unit, integration, and E2E tests, and includes project-specific Playwright examples to illustrate practical application.

Does this testing strategy framework work without external dependencies?

Yes, this testing strategy framework operates without external dependencies, providing a self-contained decision framework and structural guidelines for implementing unit, integration, and E2E tests.