testing-patterns

Plan and structure unit, integration, and E2E tests with pyramid strategies.

Updated Jan 25, 2026
One-click install
npx skills add https://github.com/tridentsof/antigravity-dev-kit --skill testing-patterns-tridentsof
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-patterns
Source: https://github.com/tridentsof/antigravity-dev-kit/tree/main/skills/testing-patterns
Command: npx skills add https://github.com/tridentsof/antigravity-dev-kit --skill testing-patterns-tridentsof

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Standardizes and guides testing practices across full-stack applications to improve reliability and maintainability.

Core Features & Use Cases

  • Test Planning Workflow (CRITICAL): Plan -> Test -> Mark Done protocol to organize testing efforts.
  • Test Pyramid guidance: visualizes unit, integration, and E2E testing balance.
  • AAA Pattern and Naming conventions: Arrange-Act-Assert structure and consistent test name formats for readability.
  • Mocking Guidelines and Code Coverage targets: practical rules to ensure meaningful tests with measurable coverage.

Quick Start

Start by auditing your current tests and apply AAA, the Test Pyramid, and consistent naming to improve reliability and readability.

Frequently Asked Questions about testing-patterns

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

FAQPage Schema
How do I structure unit tests for better readability?

Structure unit tests using the Arrange-Act-Assert (AAA) pattern to separate setup, execution, and verification. This pattern enforces consistent test name formats and clear separation of logic, making tests easier to read and maintain across full-stack applications.

What is the best way to balance unit, integration, and E2E testing?

Balance unit, integration, and E2E testing by applying the Test Pyramid strategy. This approach guides you in distributing tests across scopes to optimize both execution speed and coverage, ensuring a maintainable and reliable full-stack testing suite.

How do I organize my testing workflow before writing code?

Organize your testing workflow by following the Plan -> Test -> Mark Done protocol. This standardized test planning process helps structure your testing efforts systematically, ensuring all scopes are covered before implementation begins.

What are the guidelines for mocking in integration tests?

Mocking guidelines provide practical rules to ensure meaningful tests with measurable code coverage targets. By isolating dependencies correctly, you prevent flaky tests and maintain high reliability across both unit and integration testing scopes.

Can I apply these testing patterns to full-stack applications?

Yes, these testing patterns standardize practices specifically across full-stack applications. They provide actionable guidance with embedded examples for unit, integration, and E2E scopes, enabling rapid adoption and consistent maintainability for developers.