testing-patterns

The Testing Pyramid guides you to balance unit, integration, and E2E tests by weighting the majority of your suite toward fast unit tests, using fewer integration tests, and limiting E2E tests to critical paths. This pattern improves test reliability and maintainability.

The AAA pattern structures tests into Arrange, Act, and Assert phases to ensure clean test organization. Codifying this pattern into checkable rules improves the reliability and maintainability of your software tests.

You can stabilize test suites by introducing consistent mocking patterns and data strategies. This Skill codifies mocking best practices and anti-pattern guidance into concrete rules, helping developers and testers avoid brittle mocks.

Choose integration testing when verifying interactions across multiple components or boundaries, and unit testing for isolated logic. This Skill provides principles to guide developers in choosing testing strategies for different scopes within their software projects.

Common testing anti-patterns include poor test organization and inconsistent mocking. This Skill provides concrete anti-pattern guidance and checkable rules to help developers avoid these pitfalls and maintain reliable software tests.

Yes, this guidance applies testing patterns across software projects. It codifies unit, integration, and E2E principles into concrete rules, helping developers and testers choose strategies for different scopes regardless of the specific platform.