quality-engineering-zephyr-test-generation
End-to-end Jira → Zephyr workflow: parse AC, identify platform and market, impact-analyze existing TCs (update vs create new), draft test cases with correct naming/metadata/preconditions, and link back via create_test_case_issue_link. Use when converting a Jira story into Zephyr TCs, or when requirement changes require updating existing TCs rather than creating duplicates. (triggers: **/user_story.md, generate test cases, zephyr, impact analysis, create test case)
Best use case
quality-engineering-zephyr-test-generation is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
End-to-end Jira → Zephyr workflow: parse AC, identify platform and market, impact-analyze existing TCs (update vs create new), draft test cases with correct naming/metadata/preconditions, and link back via create_test_case_issue_link. Use when converting a Jira story into Zephyr TCs, or when requirement changes require updating existing TCs rather than creating duplicates. (triggers: **/user_story.md, generate test cases, zephyr, impact analysis, create test case)
Teams using quality-engineering-zephyr-test-generation should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/quality-engineering-zephyr-test-generation/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How quality-engineering-zephyr-test-generation Compares
| Feature / Agent | quality-engineering-zephyr-test-generation | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
End-to-end Jira → Zephyr workflow: parse AC, identify platform and market, impact-analyze existing TCs (update vs create new), draft test cases with correct naming/metadata/preconditions, and link back via create_test_case_issue_link. Use when converting a Jira story into Zephyr TCs, or when requirement changes require updating existing TCs rather than creating duplicates. (triggers: **/user_story.md, generate test cases, zephyr, impact analysis, create test case)
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# Zephyr Test Generation Standards
## **Priority: P1 (HIGH)**
## Workflow: Jira → Zephyr
1. **Analyze Requirements**:
- Identify **Acceptance Criteria (AC)** and verify **Actor/Permission Matrix**.
- Perform **Atomic AC Decomposition**: Break down complex ACs into individual testable units (1 statement = 1 TC).
- **Identify Platform**: Detect if requirement applies to **`Web`**, **`Mobile`**, or **`Both`**.
- **Identify Market**: Extract Market context (e.g., **`VN`**, `MY`, `SG`, `All`).
2. **Impact Analysis**:
- **Search Zephyr** for **Existing TCs** related to the feature before creating new ones.
- Perform **Impact Analysis** to decide: **Update those TCs** (change logic) existing TCs or create **New** (new feature) TCs. Ensure you don't create **duplicates** by updating existing ones first. Document delta changes in TC description.
3. **Draft/Merge TCs**:
- Create/Update TCs with correct **Zephyr Key** (e.g., `EZRX-T123`).
- **Traceability**: **Link TC to the Jira Ticket ID** (e.g., **`EZRX-3892`**) immediately via **`create_test_case_issue_link`**.
4. **Review**: Ensure no "OR" logic and steps are **Atomic**. Use **separate TCs per actor** (no OR logic) when different roles see different data. Use **Truth Table Verification** for multi-condition ACs.
## Metadata & Traceability Standards
1. **Preconditions**: Must be extracted from the requirement as a list of **bullet points**.
2. **Priority**: Classify as **High**, **Normal**, or **Low** based on business impact.
3. **Traceability (CRITICAL)**: Always link the TC to the **Jira Ticket ID** using the **`create_test_case_issue_link`** tool.
4. **Naming**: Prefix with **`[Web]`** or **`[Mobile]`** ONLY if exclusive. **No [Platform] prefix** if it applies to Both. Pattern: **`Module_Action on Screen when user is {Actor} ({Market})`**. Example: **`[Web] Invoice_Download invoice on Order Detail when user is Customer (VN)`**.
## Anti-Patterns
- **Ghost Updates**: Changing code without updating the corresponding Zephyr TC.
- **Duplicate Creation**: Creating a new TC for a logic shift when an update was more appropriate.
- **Vague Steps**: `System works` -> `Expect Result: Banner 'Success' is visible`.Related Skills
vitest-test-creator
Vitest Test Creator - Auto-activating skill for Test Automation. Triggers on: vitest test creator, vitest test creator Part of the Test Automation skill category.
performing-visual-regression-testing
This skill enables Claude to execute visual regression tests using tools like Percy, Chromatic, and BackstopJS. It captures screenshots, compares them against baselines, and analyzes visual differences to identify unintended UI changes. Use this skill when the user requests visual testing, UI change verification, or regression testing for a web application or component. Trigger phrases include "visual test," "UI regression," "check visual changes," or "/visual-test".
generating-unit-tests
This skill enables Claude to automatically generate comprehensive unit tests from source code. It is triggered when the user requests unit tests, test cases, or test suites for specific files or code snippets. The skill supports multiple testing frameworks including Jest, pytest, JUnit, and others, intelligently detecting the appropriate framework or using one specified by the user. Use this skill when the user asks to "generate tests", "create unit tests", or uses the shortcut "gut" followed by a file path.
train-test-splitter
Train Test Splitter - Auto-activating skill for ML Training. Triggers on: train test splitter, train test splitter Part of the ML Training skill category.
test-retry-config
Test Retry Config - Auto-activating skill for Test Automation. Triggers on: test retry config, test retry config Part of the Test Automation skill category.
generating-test-reports
This skill generates comprehensive test reports with coverage metrics, trends, and stakeholder-friendly formats (HTML, PDF, JSON). It aggregates test results from various frameworks, calculates key metrics (coverage, pass rate, duration), and performs trend analysis. Use this skill when the user requests a test report, coverage analysis, failure analysis, or historical comparisons of test runs. Trigger terms include "test report", "coverage report", "testing trends", "failure analysis", and "historical test data".
test-parallelizer
Test Parallelizer - Auto-activating skill for Test Automation. Triggers on: test parallelizer, test parallelizer Part of the Test Automation skill category.
test-organization-helper
Test Organization Helper - Auto-activating skill for Test Automation. Triggers on: test organization helper, test organization helper Part of the Test Automation skill category.
test-naming-enforcer
Test Naming Enforcer - Auto-activating skill for Test Automation. Triggers on: test naming enforcer, test naming enforcer Part of the Test Automation skill category.
managing-test-environments
This skill enables Claude to manage isolated test environments using Docker Compose, Testcontainers, and environment variables. It is used to create consistent, reproducible testing environments for software projects. Claude should use this skill when the user needs to set up a test environment with specific configurations, manage Docker Compose files for test infrastructure, set up programmatic container management with Testcontainers, manage environment variables for tests, or ensure cleanup after tests. Trigger terms include "test environment", "docker compose", "testcontainers", "environment variables", "isolated environment", "env-setup", and "test setup".
generating-test-doubles
This skill uses the test-doubles-generator plugin to automatically create mocks, stubs, spies, and fakes for unit testing. It analyzes dependencies in the code and generates appropriate test doubles based on the chosen testing framework, such as Jest, Sinon, or others. Use this skill when you need to generate test doubles, mocks, stubs, spies, or fakes to isolate units of code during testing. Trigger this skill by requesting test double generation or using the `/gen-doubles` or `/gd` command.
generating-test-data
This skill enables Claude to generate realistic test data for software development. It uses the test-data-generator plugin to create users, products, orders, and custom schemas for comprehensive testing. Use this skill when you need to populate databases, simulate user behavior, or create fixtures for automated tests. Trigger phrases include "generate test data", "create fake users", "populate database", "generate product data", "create test orders", or "generate data based on schema". This skill is especially useful for populating testing environments or creating sample data for demonstrations.