skills.rest
MayaDispeler
MayaDispelerCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

testing-standards

Enforce test design, structure, and execution best practices for unit, integration, and end-to-end tests.

3|Updated Apr 14, 2026
Search Tags:#test automation#test doubles#software testing#test design#test pyramid
One-click install
npx skills add https://github.com/MayaDispeler/TheOrqestra --skill testing-standards-mayadispeler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: testing-standards
Source: https://github.com/MayaDispeler/TheOrqestra/tree/main/skills/testing-standards
Command: npx skills add https://github.com/MayaDispeler/TheOrqestra --skill testing-standards-mayadispeler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill unit provides guidelines and rules for writing, reviewing, and improving tests, addressing common pitfalls and promoting best practices in software testing.

Core Features & Use Cases

  • Test Pyramid: Encourages a balanced test suite by prioritizing unit tests over integration and end-to-end tests.
  • Non-Negotiable Standards: Outlines specific requirements for test structure, naming, and behavior to ensure reliability.
  • Test Doubles Taxonomy: Offers a guide for choosing the right type of test doubles (stubs, mocks, fakes, spies, etc.) based on the context.
  • Decision Rules: Provides a set of rules to decide on the type of test, test structure, and test doubles to use.
  • Test Structure: Advocates for the Arrange-Act-Assert (AAA) pattern and best practices for test writing.
  • Expert Vocabulary: Defines key terms related to testing for clarity and consistency.

Quick Start

Trigger the testing-standards skill when writing or reviewing tests to ensure adherence to best practices.

Frequently Asked Questions about testing-standards

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

FAQPage Schema
How do I apply the test pyramid to balance my unit, integration, and end-to-end tests?▼

Test isolation ensures each test runs independently without side effects. Achieve it by using appropriate test doubles like stubs or mocks to decouple external dependencies, enforcing strict boundaries in your test design and execution.

What is the best way to structure test cases using the Arrange-Act-Assert pattern?▼

The Arrange-Act-Assert (AAA) pattern structures tests into three distinct phases: setting up data, executing behavior, and verifying results. This structure enforces clear test design and consistent execution across your software testing workflow.

How do I choose the right test doubles like stubs, mocks, fakes, or spies for my tests?▼

Choose test doubles based on context using established taxonomy rules. Use stubs for state verification, mocks for behavior verification, fakes for lightweight implementations, and spies to record interactions while testing software components.

When should I use test doubles in my software testing strategy?▼

Use test doubles to isolate the system under test and prevent external dependencies from making tests brittle. Apply decision rules based on your context to determine when stubs, mocks, fakes, or spies are necessary for reliable test execution.

Do I need specific testing frameworks to implement these test design standards?▼

No specific testing framework is required. The standards apply to any project requiring consistent testing practices, focusing on universal test design principles, naming conventions, and structure rather than framework-specific configurations.

Related Skills

Explore More Software Engineering Skills→
telum-aitelum-ai
2

project-import

Create a Speck project structure with a skeleton project.md file.

Official
Basic
GainInsightDevGainInsightDev

af-analyse-test-coverage

Analyze test coverage reports to identify untested code paths and gaps.

Official
Intermediate
Kushal9889Kushal9889

husky

Sets up Husky git hooks to automate code quality checks and testing before commits.

Community
Intermediate
takusaotometakusaotome
5

tdd-developer

Guide Test-Driven Development through red-green-refactor cycles with failing tests and minimal code.

Community
Intermediate