>_SkillsHub▋

> quality-engineering-zephyr-test-generation

Workflow for generating or updating Zephyr Scale Test Cases from requirements. Use when generating or updating Zephyr Scale test cases from user stories or requirements. (triggers: **/*.feature, **/user_story.md, generate test cases, update zephyr, jira validation, impact analysis)

fetch
$curl "https://skillshub.wtf/HoangNguyen0403/agent-skills-standard/quality-engineering-zephyr-test-generation?format=md"
SKILL.md•quality-engineering-zephyr-test-generation

Zephyr Test Generation Standards

Priority: P1 (HIGH)

Workflow: Jira → Zephyr

  1. Analyze Requirements:
    • Identify AC and verify Actor/Permission Matrix.
    • Identify Platform: Detect if requirement applies to Web, Mobile, or Both.
    • Identify Market: Extract Market context (e.g., VN, MY, All).
    • Use Business Analysis for logic investigation.
  2. Impact Analysis:
    • Search Zephyr for existing TCs related to the feature.
    • Perform Impact Study to decide: Update or New.
  3. Draft/Merge TCs:
    • For New: Create following Naming Convention.
    • For Traceability: Call create_test_case_issue_link immediately after creation.
    • For Update: Fetch steps and apply deltas.
  4. Review: Ensure no "OR" logic and steps are atomic.

Output Structure

Metadata & Traceability Standards

  1. Preconditions: Must be extracted from the requirement as a list of bullet points.
  2. Custom Fields: Populate Roles (multi-select) and Platform exactly as shown in requirements.
  3. Traceability (CRITICAL): Always link the TC to the Jira Issue (e.g., EZRX-39448) using the create_test_case_issue_link tool.
  4. Naming: Prefix with [Platform] ONLY if exclusive to one platform. Use the [Module]_[Action]... pattern. Omit platform if it supports Both.
  5. Filing: Use the exact Folder Path specified in the Technical Impact or module standards.

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 --same-repo

> typescript-tooling

Development tools, linting, and build config for TypeScript. Use when configuring ESLint, Prettier, Jest, Vitest, tsconfig, or any TS build tooling. (triggers: tsconfig.json, .eslintrc.*, jest.config.*, package.json, eslint, prettier, jest, vitest, build, compile, lint)

> typescript-security

Secure coding practices for TypeScript. Use when validating input, handling auth tokens, sanitizing data, or managing secrets and sensitive configuration. (triggers: **/*.ts, **/*.tsx, validate, sanitize, xss, injection, auth, password, secret, token)

> typescript-language

Modern TypeScript standards for type safety and maintainability. Use when working with types, interfaces, generics, enums, unions, or tsconfig settings. (triggers: **/*.ts, **/*.tsx, tsconfig.json, type, interface, generic, enum, union, intersection, readonly, const, namespace)

> typescript-best-practices

Idiomatic TypeScript patterns for clean, maintainable code. Use when writing or refactoring TypeScript classes, functions, modules, or async logic. (triggers: **/*.ts, **/*.tsx, class, function, module, import, export, async, promise)

┌ stats

installs/wk0
░░░░░░░░░░
github stars341
██████████
first seenMar 17, 2026
└────────────

┌ repo

HoangNguyen0403/agent-skills-standard
by HoangNguyen0403
└────────────

┌ tags

#testing
└────────────