---
name: qa-test-cases
description: Generate structured manual and automation-ready test cases from requirements, stories, UI behavior, APIs, or Jira issue context.
---

# QA Test Cases Skill

Use this skill when the user asks Copilot to create test cases, test scenarios, edge cases, regression cases, or automation-ready test coverage.

## Inputs To Ask For

- Requirement, user story, Jira issue key, API contract, or UI flow
- Acceptance criteria
- User roles and permissions
- Test environment and data constraints
- Priority rules and risk areas
- Automation target, if any

## Output Format

Return a table with these columns:

| ID | Scenario | Precondition | Steps | Test Data | Expected Result | Priority | Type | Automation Candidate |
|---|---|---|---|---|---|---|---|---|

After the table, add:

- Boundary and negative cases
- Regression impact areas
- Automation notes
- Requirement traceability notes

## Rules

- Include positive, negative, boundary, role-based, and integration cases when relevant.
- Write steps that a tester can execute without guessing.
- Keep expected results observable and measurable.
- Mark automation candidates as `Yes`, `No`, or `Later` with a short reason.
- If Jira MCP tools are available, read the target Jira ticket and linked issues before creating cases.

## Example Prompt

Create manual and automation-ready test cases for Jira story `PROJ-142`. Include positive, negative, boundary, and regression cases.