testing

Implement behavior-driven testing patterns through public APIs.

1|Updated Mar 22, 2026
One-click install
npx skills add https://github.com/mikemyl/verified-development --skill testing-mikemyl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: testing
Source: https://github.com/mikemyl/verified-development/tree/main/skills/testing
Command: npx skills add https://github.com/mikemyl/verified-development --skill testing-mikemyl

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill unit provides guidance on behavior-driven testing patterns and best practices, helping developers write more effective and maintainable tests.

Core Features & Use Cases

  • Behavior-Driven Testing: Encourages testing behavior rather than implementation details for better coverage and maintainability.
  • Actor-BDD Craft Rules: Offers language-neutral guidelines for crafting tests using Behavior-Driven Development (BDD) principles.
  • Mutation-Aware Test Planning: Suggests strategies for identifying gaps in test coverage using mutation analysis.
  • Test Through Public API Only: Promotes testing behavior through public APIs to ensure tests remain valid during refactoring.
  • Coverage Through Behavior: Emphasizes that validation code should be tested through its behavior, not implementation details.
  • Test Factory Pattern: Provides guidelines for creating test data with factory functions to ensure fresh state and maintainability.
  • No 1:1 Mapping Between Tests and Implementation: Advocates for not creating test files that mirror implementation files to ensure tests remain independent of implementation changes.

Quick Start

Load the 'testing' skill to implement behavior-driven testing patterns in your project.

Frequently Asked Questions about testing

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

FAQPage Schema
How do I write behavior-driven tests that focus on behavior over implementation?

Testing through public APIs validates external behavior without coupling tests to internal implementation details. This approach ensures tests remain valid during refactoring and improves long-term code maintainability.

What is the best way to manage test data in behavior-driven development?

Using factory functions for test data creation ensures a fresh state for each test run. This test factory pattern provides maintainable data generation, avoiding the pitfalls of shared or static test fixtures.

Why should I avoid a 1:1 mapping between test files and implementation files?

Avoiding a 1:1 file mapping ensures tests remain independent of implementation changes. This practice encourages testing behavior through public APIs rather than mirroring structural implementation details, improving test resilience.

How do I find gaps in my test coverage using mutation analysis?

Mutation-aware test planning identifies coverage gaps by intentionally modifying code to see if existing tests fail. This strategy highlights untested behavior paths and strengthens overall code quality assurance.

Can I use behavior-driven testing patterns for any programming language?

Yes, behavior-driven testing patterns utilize language-neutral guidelines for crafting tests. These BDD principles focus on validating behavior through public APIs, making them applicable across different programming languages and tech stacks.