agentsclimarketplace

Quality engineering quality assurance

Skill ComeOnOliver/skillshub/skills/HoangNguyen0403/agent-skills-standard/quality-engineering-quality-assurance

Manual test case standards: enforce 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)From its SKILL.md

Install
npx -y skills add ComeOnOliver/skillshub --skill quality-engineering-quality-assurance

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

1.8 KB, 345 tokens by cl100k_base, as published. Nobody here has run it

Quality Assurance Standards

Priority: P1 (HIGH)

1. Test Case Granularity

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

2. Naming Convention

  • Pattern: ([Platform]) [Module]_[Action] on [Screen] when [Condition]
  • Rule: Only include [Platform] if requirement is exclusive to one platform (e.g., [Mobile]). Omit 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

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

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,144. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.