Skip to main content

QA Test Suite - Workflow Checklist

Purpose: Complete test coverage of all implemented features (non-backlog, non-obsolete)
Method: Multi-browser workflow testing (2-4 browsers per workflow)
Execution: One tester, sequential workflows, shared test items

Testability Status Legend​

  • ✅ TESTABLE - Proceed with full test
  • ⚠️ PARTIAL - Test what works, document blockers
  • ❌ BLOCKED - Feature not accessible, skip detailed testing
  • 🔍 VERIFY - Needs verification (partially implemented stories)

Core Workflows (Priority 1: Critical Paths)​

Workflow 1: Service Request to Work Order Completion​

Browsers: 2 (Worker, Manager)
Stories: SPRINT0-004, SPRINT0-005, SPRINT0-006, SPRINT0-008, SPRINT0-009, SPRINT0-010, SPRINT0-011, SPRINT0-012

  • 1.1: Worker creates service request (with photo)
  • 1.2: Manager views service request list (filtering)
  • 1.3: Manager views service request detail
  • 1.4: Manager converts service request to work order
  • 1.5: Manager assigns work order to worker
  • 1.6: Worker views assigned work orders (filtering)
  • 1.7: Worker views work order detail
  • 1.8: Worker starts work (status: assigned → in_progress)
  • 1.9: Worker adds photo attachment to work order
  • 1.10: Worker posts comment on work order
  • 1.11: Manager views work order, adds comment
  • 1.12: Worker completes work (status: in_progress → done)
  • 1.13: Manager reviews audit trail
  • 1.14: Manager closes work order

Testability: ✅ TESTABLE

Workflow 2: Guest Portal with Chatbot​

Browsers: 3 (Guest/Public, Manager, Worker)
Stories: SPRINT2-005, SPRINT0-006, SPRINT1-039, SPRINT0-008, SPRINT0-010

  • 2.1: Guest accesses guest portal (unauthenticated)
  • 2.2: Guest uses conversational chatbot to triage
  • 2.3: Guest submits service request (with guest info, photo)
  • 2.4: Manager views guest service request
  • 2.5: Manager creates multiple work orders from service request
  • 2.6: Manager assigns work orders to different workers
  • 2.7: Workers receive notifications
  • 2.8: Workers complete work orders
  • 2.9: Manager verifies service request status updates

Testability: ✅ TESTABLE

Workflow 3: Direct Work Order with Assignment Group​

Browsers: 3 (Manager, Manager2, Worker)
Stories: SPRINT0-007, SPRINT1-048, SPRINT0-008, SPRINT0-010, SPRINT0-029

  • 3.1: Manager creates direct work order (no service request)
  • 3.2: Manager assigns work order to assignment group
  • 3.3: Multiple managers in group receive notifications
  • 3.4: Worker from group views assigned work order
  • 3.5: Worker starts work, adds attachment
  • 3.6: Worker completes work order
  • 3.7: All group members see completion update

Testability: ✅ TESTABLE

Workflow 4: Work Order with Inspection​

Browsers: 3 (Worker, Manager, Inspector)
Stories: SPRINT0-010, SPRINT1-045, SPRINT0-012

  • 4.1: Worker completes work order
  • 4.2: Manager sends work order for inspection
  • 4.3: Inspector views work order
  • 4.4: Inspector approves/rejects inspection
  • 4.5: Manager handles inspection result
  • 4.6: Audit trail shows inspection workflow

Testability: ✅ TESTABLE

Workflow 5: Work Order On Hold with Reason Codes​

Browsers: 2 (Worker, Manager)
Stories: SPRINT0-010, SPRINT1-037, SPRINT1-034

  • 5.1: Worker starts work order
  • 5.2: Worker puts work order on hold (with reason code)
  • 5.3: SLA pauses (verify time tracking)
  • 5.4: Manager views on-hold work order
  • 5.5: Worker resumes work (SLA resumes)
  • 5.6: Worker completes work order
  • 5.7: Manager verifies final time/SLA

Testability: ✅ TESTABLE

Workflow 6: Active Time Tracking​

Browsers: 2 (Manager, Worker)
Stories: SPRINT1-055, SPRINT0-010, SPRINT1-034

  • 6.1: Manager assigns work order to worker
  • 6.2: Worker starts work (active time starts)
  • 6.3: Worker puts on hold (active time pauses)
  • 6.4: Worker resumes work (active time resumes)
  • 6.5: Worker completes (final active time displayed)
  • 6.6: Manager verifies time tracking accuracy

Testability: ✅ TESTABLE

Workflow 7: Multiple Work Orders from Service Request​

Browsers: 3 (Worker, Manager, Worker2)
Stories: SPRINT0-004, SPRINT1-039, SPRINT0-008, SPRINT0-010

  • 7.1: Worker creates service request
  • 7.2: Manager views service request
  • 7.3: Manager creates 3 work orders from service request
  • 7.4: Manager assigns work orders to different workers
  • 7.5: Workers receive notifications
  • 7.6: Workers complete work orders independently
  • 7.7: Manager verifies service request status (all work orders complete)

Testability: ✅ TESTABLE

Workflow 8: SLA Rules and Priority Calculation​

Browsers: 2 (Manager, Worker)
Stories: SPRINT1-043, SPRINT1-036, SPRINT0-016, SPRINT0-010

  • 8.1: Manager creates SLA rule (category + priority)
  • 8.2: Manager creates work order (category triggers priority calc)
  • 8.3: Work order shows calculated priority
  • 8.4: Work order shows SLA due date (from rule)
  • 8.5: Worker starts work
  • 8.6: Worker completes before SLA due date
  • 8.7: Manager verifies SLA compliance

Testability: ✅ TESTABLE

Master Data Management Workflows (Priority 2: Configuration)​

Workflow 9: Locations Management​

Browsers: 2 (Manager, Operations_Director)
Stories: SPRINT0-013

  • 9.1: Manager creates location (Building)
  • 9.2: Manager creates child location (Floor)
  • 9.3: Manager creates child location (Room)
  • 9.4: Manager edits location
  • 9.5: Operations_Director deletes location (verify hierarchy)

Testability: ✅ TESTABLE

Workflow 10: Assets Management​

Browsers: 1 (Manager)
Stories: SPRINT0-014

  • 10.1: Manager creates asset
  • 10.2: Manager links asset to location
  • 10.3: Manager edits asset
  • 10.4: Manager views asset in work order context
  • 10.5: Manager deletes asset

Testability: ✅ TESTABLE

Workflow 11: Categories Management​

Browsers: 2 (Admin, Operations_Director)
Stories: SPRINT0-015, SPRINT1-024, SPRINT1-057

  • 11.1: Manager views standard categories (seeded)
  • 11.2: Admin or Operations_Director creates custom category
  • 11.3: Admin or Operations_Director creates child category (hierarchy)
  • 11.4: Admin or Operations_Director edits category
  • 11.5: Admin or Operations_Director validates category hierarchy (parent-child)
  • 11.6: Admin or Operations_Director deletes category

Testability: ✅ TESTABLE

Workflow 12: SLA Rules Management​

Browsers: 2 (Admin, Operations_Director)
Stories: SPRINT0-016, SPRINT1-043

  • 12.1: Admin or Operations_Director creates SLA rule (category + priority)
  • 12.2: Admin or Operations_Director edits SLA rule
  • 12.3: Manager views SLA rules list
  • 12.4: Admin deletes SLA rule
  • 12.5: Manager verifies SLA applies to work orders

Testability: ✅ TESTABLE

Workflow 13: Checklist Templates​

Browsers: 2 (Manager, Worker)
Stories: SPRINT0-017, SPRINT0-018

  • 13.1: Manager creates checklist template
  • 13.2: Manager adds items to checklist
  • 13.3: Manager edits checklist template
  • 13.4: Manager attaches checklist to work order
  • 13.5: Worker views checklist on work order
  • 13.6: Worker completes checklist items
  • 13.7: Manager views completed checklist

Testability: ✅ TESTABLE

Workflow 14: Assignment Groups Management​

Browsers: 4 (Manager, Manager2, Admin, Worker)
Stories: SPRINT1-048

  • 14.1: Manager creates assignment group
  • 14.2: Manager adds multiple managers to group
  • 14.3: Manager adds workers to group (mixed roles)
  • 14.4: Manager edits assignment group
  • 14.5: Manager assigns work order to group
  • 14.6: All managers in group receive notifications
  • 14.7: Worker from group claims work order
  • 14.8: Admin deletes assignment group

Testability: ✅ TESTABLE

Advanced Features Workflows (Priority 3: Enhanced Features)​

Workflow 15: Parts Catalog and Tracking​

Browsers: 3 (Admin or Inventory Management, Manager, Worker)
Stories: SPRINT0-019, SPRINT0-020

  • 15.1: Manager views parts catalog
  • 15.2: Admin or Inventory Management creates part in catalog
  • 15.3: Admin or Inventory Management edits part
  • 15.4: Worker views parts on work order
  • 15.5: Worker records parts used on work order
  • 15.6: Manager views parts usage report

Testability: 🔍 VERIFY (Partially implemented - test what exists)

Workflow 16: Service Request Status Lifecycle​

Browsers: 2 (Worker, Manager)
Stories: SPRINT1-023

  • 16.1: Worker creates service request (status: pending)
  • 16.2: Manager approves service request (status: approved)
  • 16.3: Manager converts to work order (status: processing)
  • 16.4: Worker starts work (status: in_progress)
  • 16.5: Worker completes work (status: fulfilled)
  • 16.6: Manager closes service request (status: closed)

Testability: 🔍 VERIFY (Database ready, UI may need updates)

Workflow 17: Room Status and Phase 5 Features​

Browsers: 2 (Manager, Worker)
Stories: SPRINT1-042, SPRINT1-025, SPRINT1-027, SPRINT1-031, SPRINT1-032, SPRINT1-033

  • 17.1: Manager views room status on location
  • 17.2: Manager sets room status flag
  • 17.3: Manager creates work order with emergency flag
  • 17.4: Worker views emergency work order
  • 17.5: Worker logs access to room
  • 17.6: Manager views access log
  • 17.7: Manager sets chargeback information
  • 17.8: Manager views asset intelligence data

Testability: 🔍 VERIFY (Display exists, workflows need verification)

Guest and Mobile Workflows (Priority 4: Guest Experience)​

Workflow 18: Guest Member Mobile Experience​

Browsers: 2 (Guest Member, Manager)
Stories: SPRINT2-003

  • 18.1: Guest member registers/logs in
  • 18.2: Guest member views mobile-optimized dashboard
  • 18.3: Guest member creates service request (mobile)
  • 18.4: Guest member views their service requests
  • 18.5: Manager processes guest member request
  • 18.6: Guest member receives notification
  • 18.7: Guest member views updated request status

Testability: ✅ TESTABLE

Notification and Settings Workflows (Priority 5: Configuration)​

Workflow 19: Notification System​

Browsers: 3 (Manager, Worker, Manager2)
Stories: SPRINT0-028, SPRINT0-029, SPRINT0-030, SPRINT1-038, SPRINT1-047

  • 19.1: Manager assigns work order (worker receives notification)
  • 19.2: Worker views notification in app
  • 19.3: Worker marks notification as read
  • 19.4: Manager configures notification preferences
  • 19.5: Manager sets Do Not Disturb window
  • 19.6: Manager configures global notification policies
  • 19.7: Worker receives notification (respects DND)
  • 19.8: Manager verifies notification delivery

Testability: ✅ TESTABLE

Workflow 20: Settings Management​

Browsers: 1 (Manager/Admin)
Stories: SPRINT1-022

  • 20.1: Manager accesses settings area
  • 20.2: Manager views user settings (profile)
  • 20.3: Manager views system settings (organization)
  • 20.4: Admin views application settings (platform)
  • 20.5: Manager updates system settings
  • 20.6: Manager verifies settings persist

Testability: ✅ TESTABLE

Onboarding Workflow (Priority 6: Setup)​

💡 Recommended First Step: The Onboarding Wizard is the fastest way to configure test data (locations, categories, SLA rules, users). Consider running this workflow early in your testing cycle to set up all necessary configuration data for other workflows.

Workflow 21: Onboarding Wizard​

Browsers: 1 (New Tenant Admin)
Stories: SPRINT1-046, SPRINT1-051, SPRINT1-052

  • 21.1: New tenant accesses onboarding
  • 21.2: Step 1: Site identification (slug availability check)
  • 21.3: Step 2: Location ingestion (CSV upload or manual)
  • 21.4: Step 3: Taxonomy selection (standard or custom categories)
  • 21.5: Step 4: SLA rules setup
  • 21.6: Step 5: User setup (create initial users)
  • 21.7: Step 6: Data import (optional)
  • 21.8: Step 7: Dashboard launch (subdomain URL display)
  • 21.9: Onboarding banner appears if incomplete

Testability: ✅ TESTABLE

Dashboard and KPI Workflows (Priority 7: Analytics)​

Workflow 22: Manager KPI Dashboard​

Browsers: 1 (Manager)
Stories: SPRINT1-040

  • 22.1: Manager views KPI dashboard
  • 22.2: Manager views triage speed metrics
  • 22.3: Manager views SLA compliance metrics
  • 22.4: Manager views rework hotspots
  • 22.5: Manager views workload balance
  • 22.6: Manager filters dashboard by date range

Testability: ✅ TESTABLE

Workflow 23: Worker KPI Dashboard​

Browsers: 1 (Worker)
Stories: SPRINT1-041

  • 23.1: Worker views KPI dashboard
  • 23.2: Worker views leaderboard
  • 23.3: Worker views on-time streaks
  • 23.4: Worker views quality metrics
  • 23.5: Worker views personal performance trends

Testability: ✅ TESTABLE

RBAC and Security Workflows (Priority 8: Security)​

Workflow 24: Role-Based Access Control​

Browsers: 4 (Worker, Manager, Operations Director, Admin)
Stories: SPRINT0-002, SPRINT0-003

  • 24.1: Worker attempts to convert service request (should fail)
  • 24.2: Worker attempts to assign work order (should fail)
  • 24.3: Manager can convert service request (should succeed)
  • 24.4: Manager can assign work order (should succeed)
  • 24.5: Operations Director can triage (should succeed)
  • 24.6: Admin can access all features (should succeed)
  • 24.7: Multi-tenant isolation (Tenant A cannot see Tenant B data)

Testability: ✅ TESTABLE

Mobile Responsiveness (Priority 9: UX)​

Workflow 25: Mobile-Responsive Testing​

Browsers: 1 (Mobile Device)
Stories: SPRINT0-007B

  • 25.1: Worker accesses system on mobile
  • 25.2: Mobile menu functions correctly
  • 25.3: Forms are usable on mobile (touch targets)
  • 25.4: Work order detail view is mobile-optimized
  • 25.5: Service request creation works on mobile
  • 25.6: Photo upload works on mobile
  • 25.7: Navigation works in portrait and landscape

Testability: ✅ TESTABLE

Summary​

Total Workflows: 25
Total Test Cases: ~150-200 test cases
Stories Covered: All ✅ implemented + 🚧 partially implemented (non-backlog, non-obsolete)

Execution Order:

  1. Core Workflows (1-8) - Critical paths first
  2. Master Data (9-14) - Configuration needed for other tests
  3. Advanced Features (15-17) - Verify partial implementations
  4. Guest/Mobile (18, 25) - User experience
  5. Notifications/Settings (19-20) - Configuration
  6. Onboarding (21) - Setup
  7. Dashboards (22-23) - Analytics
  8. RBAC (24) - Security validation

Next Steps:

  1. Review and agree on workflow list
  2. Add testability checks to each workflow
  3. Create detailed test case documentation
  4. Create Testability Matrix template
  5. Create phased execution plan