testing

Design and implement unit, integration, and end-to-end test suites.

Updated Dec 28, 2025
One-click install
npx skills add https://github.com/I2olanD/dotfiles --skill testing-i2oland
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/I2olanD/dotfiles/tree/main/.config/opencode/skill/testing
Command: npx skills add https://github.com/I2olanD/dotfiles --skill testing-i2oland

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams design and implement robust test suites across unit, integration, and end-to-end levels.

Core Features & Use Cases

  • Practical guidance on structuring tests by layer (unit, integration, E2E) to balance speed and confidence.
  • Guidance on mocking, test isolation, and debugging failures to reduce flaky tests.
  • Real-world use cases and patterns to improve test quality and maintainability.

Quick Start

Follow the test pyramid guidance to organize your project’s tests and start applying unit, integration, and E2E patterns.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I structure unit, integration, and e2e tests using the test pyramid?

The test pyramid organizes tests by layer to balance speed and confidence, distributing unit, integration, and e2e tests effectively. This structure reduces defects, speeds feedback, and improves overall test reliability across real-world projects.

What is the best way to reduce flaky tests and improve mocking practices?

Reduce flaky tests by applying strict mocking rules and ensuring test isolation. Guiding debugging practices and avoiding common testing anti-patterns helps teams improve test quality and maintainability while reducing intermittent failures.

How do I balance test speed and confidence across different testing layers?

Balance speed and confidence by codifying layer distribution across unit, integration, and end-to-end levels. This practical guidance helps teams structure tests effectively, ensuring fast feedback without sacrificing comprehensive coverage.

When should I use integration tests instead of unit tests in my test suite?

Use integration tests when verifying interactions between components, reserving unit tests for isolated logic. The test pyramid provides practical guidance on layer distribution, helping teams decide the appropriate scope for each test type.

What testing anti-patterns should teams avoid when scaling end-to-end tests?

Teams scaling end-to-end tests should avoid anti-patterns that cause slow feedback and flaky results. Applying the test pyramid codifies layer distribution and debugging practices, guiding effective strategies that improve test quality and maintainability.