Can this skill help reduce flaky tests?

Yes, it enforces test isolation and independent state management principles specifically designed to eliminate non-deterministic test behavior.

How does it handle mocking?

The skill provides best practices for mocking external services and dependencies while discouraging the mocking of internal implementation details to keep tests maintainable.

Does it focus purely on code coverage percentages?

No, it prioritizes meaningful coverage of business logic, error handling, and edge cases over reaching an arbitrary 100% coverage metric.

When should I trigger the testing-basics skill?

You should trigger it whenever you are writing new tests, setting up a test suite for a new feature, or debugging issues within existing test files.

What languages does this skill support?

The skill provides language-agnostic patterns like AAA and standard naming conventions that apply to Python, JavaScript, Java, and most other modern programming environments.

Testing Foundations

Name: Testing Foundations
Author: timequity

bytimequity

Security & Testing

Implements industry-standard testing patterns and best practices to ensure high-quality code reliability and maintainable test suites.

About

The Testing Foundations skill equips Claude with essential methodology for writing robust tests across any programming language or framework. It focuses on the AAA (Arrange-Act-Assert) pattern, descriptive naming conventions, and the strategic distinction between unit, integration, and E2E tests. By enforcing test isolation and providing clear guidance on what to mock, this skill helps developers move beyond simple code coverage to create meaningful, non-flaky test suites that protect business logic and handle edge cases effectively.

Key Features

0 GitHub stars
Applies the Arrange-Act-Assert (AAA) pattern for readable test structures
Implements test isolation and cleanup best practices to prevent state sharing
Provides strategic guidance on Unit, Integration, and E2E test scoping
Enforces descriptive naming conventions for clear test intent
Guides the proper use of mocking for external dependencies versus internal logic

Use Cases

Bootstrapping a new project with a standard testing architecture
Expanding test coverage for complex business logic and edge cases
Refactoring existing tests to improve isolation and reduce flakiness

About

Key Features

0 GitHub stars
Applies the Arrange-Act-Assert (AAA) pattern for readable test structures
Implements test isolation and cleanup best practices to prevent state sharing
Provides strategic guidance on Unit, Integration, and E2E test scoping
Enforces descriptive naming conventions for clear test intent
Guides the proper use of mocking for external dependencies versus internal logic

Use Cases

Bootstrapping a new project with a standard testing architecture
Expanding test coverage for complex business logic and edge cases
Refactoring existing tests to improve isolation and reduce flakiness