Skip to main content

QA Error Handling Template

Purpose: Standard error handling for all test cases
Usage: Include this section in every test case

Error Handling Section (Add to Each Test Case)​

**Error Handling:**
- If feature is not accessible: Mark as "BLOCKED - [reason]" and skip remaining steps
- If feature loads but errors: Document error, mark as "PARTIAL - [error description]"
- If feature works: Proceed with full test

**Error Documentation:**
- Error Type: [BLOCKED / PARTIAL / COSMETIC / FUNCTIONAL]
- Error Description: [What happened]
- Screenshot: [Attach if possible]
- Workaround: [If any]
- Story ID: [Which story this relates to]

Error Type Definitions​

🔴 BLOCKED​

Feature completely broken, cannot proceed with testing.

  • Action: Document blocker, skip detailed testing, move to next test case
  • Example: "Cannot access service request creation page - 404 error"

🟠 PARTIAL​

Feature partially works, some functionality broken.

  • Action: Test what works, document what doesn't, continue testing
  • Example: "Service request creates but photo upload fails"

🟡 COSMETIC​

Feature works but UI/UX issues.

  • Action: Document issue, continue testing, note for later fix
  • Example: "Button text overlaps on mobile view"

🟢 FUNCTIONAL​

Feature works but behavior doesn't match expected.

  • Action: Document expected vs actual, continue testing
  • Example: "Work order status updates but notification not sent"

Error Reporting Format​

Test Case: W1.1 - Worker creates service request
Error Type: 🟠 PARTIAL
Error Description: Service request form loads but "Submit" button is disabled after filling required fields. Console shows validation error: "Property ID is required" even though property is selected.
Screenshot: screenshots/w1.1-error-property-validation.png
Workaround: Refresh page, select property again, then submit
Story ID: SPRINT0-004
SEV1 Risk: 🔴 HIGH - Blocks service request creation

Quick Error Checklist​

When encountering an error:

  • Document error type (BLOCKED/PARTIAL/COSMETIC/FUNCTIONAL)
  • Take screenshot (if possible)
  • Note error message/console errors
  • Identify story ID affected
  • Note SEV1 risk level
  • Document workaround (if any)
  • Continue testing (if partial) or skip (if blocked)
  • Update Testability Matrix

Common Error Patterns​

  • Symptom: Cannot access page, 404 error
  • Check: URL, permissions, tenant routing
  • Document: Navigation path attempted, error message

Form Submission Errors​

  • Symptom: Form doesn't submit, validation errors
  • Check: Required fields, data format, network errors
  • Document: Form data entered, validation messages

Permission Errors​

  • Symptom: Action not allowed, button disabled
  • Check: User role, RLS policies, feature flags
  • Document: User role, action attempted, error message

Data Display Errors​

  • Symptom: Data not showing, incorrect data
  • Check: Filters, refresh, data source
  • Document: Expected data, actual data shown

Usage: Copy error handling section into each test case documentation