skills.rest
pavel-molyanov
pavel-molyanovCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

test-master

Define testing strategies using the test pyramid and test type selection guidelines.

244|75|Updated Dec 22, 2025
Search Tags:#unit tests#testing#quality assurance#integration tests#e2e tests#test strategy
One-click install
npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill test-master-pavel-molyanov
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: test-master
Source: https://github.com/pavel-molyanov/molyanov-ai-dev/tree/main/skills/test-master
Command: npx skills add https://github.com/pavel-molyanov/molyanov-ai-dev --skill test-master-pavel-molyanov

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a comprehensive guide to software testing methodologies, ensuring high-quality code through effective test strategies, clear guidelines on when to use different test types, and principles for maintaining test quality.

Core Features & Use Cases

  • Test Strategy Definition: Understand the Test Pyramid and when to apply Smoke, Unit, Integration, and E2E tests.
  • Test Quality Assurance: Learn principles for writing effective tests and identify anti-patterns like redundant testing.
  • Use Case: A developer is unsure whether to write an integration test or an E2E test for a new API endpoint. They consult this Skill to understand the trade-offs and best practices for their specific scenario.

Quick Start

Explain the test pyramid strategy and when to use each test type.

Frequently Asked Questions about test-master

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

FAQPage Schema
What is the test pyramid and when should I use each test type?▼

The test pyramid is a testing strategy defining Smoke, Unit, Integration, and E2E tests. You use unit tests for isolated logic, integration tests for module interactions, and E2E tests for full user flows to ensure comprehensive coverage.

How do I choose between writing an integration test and an E2E test?▼

Choosing between an integration test and an E2E test depends on project complexity. Integration tests validate module interactions efficiently, while E2E tests verify complete user workflows but require more maintenance and execution time.

How do I avoid redundant tests and ensure test quality?▼

To avoid redundant tests and ensure test quality, follow principles that prevent overlapping coverage across test types. Focus on clear guidelines for writing effective tests and identifying anti-patterns in your test suite.

What is the best way to define a unit test strategy for a new API endpoint?▼

The best way to define a test strategy for a new API endpoint is to evaluate trade-offs between test types. Apply guidelines to select appropriate tests based on specific project scenarios and complexity.

When should I not use E2E tests in my testing methodology?▼

You should not use E2E tests when verifying isolated component logic or simple module integrations. E2E tests introduce significant execution overhead and maintenance burden, making unit or integration tests more suitable for high-frequency validation.

Related Skills

Explore More Software Engineering Skills→
BurburtonBurburton

module-boundary-design

Formalize module boundaries with inputs, outputs, dependencies, and integration seams.

Community
Advanced
Sheldon-92Sheldon-92
3

Testing

Execute test suites and report failures with coverage metrics.

Community
Intermediate
RangeyRoverRangeyRover
3

speckit.checker

Run static analysis across multiple languages and generate prioritized issue reports.

Community
Intermediate
disciplin-run-orgdisciplin-run-org

unit-test-builder

Generate pytest test suites using adversarial and systematic testing methodologies.

Official
Intermediate