OpenSkillIndex← back to search
claude-code

Agent-skills-standard quality-engineering-quality-assurance

Write manual test cases with 1-condition-per-TC granularity, Module_Action on Screen when Condition naming, platform prefix rules, and High/Normal/Low priority classification. Use when writing or reviewing manual test cases for Zephyr — to split compound TCs, fix naming violations, assign correct platform tags, or determine bug priority. (triggers: test case, manual test, zephyr, test scenario, naming convention, acceptance criteria)

install
source · Clone the upstream repo
git clone https://github.com/HoangNguyen0403/agent-skills-standard
Claude Code · Install into ~/.claude/skills/
T=$(mktemp -d) && git clone --depth=1 https://github.com/HoangNguyen0403/agent-skills-standard "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/quality-engineering/quality-engineering-quality-assurance" ~/.claude/skills/hoangnguyen0403-agent-skills-standard-quality-engineering-quality-assurance && rm -rf "$T"
manifest: skills/quality-engineering/quality-engineering-quality-assurance/SKILL.md
source content

Quality Assurance Standards

Priority: P1 (HIGH)

1. Test Case Granularity

  • 1 Test Case = 1 Condition on 1 Screen.
  • Split Screens: "Order Details" & "Item Details" separate.
  • Split Conditions: "Config " & "Config B" separate.
  • No "OR" Logic: Each TC must test single, distinct path.

2. Naming Convention

  • Pattern: 
    Platform_Module_Action on Screen when Condition
    (e.g., 
    Web_Order_Verify...
    or 
    Mobile_Order_Verify...
    )
  • Rule: Only include 
    Web_
    or 
    Mobile_
    prefix if requirement exclusive to one platform. Omit prefix if it supports Both.
  • Example: 
    Order_Verify payment term on Item Details when Toggle is OFF
    (Supports Both)

3. Priority Levels

Use priority rationale to justify each classification:

  • High: Critical path, blocker bug.
  • Normal: Standard validation, edge case.
  • Low: Cosmetic, minor improvement.

4. References

Anti-Patterns

  • No Broad TCs: 
    "Verify order flow works"
    — too broad; every TC must cover exactly 1 condition on 1 screen
  • No Shared TCs (Divergent): Testing Web and Mobile behavior in single TC when behavior diverges — split into separate TCs per platform
  • No Incomplete Naming: 
    Order_Verify page
    — name must follow full pattern: 
    Module_Action on Screen when Condition
  • No Priority Inflation: Marking cosmetic spacing bug as High priority — reserve High for critical path blockers only