blackbox-covering

Generates combinatorial test cases using pairwise, orthogonal array, and T-way covering techniques.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When a system has many independent input factors, testing every combination explodes combinatorially. This Skill reduces the case count by applying factor-coverage techniques—pairwise, orthogonal arrays, and T-way testing—so you still cover critical interactions without exhaustive enumeration. ## Core Features & Use Cases - Pairwise (All-pairs): Covers every value pair of any two parameters at least once, minimizing case count based on the heuristic that most defects arise from two-factor interactions. - Orthogonal Array: Uses balanced assignment tables (L8, L9, etc.) so every pair appears an equal number of times, letting you read main effects of each factor level. - T-way Testing: Generalizes to t-factor combinations (3-way, 4-way) with constraint support to exclude impossible value combinations from the covering array. - Use Case: Testing a checkout page across OS × browser × language × currency. Instead of hundreds of combinations, generate a pairwise covering array with a tool, load it as test data, and run each row as one Vitest case. ## Quick Start Ask the AI to design pairwise test cases for a feature with many independent configuration parameters, such as OS, browser, and language combinations.

Frequently Asked Questions about blackbox-covering

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

FAQPage Schema
How do I reduce test cases when there are too many parameter combinations?

Use pairwise testing to cover every value pair of any two parameters at least once instead of testing all combinations. Generate the minimal covering array with a tool like PICT or ACTS, then run each row as one test case.

What is the difference between pairwise testing and orthogonal arrays?

Pairwise prioritizes coverage: every pair appears at least once, with uneven repetition allowed, yielding fewer cases. Orthogonal arrays use balanced assignment where every pair appears equally often, letting you analyze main effects of each factor level.

When should I use T-way testing instead of pairwise?

Use T-way testing when defects are suspected from interactions of three or more variables, such as authentication method × protocol × cipher suite. Raise t only for suspicious factor groups, since higher t rapidly increases case count.

Can pairwise testing handle impossible value combinations?

Yes, by declaring impossible combinations as constraints passed to the covering array generator. Constraints exclude invalid cases at generation time, but over-constraining can accidentally remove reachable combinations and create coverage gaps.

What are the limitations of pairwise testing?

Pairwise relies on the heuristic that most defects come from two-factor interactions, so it can miss known three-factor bugs. Add such known multi-factor cases explicitly alongside the pairwise set, and never build the minimal set by hand.