test

Standardize unit, integration, and E2E testing with Vitest, Jest, and Playwright configurations.

1|Updated Sep 12, 2025
One-click install
npx skills add https://github.com/JimmyTranDev/dotfiles --skill test-jimmytrandev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test
Source: https://github.com/JimmyTranDev/dotfiles/tree/main/src/opencode/skills/test
Command: npx skills add https://github.com/JimmyTranDev/dotfiles --skill test-jimmytrandev

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Tests across unit, integration, and end-to-end levels are often inconsistent, hard to adopt, and poorly documented. This skill provides a structured approach that covers test type definitions, naming conventions, mocking strategies, framework setup, and CI integration to raise overall test quality and reduce flaky tests.

Core Features & Use Cases

  • Define test type categories: unit, integration, e2e, and snapshot tests for clear scope.
  • Enforce Arrange-Act-Assert structure and precise naming conventions to improve readability and maintenance.
  • Provide mocking and dependency-injection guidance to isolate logic and enable fast, reliable tests.
  • Offer framework setup guidance with Vitest, Jest, and Playwright examples to cover frontend and backend codebases.
  • Establish CI-ready practices including test isolation, coverage thresholds, and reporting.

Quick Start

Set up a Vitest-based test suite and begin writing unit, integration, and E2E tests following the AAA pattern.

Frequently Asked Questions about test

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

FAQPage Schema
How do I structure unit and integration tests to reduce flaky test failures?

Structure unit and integration tests using the Arrange-Act-Assert pattern and strict isolation rules to ensure deterministic tests and reduce flaky failures caused by shared state.

What's the best way to configure Vitest and Playwright for both frontend and backend codebases?

Configure Vitest and Playwright by standardizing framework setup patterns, naming conventions, and dependency injection to isolate logic across both frontend and backend codebases.

How do I handle mocking and dependency injection for reliable software testing?

Handle mocking by applying structured dependency-injection guidance to isolate logic, which enables fast and reliable software testing across your application layers.

Does this testing workflow support CI integration with coverage thresholds and reporting?

Yes, the workflow establishes CI-ready practices including test isolation, specific coverage targets, and reporting to integrate seamlessly with continuous integration pipelines.

When should I use E2E testing versus snapshot tests in my testing strategy?

Use E2E testing for full application flow validation and snapshot tests for detecting unintended UI changes, establishing clear test type categories to define scope and improve maintenance.