Quality Assurance

Standards for creating high-quality, granular manual test cases and QA processes.

mte90 7d35297 3 files · 3.2 KB Updated

File contents

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

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

4. References

  • Detailed Examples

mte90/dotfiles/tree/main/.config/opencode/skills/quality-engineering/quality-assurance commit 7d35297241

Frequently asked questions

npx skillmds@latest add mte90/quality-assurance