testing-patterns

Standardize unit, integration, and mocking strategies across test suites.

Updated Sep 2, 2025
One-click install
npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill testing-patterns-rafaelminatto1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-patterns
Source: https://github.com/rafaelminatto1/fisioflow-51658291/tree/main/.agent/skills/testing-patterns
Command: npx skills add https://github.com/rafaelminatto1/fisioflow-51658291 --skill testing-patterns-rafaelminatto1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Testing patterns and principles help teams create reliable, maintainable test suites by providing clear guidance on how to structure tests across different levels.

Core Features & Use Cases

  • Comprehensive guidance on unit, integration, and mocking strategies for fast feedback and maintainable code.
  • Template-driven patterns such as AAA, test pyramid, and data-driven testing to standardize writing tests across projects.
  • Use Case: When starting a new project or refactoring, teams can adopt these patterns to align test practices and reduce flaky tests.

Quick Start

Apply established testing patterns to standardize unit, integration, and mocking strategies across your projects.

Frequently Asked Questions about testing-patterns

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

FAQPage Schema
How do I standardize testing patterns across multiple projects?

Standardize testing patterns by applying template-driven principles like the test pyramid and AAA to align unit, integration, and mocking strategies. This ensures fast feedback, maintainable code, and reduces flaky tests across common languages and frameworks.

What is the best way to structure unit and integration tests for scalable test governance?

Structure tests using the test pyramid to balance unit and integration levels, ensuring scalable test governance. Clear mocking strategies and data-driven templates standardize execution, yielding reliable software test suites and deterministic task outcomes via executable scripts.

How does mocking strategy improve the reliability of software test suites?

Mocking strategies improve reliability by isolating components during unit testing, which reduces external dependencies and flaky tests. Combining mocks with integration testing ensures fast feedback and maintainable code across common languages.

Can I use these testing patterns with any programming language and framework?

Yes, these testing patterns apply to projects using common languages and frameworks seeking clear unit, integration, and mocking strategies. The templates establish language-agnostic governance to standardize writing tests across diverse environments.

Why does my test suite have flaky tests when refactoring?

Flaky tests during refactoring often occur due to misaligned unit and integration boundaries or insufficient mocking strategies. Applying structured testing patterns and templates like the test pyramid standardizes practices to stabilize and benchmark your test suites.