testing-patterns

Document and enforce consistent testing patterns for unit, integration, and mock-based tests.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/bcassiano/MariIA --skill testing-patterns-bcassiano
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-patterns
Source: https://github.com/bcassiano/MariIA/tree/main/ag_kit_2/.agent/skills/testing-patterns
Command: npx skills add https://github.com/bcassiano/MariIA --skill testing-patterns-bcassiano

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Patterns and guidelines for reliable, well-structured tests across projects, reducing flakiness and maintenance costs.

Core Features & Use Cases

  • Comprehensive guidance on the Testing Pyramid, AAA pattern, and test type selection.
  • Best practices for test data, organization, and avoiding anti-patterns.
  • Examples of how to apply these patterns in unit, integration, and end-to-end tests.

Quick Start

Run the included test runner to execute project tests and generate coverage insights.

Frequently Asked Questions about testing-patterns

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

FAQPage Schema
What are the best testing patterns for reducing flakiness and maintenance costs?

The AAA pattern structures tests into Arrange, Act, and Assert phases to improve readability and reduce flakiness. It guides unit, integration, and end-to-end testing strategies by enforcing clear naming conventions and organized test data generation.

How do I organize unit and integration tests to avoid common anti-patterns?

You can organize unit and integration tests by following structured test organization guidelines and mock-based testing strategies. This approach enforces consistent naming conventions and prevents common testing anti-patterns across projects of any size.

When should I use mocking in my unit testing strategy?

Mocking should be used in unit testing to isolate components and simulate dependencies. Structured mock-based testing strategies guide this process, ensuring comprehensive test organization and reliable test suites without introducing flakiness.

Can I apply these testing guidelines to development projects of any size?

Yes, these testing guidelines apply to development projects of any size. They document and enforce consistent testing patterns across codebases, satisfying requirements for comprehensive test organization and structured test data generation regardless of scale.

How do I run project tests and generate coverage insights?

You run the included test runner script to execute project tests and generate coverage insights. This provides immediate feedback on your test suite's reliability and highlights areas lacking comprehensive test coverage.

Why does test suite flakiness increase and how can structured patterns help?

Test suite flakiness increases due to inconsistent test organization and poor test data management. Structured patterns help by enforcing clear naming conventions, guiding test type selection, and applying mock-based strategies to reduce maintenance costs.