Verification Matrix — PWA and Updates

Implements:

• REQ-CONN-003 PWA Installation and Update Management

Requirement → Scenario Index

Requirement Ref	Requirement (short)	Scenario IDs
REQ-CONN-003: PWA Updates
BR-1	Update check on launch	TC-CONN-UPDATE-001
EDR-1	Update notification displayed	TC-CONN-UPDATE-002, TC-CONN-UPDATE-003
EDR-2	Standard update with options	TC-CONN-UPDATE-004
EDR-3	Critical update (no dismiss)	TC-CONN-UPDATE-005
EDR-4	Unsynchronised data warning	TC-CONN-UPDATE-006
EDR-5	Remind me later behaviour	TC-CONN-UPDATE-007
EDR-6	Offline update queueing	TC-CONN-UPDATE-008
EDR-8	PWA installation prompt	TC-CONN-UPDATE-010
SDR-1	Suppress during operations	TC-CONN-UPDATE-011
UBI-1	Background download	TC-CONN-UPDATE-012
UBI-2	Session preservation	TC-CONN-UPDATE-013
ADR-007	Offline detection	TC-CONN-HEART-002, TC-CONN-HEART-003

Scenarios (at a glance)

ID	Title	Type
3. PWA Updates (REQ-CONN-003)
TC-CONN-UPDATE-001	Update check on app launch	Positive
TC-CONN-UPDATE-002	Update notification not during operation	Positive
TC-CONN-UPDATE-003	Update notification after operation complete	Positive
TC-CONN-UPDATE-006	Unsynchronised data warning before update	Positive
TC-CONN-UPDATE-008	Offline update queued and displayed online	Positive
TC-CONN-UPDATE-010	PWA installation prompt displayed	Positive
TC-CONN-UPDATE-012	Background download automatic	Positive
TC-CONN-UPDATE-013	Session preserved across update	Positive
TC-CONN-UPDATE-014	Multiple versions cumulative update	Positive

Scenario details

3. PWA Updates (REQ-CONN-003)

TC-CONN-UPDATE-001: Update check on app launch

• Arrange
  • User has PWA installed
  • New version available on server
  • User is not currently using the app
• Act
  • User launches the app (from home screen or browser)
• Assert
  • System checks for updates on launch
  • If update available and user idle, notification displayed
  • If update available and user starts action, notification queued
  • Update check logged for analytics

TC-CONN-UPDATE-002: Update notification not during operation

• Arrange
  • User is using the app
  • New update becomes available
  • User is in middle of locking on workers
• Act
  • Server pushes update notification
• Assert
  • Update notification NOT displayed during lock-on flow
  • Notification queued for later
  • User workflow not interrupted
  • No modal or banner appears during operation

TC-CONN-UPDATE-003: Update notification after operation complete

• Arrange
  • User was locking on worker (update notification queued)
  • Update notification was suppressed during operation
• Act
  • User completes worker lock-on (returns to worksite view)
• Assert
  • Update notification now displayed
  • Notification shows "A new app version is available"
  • Clear message to refresh or relaunch app
  • User can make informed decision

TC-CONN-UPDATE-006: Unsynchronised data warning before update

• Arrange
  • Update available
  • User has unsynchronised data (offline actions queued)
  • User clicks "Update Now"
• Act
  • System checks for unsynchronised data
• Assert
  • Warning displayed before update proceeds
  • Warning states: "You have unsynchronised changes. Updating now may result in data loss."
  • User given options: "Wait for sync" or "Proceed anyway"
  • Clear indication of risk
  • User can cancel update to preserve data

TC-CONN-UPDATE-008: Offline update queued and displayed online

• Arrange
  • Device is offline
  • Server pushes update notification (or update becomes available)
• Act
  • Device regains connectivity
• Assert
  • Queued update notification now displayed
  • Notification not lost during offline period
  • User receives update prompt when back online
  • Update can now be installed with connectivity

TC-CONN-UPDATE-010: PWA installation prompt displayed

• Arrange
  • User accessing app via browser (not installed to home screen)
  • User meets trigger criteria (e.g., 3rd visit, engaged usage pattern)
• Act
  • Trigger conditions met
• Assert
  • PWA installation prompt displayed
  • Prompt encourages adding to home screen
  • Clear benefits explained (faster access, offline capability)
  • User can accept or dismiss
  • Prompt respectful, not aggressive
  • Browser's native install prompt may also appear

TC-CONN-UPDATE-012: Background download automatic

• Arrange
  • New update becomes available
  • User's device is online
• Act
  • Time passes (user may or may not be actively using app)
• Assert
  • Update downloads automatically in background
  • No user intervention required for download
  • Download happens without disrupting use
  • User only prompted when ready to install
  • Service worker handles download silently

TC-CONN-UPDATE-013: Session preserved across update

• Arrange
  • User is authenticated and using app
  • Update available and user clicks "Update Now"
  • No unsynchronised data
• Act
  • App refreshes/relaunches to install update
• Assert
  • User remains authenticated after update
  • Session preserved where technically feasible
  • User doesn't need to log in again
  • Workflow can continue after update
  • If session cannot be preserved, clear message shown

TC-CONN-UPDATE-014: Multiple versions cumulative update

• Arrange
  • User running version 1.0.0
  • Server has versions 1.1.0, 1.2.0, and 1.3.0 available
• Act
  • User clicks "Update Now"
• Assert
  • System updates directly to latest version (1.3.0)
  • No need to install each intermediate version
  • Single update action brings user current
  • Update process efficient and fast

---