hoangnguyen0403/quality-engineering-quality-assurance

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

• Detailed Examples

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