test-catalog

Assigns test techniques to T-ID ledger behaviors via an index of 40 technique skills.

Updated Jun 24, 2026
One-click install
npx skills add https://github.com/Hakkadaikon/hymme --skill test-catalog-hakkadaikon
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: test-catalog
Source: https://github.com/Hakkadaikon/hymme/tree/main/skills/test-catalog
Command: npx skills add https://github.com/Hakkadaikon/hymme --skill test-catalog-hakkadaikon

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Choosing the right test technique for each behavior under test is error-prone: teams default to ad-hoc cases, over-rely on coverage metrics, or misuse mocks. This Skill provides a curated index of 40 test technique skills and a gated workflow that assigns techniques to every behavior in a T-ID test-design ledger. ## Core Features & Use Cases - Technique Index: A decision table mapping what you want to verify (equivalence partitioning, state transition, pairwise, MC/DC, mutation testing, property-based testing, fuzzing, flakiness handling, non-functional testing, and more) to the exact technique skill to open. - Assignment Gate: Enforces that a technique is only recorded in the ledger after its technique skill has actually been opened, preventing self-invented examples and known pitfalls. - Progressive Disclosure: Only the assigned technique skills are loaded, keeping context lean across the 40-skill catalog. - Use Case: After test-extract produces a T-ID ledger for a payment module, use this Skill to assign boundary value analysis to amount fields, state transition testing to order lifecycle, and mutation testing to verify suite strength, then hand off to test-verify. ## Quick Start Ask the AI to assign test techniques from the test catalog to each T-ID in the test-design ledger for your target module.

Frequently Asked Questions about test-catalog

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

FAQPage Schema
How do I choose the right test technique for each behavior?

Start from the behavior's category (normal, boundary, error, or non-functional) and look it up in the index table, which maps verification goals to technique skills like equivalence partitioning, state transition, or decision tables. Open only the assigned technique skill before writing it into the ledger.

What test design techniques are covered in the catalog?

The catalog indexes 40 technique skills spanning equivalence partitioning, boundary value, decision tables, state transition, pairwise and orthogonal arrays, MC/DC, basis path, mutation testing, TDD cycles, property-based testing, fuzzing, metamorphic testing, golden/snapshot oracles, and non-functional performance and resilience testing.

When should I use pairwise testing versus a decision table?

Use a decision table when business rules combine conditions into distinct outcomes that must all be enumerated. Use pairwise or orthogonal array covering when you need to shrink a large factor combination space while still covering every pair of factor values.

Does this skill work without a completed test ledger?

The full assignment workflow requires a completed T-ID ledger from the extraction phase; without it you should return to the extraction step first. For one-off technique questions, you may consult the index alone without a ledger.

Why is high code coverage not enough to validate tests?

High C0/C1 coverage only shows code was reached, not that behavior was verified. The catalog directs you to mutation testing to measure the suite's actual defect-detection strength and warns against mock overuse that couples tests to implementation details.