standards-testing

Standardize unit, integration, and E2E testing with AAA patterns and coverage goals.

2|Updated Apr 10, 2024
One-click install
npx skills add https://github.com/gdurandvadas/dotfiles --skill standards-testing-gdurandvadas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: standards-testing
Source: https://github.com/gdurandvadas/dotfiles/tree/main/config/opencode/skills/standards-testing
Command: npx skills add https://github.com/gdurandvadas/dotfiles --skill standards-testing-gdurandvadas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Teams often lack a unified framework for unit, integration, and end-to-end testing, resulting in inconsistent quality and slow feedback loops. This standard defines clear expectations to accelerate reliable testing practices.

Core Features & Use Cases

  • Defines the AAA (Arrange-Act-Assert) testing pattern to standardize test organization.
  • Establishes explicit coverage goals (e.g., critical path coverage and public API testing) and practical checklists for test creation and reviews.
  • Provides guidance on test structure, naming, and best practices to improve maintainability and reliability.

Quick Start

Adopt these standards in your project by integrating the AAA pattern, enabling coverage targets, and applying the checklists during test design and reviews.

Frequently Asked Questions about standards-testing

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

FAQPage Schema
How do I standardize unit, integration, and E2E testing practices across multiple projects?

This approach standardizes testing practices by enforcing the AAA pattern, setting explicit coverage goals, and applying comprehensive checklists during test design and reviews to ensure consistent quality across projects.

What is the AAA pattern in testing and how does it improve test maintainability?

The AAA (Arrange-Act-Assert) pattern standardizes test organization by structuring tests into clear phases, which improves maintainability and reliability through consistent test structure and naming conventions.

How do I set test coverage goals for critical paths and public APIs?

Establish explicit coverage goals targeting critical path coverage and public API testing, creating practical checklists that enforce concrete requirements for test quality gates.

Can I use these testing standards checklists for both test creation and code reviews?

Yes, the testing standards provide practical checklists designed to be applied during both test creation and reviews, enforcing requirements for test structure, naming, and overall quality.

Why does my team have inconsistent test quality and slow feedback loops across projects?

Inconsistent test quality often stems from lacking a unified framework for unit, integration, and end-to-end testing; defining clear expectations and standards accelerates reliable testing practices and feedback.