When should I use mocking according to these principles?

Mocks should be used for external dependencies like APIs and databases, slow operations, or unpredictable behaviors to keep tests fast and isolated.

What level of code coverage does this skill recommend?

It suggests a minimum of 80% code coverage for production environments, focusing specifically on critical business logic and paths.

What is the AAA pattern mentioned in the skill?

AAA stands for Arrange-Act-Assert, a pattern that structures tests into three clear phases to improve readability and maintenance.

How does this skill assist with Test-Driven Development (TDD)?

It provides a structured Red-Green-Refactor workflow to help you write failing tests first, implement minimal code, and refactor for quality.

Is this skill specific to a particular programming language?

No, the principles are language-agnostic and can be applied to any environment, including JavaScript, Python, Go, Java, and more.

Testing Principles

Name: Testing Principles
Author: Tahir-yamin

byTahir-yamin

•

Seguridad y Pruebas

Implements language-agnostic testing standards and TDD workflows to ensure high-quality, reliable, and maintainable software.

Acerca de

This skill provides a comprehensive framework for writing high-quality code across any programming language by enforcing industry-standard testing principles. It guides users through the Red-Green-Refactor TDD cycle, defines clear boundaries between unit, integration, and E2E tests via the test pyramid, and establishes rigorous quality standards like the AAA (Arrange-Act-Assert) pattern and 80% code coverage. Whether you are building a new feature or refactoring legacy code, this skill ensures your test suite remains fast, deterministic, and effective at catching regressions.

Características Principales

Rigorous quality standards for coverage and test isolation
3 GitHub stars
Best practices for mocking and test double implementation
Language-agnostic test design patterns including AAA
Clear classification for Unit, Integration, and E2E testing
Standardized TDD workflow guidance (Red-Green-Refactor)

Casos de Uso

Establishing standardized testing strategies for cross-functional teams
Refactoring legacy code with characterization tests
Implementing Test-Driven Development for new features

Acerca de

Características Principales

Rigorous quality standards for coverage and test isolation
3 GitHub stars
Best practices for mocking and test double implementation
Language-agnostic test design patterns including AAA
Clear classification for Unit, Integration, and E2E testing
Standardized TDD workflow guidance (Red-Green-Refactor)

Casos de Uso

Establishing standardized testing strategies for cross-functional teams
Refactoring legacy code with characterization tests
Implementing Test-Driven Development for new features