testing-patterns

Define and apply testing patterns for unit, integration, and end-to-end tests.

8|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo --skill testing-patterns-gabriellpequeno
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing-patterns
Source: https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo/tree/main/.cursor/skills/testing-patterns
Command: npx skills add https://github.com/gabriellpequeno/Reserva-Aqui---Projeto-de-fim-de-ciclo --skill testing-patterns-gabriellpequeno

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Define piramide de testes, AAA, mocks e organizacao. Use ao escrever ou revisar testes.

Core Features & Use Cases

  • Piramide de testes: muitos testes unitarios rapidos; alguns de integracao; E2E para fluxos criticos.
  • AAA: Arrange, Act, Assert para estruturar casos de teste de forma previsível.
  • Mocks: isolar fronteiras (rede, tempo, DB) para testes unitarios estáveis.

Quick Start

Follow these patterns to structure and review your tests across unit, integration, and end-to-end levels.

Frequently Asked Questions about testing-patterns

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

FAQPage Schema
What is the testing pyramid and how does it structure unit and E2E tests?

The AAA pattern structures test cases into Arrange, Act, and Assert phases to make execution predictable and consistent. This pattern isolates test setup, execution, and verification for reliable software testing.

How do I use mocks to isolate boundaries in unit tests?

Mocks isolate external boundaries like network, time, and databases to create stable unit tests. By replacing these dependencies, mocks ensure your software testing remains deterministic and unaffected by external system states.

What's the best way to write consistent tests across different levels?

The best way to structure consistent tests is applying the testing pyramid alongside the AAA pattern and mocks. This combination ensures fast unit tests, reliable integration tests, and targeted E2E tests for critical software development workflows.

When should I not use end-to-end tests in my testing strategy?

You should limit end-to-end tests to critical flows only, avoiding them for standard logic due to their slower execution and higher maintenance. Rely on fast unit and integration tests for broader coverage to ensure deterministic testing practices.