test-approach

Analyze code and public interfaces to generate or refine tests.

Updated Apr 30, 2026

Search Tags:#unit-testing #test #code-review #test-coverage #golden-path #behavior-focused #testing-philosophy

Ready to run

npx skills add https://github.com/wapgear/izmailov-skills --skill test-approach

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: test-approach
Source: https://github.com/wapgear/izmailov-skills/tree/main/skills/test-approach
Command: npx skills add https://github.com/wapgear/izmailov-skills --skill test-approach

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Helps development teams design, review, and improve tests by applying Izmailov's testing philosophy to codebases and test suites.

Core Features & Use Cases

Analyze code and identify public APIs and behavior to validate existing tests.
Generate new tests or extend coverage to address golden-path scenarios, edge cases, and error handling.
Review test suites to align with the project's testing principles and improve readability and maintainability.

Quick Start

Analyze a codebase and generate or augment tests following Izmailov's testing philosophy.

Frequently Asked Questions about test-approach

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

FAQPage Schema

How do I generate behavior-focused unit tests for existing code?▼

Generate behavior-focused unit tests by analyzing public interfaces to validate golden-path scenarios and edge cases, ensuring tests prioritize behavior over implementation and use minimal mocks.

What is the best way to review test coverage and identify testing gaps?▼

Review test coverage by analyzing code and public APIs to identify testing gaps, then refine existing tests to align with behavior-driven testing principles and improve readability.

How do I improve test maintainability when my test suite relies heavily on mocks?▼

Improve test maintainability by enforcing a testing philosophy that prioritizes behavior over implementation, using minimal mocks, and adopting clear test names for better readability.

Can I use this approach for both integration and end-to-end test scenarios?▼

Yes, this testing approach applies to unit, integration, and end-to-end scenarios across various languages and frameworks to generate or refine tests based on behavior validation.

Why should my tests focus on behavior instead of implementation details?▼

Tests should focus on behavior instead of implementation details to enforce clear test names and minimal mocks, resulting in more maintainable and readable test suites.

What's the best way to add tests for error handling and edge cases?▼

Add tests for error handling and edge cases by analyzing public interfaces to extend coverage, validating golden-path scenarios while applying behavior-driven testing principles.