qa-testcase-from-docs

Generate structured test cases from requirements documents using ISO 29119-4 models.

2|2|Updated Mar 7, 2026

Search Tags:#requirements analysis #traceability #test design #test case generation #ISO 29119 #test modeling

Ready to run

npx skills add https://github.com/AZANIR/qa-skills --skill qa-testcase-from-docs

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-testcase-from-docs
Source: https://github.com/AZANIR/qa-skills/tree/main/.cursor/skills/qa-testcase-from-docs
Command: npx skills add https://github.com/AZANIR/qa-skills --skill qa-testcase-from-docs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill automates the creation of structured test cases directly from requirements and specification documents, ensuring comprehensive test coverage and traceability.

Core Features & Use Cases

Model-Based Test Generation: Leverages ISO 29119-4 techniques (Equivalence Partitioning, Boundary Value Analysis, State Transition, Decision Tables) to build formal test models.
Traceability: Automatically links generated test cases back to their originating requirements.
Use Case: Transform a product requirements document into a detailed set of positive, negative, boundary, and edge test cases, complete with steps, expected results, and traceability IDs, ready for manual execution or automation.

Quick Start

Generate test cases from the requirements document located at '/path/to/requirements.md'.

Frequently Asked Questions about qa-testcase-from-docs

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

FAQPage Schema

How do I generate test cases from requirements documents?▼

Test case generation from requirements documents normalizes specification inputs and builds formal test models using ISO 29119-4 techniques. It derives positive, negative, and boundary test cases with measurable coverage and traceability links back to the original requirements.

Can I use model-based testing techniques like equivalence partitioning and decision tables for test design?▼

Model-based test design leverages equivalence partitioning, boundary value analysis, state transition, and decision tables to build formal test models. This approach structures test case derivation directly from requirements to ensure comprehensive functional coverage.

How do I export generated test cases to test management tools like Zephyr or TestRail?▼

Generated test cases can be exported directly to test management tools like Zephyr and TestRail. The process formalizes test cases with steps, expected results, and traceability IDs, supporting output in Markdown, JSON, CSV, and native test management formats.

What is the best way to ensure traceability between test cases and product specifications?▼

Traceability between test cases and product specifications is ensured by automatically linking generated test cases back to their originating requirements. This formalizes tests with unique traceability IDs, maintaining measurable coverage throughout the test design process.

Does test case generation from docs support automated test execution frameworks?▼

Test case generation from docs outputs structured test cases complete with steps and expected results ready for manual execution or automation. It formats outputs as JSON or CSV, allowing seamless integration into automated test execution frameworks.

When should I use ISO 29119-4 test modeling for test case generation?▼

ISO 29119-4 test modeling should be used when transforming detailed product requirements into structured test cases. It normalizes requirements to build formal models, ensuring measurable coverage for complex functional validation and edge case identification.