# Quality Engineering Zephyr Test Generation

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business...

- Repository: https://github.com/HoangNguyen0403/agent-skills-standard (582 stars)
- Category: Testing
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-zephyr-test-generation -g -a claude-code -y`
Codex: `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-zephyr-test-generation -g -a codex -y`
Cursor: `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-zephyr-test-generation -g -a cursor -y`
Gemini CLI: `npx skills add HoangNguyen0403/agent-skills-standard --skill quality-engineering-zephyr-test-generation -g -a gemini-cli -y`

## Description

Generate Zephyr test cases from Jira stories: parse acceptance criteria and business rules, impact-analyze existing TCs (update vs. create new), and draft correctly named test cases. Use for AC-to-test generation; defer post-generation Jira linking and manual test-case quality review.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Zephyr Test Generation Standards

## **Priority: P1 (HIGH)**

## Workflow: Jira → Zephyr

1. **Analyze Requirements**:
 - Extract: Summary, ACs, Platform per AC row, Market, Components.
 - Fetch Jira with `?expand=renderedFields`, HTML authoritative for platform colors:
 `#00B8D9` = Web · `#36B37E` = Mobile · `#FF991F` = Web+Mobile
 - See [Actor/Permission Matrix](../quality-engineering-business-analysis/references/analysis_patterns.md) for role/market logic.
 - HALT on ambiguous AC per `quality-engineering-test-plan-authoring` scenario expansion: ultra-short AC, no expected behavior, bundled ACs, contradiction. Ask before drafting.

2. **Impact Analysis** (run before any TC creation)
 - **Step, Direct Lookup**: Call `Get Issue Link Test Cases` with Jira issue key (e.g., `{PROJECT}-{ID}`).
 - **Step B, Supplemental**: If Step 0, search by `[Module]` and `[Screen]` keywords + check sibling issue links.
 - See [Discovery Protocol](references/impact_analysis.md) for full chain.
 - Map each AC to coverage status:
 - **Covered** → ask user: skip or update to current format?
 - **Partial** → always propose NEW TC.
 - **Not Covered** → always create NEW TC.

3. **Draft Artifact**:
 - Delete any existing `zephyr_test_plan.md` before writing.
 - Follow 4-section format in [TC Format Reference](references/tc_format.md) exactly.
 - After writing: read back file and print full content in chat so user can review without opening it.
 - Ask for: review approval, handling of Covered ACs, and Zephyr Folder ID.

4. **Create in Zephyr** (after explicit user approval)
 - `Create Test Case` (with `customFields` included, no separate Update needed) → `Create Test Case Steps` → `Create Test Case Issue Link`
 - For **updates** to existing TCs: fetch current steps via `Get Test Case Steps`, show before/after diff, wait for explicit approval, then `Update Test Case`.
 - Param contract per [SmartBear API Notes](references/smartbear-api.md).

## Platform Rules

The rest: https://github.com/HoangNguyen0403/agent-skills-standard/blob/HEAD/.agents/skills/quality-engineering/quality-engineering-zephyr-test-generation/SKILL.md