Mapping Requirements to Test Cases

When to use this skill

• When the user provides a "Requirement document" and "Existing test cases" (Excel or JIRA Ticket ID).
• When asked to identify "Missing test cases", "Duplicate test cases", and "Incomplete coverage".
• When a requirement-to-test-case mapping/gap analysis report is needed.

Workflow

1.Requirement Extraction:

Read the requirement document (PDF, Text, Word, or Markdown). Parse and identify unique Requirements (e.g., REQ-001, FR-01, or bullet points). Store Requirement IDs and Descriptions in a list.

2. Test Case Extraction:

Excel/CSV: Use pandas to load the file. Identify columns for "Test Case ID", "Test Description", and "Requirement Mapping/Requirement ID". JIRA: If a JIRA Ticket ID is provided, use available JIRA tools (or ask user for details) to fetch the "Test Issues" linked to the requirement.

3. Cross-Mapping & Gap Analysis:

Covered: A requirement is covered if it appears in the "Requirement Mapping" column of at least one test case. Missing: A requirement is missing if no test case maps to it. Duplicates: Flag requirements that have multiple test cases covering the exact same validation logic. Incomplete: Flag requirements that have a test case but lack specific edge cases (e.g., negative testing).

4. Reporting:

Generate the summary report in the table format requested.