Skip to main content

QA Phased Execution Plan

Purpose: Structured approach to testing all workflows
Goal: Discover what's actually implemented vs documented

Phase 1: Testability Pass (Days 1-2)​

Goal: Identify what's testable vs completely broken

Tasks:

  1. Quick smoke test of all 25 workflows
  2. Update Testability Matrix
  3. Identify critical blockers
  4. Prioritize workflows for detailed testing
  5. Set up minimal configuration (2 categories, 1-2 locations) for Phase 2

Configuration Setup:

  • Create 2-3 basic categories
  • Create 1-2 locations (hierarchy: Building > Room)
  • Create 1 basic SLA rule (if needed)
  • Create 1 assignment group (if needed)
  • Keep it minimal - focus on testability, not configuration

Output:

  • Testability Matrix completed
  • Blocker list (critical issues)
  • Prioritized workflow list
  • Minimal configuration ready for Phase 2

Time: 1-2 days

Phase 2: Core Workflows (Days 3-5)​

Goal: Test critical paths that everything else depends on

Workflows:

  • W1: Service Request to Work Order Completion
  • W2: Guest Portal with Chatbot
  • W3: Direct Work Order + Assignment Group
  • W4: Work Order with Inspection
  • W5: On Hold + Reason Codes
  • W6: Active Time Tracking
  • W7: Multiple Work Orders
  • W8: SLA Rules + Priority

Configuration Approach: MINIMAL SETUP

  • Use basic/minimal configuration to keep focus on workflows
  • Categories: 2-3 categories (e.g., "Plumbing", "Electrical")
  • Locations: 1-2 locations (e.g., "Building A > Room 101")
  • Assets: 1-2 assets (optional)
  • SLA Rules: 1 basic rule (if needed for W8)
  • Assignment Groups: 1 group (if needed for W3)
  • Checklists: Use existing or skip (test in Phase 3)

Focus:

  • Full workflow testing (not configuration features)
  • Multi-browser interactions
  • Error documentation
  • Playwright script capture
  • Do NOT test CRUD operations - that's Phase 3

Output:

  • 8 workflows fully tested
  • Defect list (SEV1 prioritized)
  • Playwright scripts captured

Time: 3-5 days

Phase 3: Master Data (Days 6-7)​

Goal: Test configuration features themselves (CRUD, validation, hierarchy)

Workflows:

  • W9: Locations Management
  • W10: Assets Management
  • W11: Categories Management
  • W12: SLA Rules Management
  • W13: Checklist Templates
  • W14: Assignment Groups

Configuration Approach: FULL TESTING

  • Test all CRUD operations (Create, Read, Update, Delete)
  • Test data validation (required fields, formats, constraints)
  • Test hierarchy management (parent-child relationships)
  • Test edge cases (duplicate names, invalid data, etc.)
  • Build out full configuration for later phases if needed

Focus:

  • Configuration feature functionality (not workflows)
  • CRUD operations completeness
  • Data validation rules
  • Hierarchy management
  • Error handling in configuration

Output:

  • 6 workflows tested
  • Master data setup verified
  • Configuration defects documented
  • Full configuration available for later phases

Time: 2 days

Note: After Phase 3, you'll have a fully configured system for testing advanced features in Phase 4+

Phase 4: Advanced Features (Days 8-9)​

Goal: Verify partially implemented features

Workflows:

  • W15: Parts Catalog (VERIFY)
  • W16: Service Request Status Lifecycle (VERIFY)
  • W17: Room Status + Phase 5 Features (VERIFY)

Focus:

  • Test what exists
  • Document what's missing
  • Verify database vs UI alignment

Output:

  • Verification results
  • Gap analysis (what's missing)
  • Partial implementation status

Time: 2 days

Phase 5: Guest/Mobile Experience (Day 10)​

Goal: Test user-facing features

Workflows:

  • W18: Guest Member Mobile Experience
  • W25: Mobile Responsiveness

Focus:

  • Mobile usability
  • Guest experience
  • Responsive design

Output:

  • Mobile testing results
  • UX issues documented
  • Guest flow verified

Time: 1 day

Phase 6: Notifications & Settings (Day 11)​

Goal: Test configuration and communication

Workflows:

  • W19: Notification System
  • W20: Settings Management

Focus:

  • Notification delivery
  • Settings persistence
  • User preferences

Output:

  • Notification testing results
  • Settings verification
  • Configuration defects

Time: 1 day

Phase 7: Onboarding (Day 12)​

Goal: Test tenant setup process

Workflows:

  • W21: Onboarding Wizard

Focus:

  • Complete onboarding flow
  • Data import
  • Slug validation
  • Subdomain setup

Output:

  • Onboarding flow verified
  • Setup defects documented

Time: 1 day

Phase 8: Dashboards & Analytics (Day 13)​

Goal: Test reporting and KPIs

Workflows:

  • W22: Manager KPI Dashboard
  • W23: Worker KPI Dashboard

Focus:

  • Data accuracy
  • Metric calculations
  • Dashboard performance

Output:

  • Dashboard testing results
  • KPI accuracy verified
  • Analytics defects

Time: 1 day

Phase 9: Security & RBAC (Day 14)​

Goal: Validate permissions and security

Workflows:

  • W24: RBAC Testing

Focus:

  • Permission enforcement
  • Multi-tenant isolation
  • Unauthorized access prevention

Output:

  • Security testing results
  • RBAC verification
  • Security defects (if any)

Time: 1 day

Phase 10: Defect Triage & Documentation (Days 15-16)​

Goal: Prioritize defects and finalize documentation

Tasks:

  1. Review all defects
  2. Prioritize by SEV1 risk
  3. Update Testability Matrix
  4. Create defect summary
  5. Update feature list based on testing
  6. Finalize Playwright scripts

Output:

  • Prioritized defect list
  • Updated feature list (as-built)
  • Complete test documentation
  • Playwright script library

Time: 2 days

Configuration Strategy Summary​

Phase 1: Minimal setup (2 categories, 1-2 locations) - just enough to test workflows
Phase 2: Use minimal config - focus on workflows, not configuration features
Phase 3: Test configuration features themselves - build out full config
Phase 4+: Use full configuration from Phase 3 for advanced feature testing

Benefits:

  • ✅ Faster Phase 2 testing (no time spent on complex setup)
  • ✅ Clear separation: workflows vs configuration features
  • ✅ Phase 3 builds full config for later phases
  • ✅ Configuration defects isolated to Phase 3

Total Timeline​

Estimated: 14-16 days
With Buffer: 3 weeks

Daily Checklist​

Each Day:

  • Update Testability Matrix
  • Document all errors encountered
  • Capture Playwright scripts (if feature works)
  • Update workflow checklist (mark completed)
  • Note blockers for next day

End of Day:

  • Review defects found
  • Prioritize for next day
  • Update progress tracker

Success Criteria​

Phase 1 Complete When:

  • All workflows testability checked
  • Blocker list created
  • Prioritized plan finalized

Phase 2-9 Complete When:

  • All test cases executed
  • All errors documented
  • Playwright scripts captured (for working features)

Phase 10 Complete When:

  • All defects triaged
  • Feature list updated (as-built)
  • Test documentation complete
  • Ready for stakeholder review

Start Date: _______________
Target Completion: _______________