testing

Standardize unit and end-to-end tests using Vitest and Playwright.

Updated Jan 1, 2026
One-click install
npx skills add https://github.com/darshan-rambhia/vamsa --skill testing-darshan-rambhia
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/darshan-rambhia/vamsa/tree/main/.claude/skills/testing
Command: npx skills add https://github.com/darshan-rambhia/vamsa --skill testing-darshan-rambhia

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill standardizes how Vamsa is tested by outlining clear unit and end-to-end testing practices using Vitest and Playwright, reducing flaky tests and ensuring code quality.

Core Features & Use Cases

  • Unit Testing Philosophy: Verify actual behavior through focused tests that exercise logic, components, and integrations.
  • E2E Testing Philosophy: Model user journeys with Given-When-Then patterns to validate end-to-end flows.
  • Reference Recipes: Follow templates in unit-recipes.md and e2e-recipes.md for domain-specific scenarios like React components, GEDCOM workflows, and admin pages.

Quick Start

Use the skill to guide test authoring whenever you create or update tests, aligning with Vitest and Playwright standards.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I structure deterministic unit tests for React components using Vitest?

Deterministic unit tests with Vitest verify actual behavior by exercising React component logic through focused tests. This skill provides standardized templates and recipes in unit-recipes.md to ensure consistent test structure, naming conventions, and coverage targets without flaky results.

What is the best way to model user journeys for E2E testing with Playwright?

E2E testing with Playwright models user journeys using Given-When-Then patterns to validate end-to-end flows. This skill enforces deterministic patterns and provides e2e-recipes.md with page-objects and utilities for domain-specific scenarios like admin flows and GEDCOM workflows.

Can I use Playwright and Vitest together for component and integration testing?

Yes, Vitest and Playwright work together to cover component, integration, and user-journey tests. Vitest handles focused unit logic while Playwright manages end-to-end browser flows, ensuring comprehensive coverage across React components and admin pages.

Why does my E2E testing pattern produce flaky results across user journeys?

Flaky E2E testing often stems from non-deterministic patterns. This skill standardizes test practices by enforcing deterministic patterns, provided utilities, and page-objects, reducing flakiness and validating user journeys reliably through Given-When-Then structures.

Do I need to follow specific naming conventions and coverage targets when writing tests?

Yes, following specific naming conventions and coverage targets is required. This skill codifies test structure and naming conventions, providing reference recipes and enforcing coverage goals to ensure code quality and reduce flaky tests across unit and E2E suites.

When do I need page-objects and provided utilities for GEDCOM feature testing?

Page-objects and provided utilities are needed when testing GEDCOM workflows to maintain deterministic patterns. This skill supplies e2e-recipes.md with domain-specific templates for GEDCOM features, ensuring user journeys are modeled consistently and reliably.