What are the recommended code coverage targets?

The skill suggests maintaining at least 80% line coverage and 70% branch coverage, with 100% coverage for all critical business paths.

What testing levels does this skill support?

It covers the full testing pyramid, including Unit Tests (70%), Integration Tests (20%), and End-to-End (E2E) Tests (10%).

How does the skill handle external dependencies?

It provides patterns for mocking external services (like payment gateways or repositories) while recommending that you don't mock objects you own, such as domain entities.

What is the AAA pattern mentioned in the skill?

AAA stands for Arrange-Act-Assert, a pattern that organizes tests into three distinct sections to improve clarity and maintainability.

Does it support testing for modern async workflows?

Yes, it includes specific implementation patterns for testing asynchronous code and temporal workflows to ensure state consistency.

Testing Best Practices

Name: Testing Best Practices
Author: violetio

byvioletio

Security & Testing

Implements standardized testing patterns, architectural pyramids, and TDD best practices for robust software development.

About

The Testing Best Practices skill provides a comprehensive framework for software verification within AI-assisted development workflows. It guides developers through the implementation of the testing pyramid—balancing Unit, Integration, and E2E tests—while enforcing the AAA (Arrange-Act-Assert) pattern for readable and maintainable test suites. By offering domain-specific guidance on mocking strategies, test data builders, and coverage targets, this skill ensures that Claude generates high-quality, reliable code that adheres to industry-standard testing principles.

Key Features

Support for testing asynchronous and temporal workflows
Advanced Mocking and Test Data Builder implementations
Specific targets for line, branch, and critical path coverage
Standardized AAA (Arrange-Act-Assert) test patterns
Structural guidance for the Testing Pyramid (Unit, Integration, E2E)
0 GitHub stars

Use Cases

Defining mocking boundaries for external dependencies like APIs and databases
Refactoring legacy code using Test Driven Development (TDD) and standardized naming
Architecting a comprehensive test suite for new microservices or applications

About

Key Features

Support for testing asynchronous and temporal workflows
Advanced Mocking and Test Data Builder implementations
Specific targets for line, branch, and critical path coverage
Standardized AAA (Arrange-Act-Assert) test patterns
Structural guidance for the Testing Pyramid (Unit, Integration, E2E)
0 GitHub stars

Use Cases

Defining mocking boundaries for external dependencies like APIs and databases
Refactoring legacy code using Test Driven Development (TDD) and standardized naming
Architecting a comprehensive test suite for new microservices or applications