Decision table & Pairwise testing

Generates decision table and pairwise test designs, test cases, and bug reports for EShop requirements.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill decision-table-pairwise-testing-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: Decision table & Pairwise testing
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.agents/skills/Decision%20table%20%26%20Parwise%20Testing
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill decision-table-pairwise-testing-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing systematic functional test cases from a requirements specification is error-prone and time-consuming. This Skill automates the full decision table and pairwise testing workflow for the EShop system, from condition identification through test execution and bug reporting. ## Core Features & Use Cases - Decision Table Test Design: Identifies conditions and outcomes from the EShop spec (README.md and api_specification.md), builds the full decision table, marks impossible combinations, and reduces rules using don't-care merging. - Pairwise Expansion: Detects rules containing don't-care conditions and expands them with pairwise coverage so every pair of condition values appears at least once. - Test Case & Bug Report Generation: Produces one markdown test case file per final test case ID, executes tests against the running app, updates Actual results and Status, and writes bug reports with screenshots for failures. - Use Case: Given requirement FR-09 (coupon codes), the Skill produces DTT-FR09.md with 32 rules reduced to 6 and expanded to 16 pairwise test cases, then generates TC-FR09-01.md through TC-FR09-16.md and bug reports for any failures. ## Quick Start Use the Decision table & Pairwise testing skill to design and run test cases for requirement FR-09 of the EShop system.

Frequently Asked Questions about Decision table & Pairwise testing

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

FAQPage Schema
How do I create test cases using decision table testing?▼

List all conditions and their possible values, enumerate every combination as rules, mark impossible combinations, then merge rules with identical outcomes using don't-care symbols. Each remaining rule becomes a test case with concrete input values and expected results.

When should pairwise testing be applied after a decision table?▼

Apply pairwise testing only when the reduced decision table contains rules with don't-care entries. With three or more don't-care conditions, pairwise selection covers every pair of condition values with far fewer test cases than exhaustive enumeration.

What is a don't care condition in a decision table?▼

A don't care condition, marked with a dash, means the condition's value does not affect the rule's outcome. It appears when two rules differing in exactly one condition produce identical results and are merged during table reduction.

Can decision table testing be used for every software feature?▼

No. Decision table testing suits features where outcomes depend on combinations of input conditions, such as coupon validation or login lockout. Features without meaningful condition combinations cannot use this technique and need another test design method.

How are bug reports generated from failed test cases?▼

When a test case fails, a bug report file is created with the bug description, covered test case, preconditions, steps, expected and actual results, and an optional screenshot. Files follow the naming pattern <function>-bug-<sequence>.md.