dt-test-designer

Generates decision-table test cases, test runs, bug reports, and traceability matrices from EShop requirements.

Updated Jun 8, 2026
One-click install
npx skills add https://github.com/DuyITLOR/group05_eshop --skill dt-test-designer-duyitlor
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: dt-test-designer
Source: https://github.com/DuyITLOR/group05_eshop/tree/main/.claude/skills/dt-test-designer
Command: npx skills add https://github.com/DuyITLOR/group05_eshop --skill dt-test-designer-duyitlor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Designing complete, spec-compliant test documentation for a software requirement is slow and error-prone. This Skill automates the full Decision Table testing workflow for the EShop system, turning one functional requirement (FR-xx) from the README spec into a consistent set of test artifacts that follow the course's Test Case & Bug Management conventions. ## Core Features & Use Cases - Decision Table Construction: Reads the requirement spec, identifies Conditions and Actions, builds the full 2^n table, then collapses it with don't-care rules into a minimal rule set. - Full Artifact Generation: Produces a Test Design document, individual Test Case files (TC-[MODULE]-NNN), Test Run records, Bug Reports for failed cases, and a Traceability Matrix linking requirements to tests and bugs. - Convention Enforcement: Applies strict naming (TC-REGISTER-001), valid statuses (Pass/Fail/Blocked/Not Run), and bidirectional Test Case ↔ Bug linking required by the course. - Use Case: Ask it to apply the decision table technique to FR-01 (Registration); it outputs DT-REGISTER.md plus six isolated-cause test cases ready for submission under HW/week04. ## Quick Start Ask the assistant to write test cases using the decision table technique for FR-01 of the EShop spec, outputting to the default homework directory.

Frequently Asked Questions about dt-test-designer

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

FAQPage Schema
How do I write test cases using the decision table technique?▼

Identify each business rule as a boolean Condition, define the Actions (success and error outcomes), build the full 2^n table, then collapse columns using don't-care entries so each rule isolates one failing condition. Each resulting rule becomes one test case.

How to generate test cases for a requirement like FR-01 registration?▼

Invoke the skill with the target FR number; it reads the spec from README.md, derives conditions such as valid email and strong password, and outputs a test design document plus TC-REGISTER-001 through TC-REGISTER-006 test case files.

What naming convention do the generated test cases follow?▼

Test cases use the format TC-[MODULE]-[NUMBER], for example TC-REGISTER-001, with a three-digit incrementing number. The module is derived from the requirement, such as REGISTER for FR-01 or LOGIN for FR-02.

Does the skill execute the application to fill in actual test results?▼

Execution is optional. If you choose not to run the app, test cases are marked Not Run and no bug reports are created. If you run it, actual results are recorded and bug reports are generated for failed cases.

When is a bug report created and what must it contain?▼

A bug report is created only for test cases with Fail or Blocked results. It must reference the discovering test case, the related requirement, severity and priority, environment, reproduction steps, expected and actual results, and evidence.