Skip to main content

System Admin Dashboard Test Cases - ONB05US01


Test Scenario Summary

This document contains comprehensive enhanced test cases for the System Admin Dashboard feature covering organization setup with weighted progress calculations, utility setup with 3-parameter formula, user adoption monitoring, security activity tracking, data upload functionality, subscription management, and user behavior tracking events.




Test Case 1: Organization Setup Weighted Progress Display

Test Case Metadata

  • Test Case ID: ONB05US01_TC_001
  • Title: Verify Organization Setup displays 75% progress using weighted calculation (Currency 40% + Date Format 30% + Timezone 30%)
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Organization Setup Progress
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Onboarding, Progress-Calculation, MOD-Dashboard, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Module-Coverage, Report-Revenue-Impact-Tracking, Report-Customer-Segment-Analysis, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Organization-Setup-Service, Weighted-Calculation, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: High
  • Expected_Execution_Time: 4 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Organization Setup Service, Dashboard API, Calculation Engine
  • Code_Module_Mapped: Dashboard-Web, Organization-Setup-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Module-Coverage, Revenue-Impact-Tracking, Customer-Segment-Analysis, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Organization Setup Service, Database, Calculation Engine
  • Performance_Baseline: < 2 seconds for progress calculation
  • Data_Requirements: Metro Water Utilities organization with Currency: Complete, Date Format: Complete, Timezone: Pending

Prerequisites

  • Setup_Requirements: Metro Water Utilities organization configured with partial setup
  • User_Roles_Permissions: System Admin role with full dashboard access
  • Test_Data: Organization "Metro Water Utilities", Currency task completed (40% weight), Date Format completed (30% weight), Timezone pending (0% weight)
  • Prior_Test_Cases: User authentication successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Login as System Admin

Dashboard loads successfully with organization data

admin@metrowater.com / SecurePass123!

Valid Metro Water Utilities admin

2

Navigate to System Admin Dashboard

Dashboard displays with Organization Setup section visible

N/A

Main dashboard interface

3

Locate Organization Setup section

Section shows "Organization Setup" header with progress bar

N/A

UI section identification

4

Verify progress percentage calculation

Shows exactly 70% completion based on weighted formula

Currency: ✓ (40%), Date Format: ✓ (30%), Timezone: ○ (0%) = 70% total

Weighted calculation: (40% × 1) + (30% × 1) + (30% × 0) = 70%

5

Verify visual progress bar

Blue progress bar fills to 70% of total width

N/A

Visual progress indicator

6

Check individual task status indicators

Currency and Date Format show green checkmarks, Timezone shows pending circle

Currency: ✓, Date Format: ✓, Timezone: ○

Individual task status validation

7

Verify "Setup progress" label

Label displays "Setup progress" above the 70% indicator

N/A

UI label verification per wireframe

8

Validate Complete Setup button state

Button is disabled due to incomplete setup

"Complete Setup" button grayed out

Button state based on completion status

Verification Points

  • Primary_Verification: Organization Setup section displays exactly 70% progress using weighted calculation formula
  • Secondary_Verifications: Individual task statuses are correct, progress bar visual matches percentage, Complete Setup button state aligns with completion
  • Negative_Verification: Progress should not show 100% or any incorrect calculation, button should not be enabled

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Low
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: User authentication, Organization setup data creation
  • Blocked_Tests: Complete Setup button functionality tests
  • Parallel_Tests: Other dashboard section tests
  • Sequential_Tests: Must run after data setup, before button tests

Additional Information

  • Notes: Critical test validating core business rule for weighted progress calculation
  • Edge_Cases: Test with different completion combinations to verify formula accuracy
  • Risk_Areas: Incorrect progress calculation could mislead users about setup completion
  • Security_Considerations: Verify progress data is not manipulable by unauthorized users

Missing Scenarios Identified

  • Scenario_1: Test all possible task completion combinations (8 scenarios) to validate weighted formula
  • Type: Edge Case
  • Rationale: Business rule specifies exact weightage, need comprehensive validation
  • Priority: P1




Test Case 2: Visual Task Status Indicators Consistency

Test Case Metadata

  • Test Case ID: ONB05US01_TC_002
  • Title: Verify visual distinction between completed (✓), in-progress (⧗), and pending (○) tasks using exact wireframe indicators
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Task Status Visualization
  • Test Type: UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, UI-Validation, Visual-Indicators, MOD-Dashboard, P2-High, Phase-Regression, Type-UI, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Cross-Browser-Results, Report-Module-Coverage, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Organization-Setup-Service, Status-Icons, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Low
  • Expected_Execution_Time: 3 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: None
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Organization Setup Service, UI Component Library
  • Code_Module_Mapped: Dashboard-Web, UI-Components
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Quality-Dashboard, User-Acceptance, Cross-Browser-Results, Module-Coverage, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 116+, Safari 16+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Organization Setup Service, UI Component Library
  • Performance_Baseline: < 1 second for UI rendering
  • Data_Requirements: Metro Water Utilities with mixed task completion states

Prerequisites

  • Setup_Requirements: Metro Water Utilities organization with specific task states
  • User_Roles_Permissions: System Admin role
  • Test_Data: Currency: Complete (✓), Date Format: Pending (○), Timezone: In-Progress (⧗)
  • Prior_Test_Cases: ONB05US01_TC_001 passed

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access System Admin Dashboard for Metro Water Utilities

Dashboard loads with Organization Setup section

admin@metrowater.com

Post-authentication state

2

Examine Currency task status indicator

Green checkmark (✓) icon displayed next to "Currency"

Currency task: Complete status

Completed state validation

3

Examine Date Format task status indicator

Yellow/orange circle (○) icon displayed next to "Date Format"

Date Format task: Pending status

Pending state validation

4

Examine Timezone task status indicator

Blue progress/clock (⧗) icon displayed next to "Timezone"

Timezone task: In-progress status

In-progress state validation

5

Verify icon color consistency

Each status uses distinct, consistent color coding across the interface

Green: ✓, Yellow: ○, Blue: ⧗

Color coding validation

6

Check icon size and positioning

All icons are same size and properly aligned with task names

Icon dimensions: 16x16px, left-aligned

Visual consistency check

7

Validate icon clarity and accessibility

Icons are clearly visible and distinguishable at normal viewing distance

N/A

Accessibility verification

8

Test cross-browser icon rendering

Icons display consistently across Chrome, Firefox, and Safari

Cross-browser testing

Multi-browser compatibility

Verification Points

  • Primary_Verification: Tasks display appropriate visual indicators (✓, ○, ⧗) based on exact completion status
  • Secondary_Verifications: Icons are clearly distinguishable, color coding is consistent, proper alignment maintained
  • Negative_Verification: No task should display incorrect status icon or inconsistent visual treatment

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Low
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Organization setup data creation, Dashboard load
  • Blocked_Tests: Status change workflow tests
  • Parallel_Tests: Other visual validation tests
  • Sequential_Tests: Follows basic dashboard load tests

Additional Information

  • Notes: Critical for user experience and onboarding clarity
  • Edge_Cases: Test with all possible status combinations, different screen resolutions
  • Risk_Areas: Inconsistent visual feedback could confuse users during setup process
  • Security_Considerations: Status indicators should reflect actual data, not be manipulable

Missing Scenarios Identified

  • Scenario_1: Test status icon changes during real-time updates when tasks are completed
  • Type: Integration
  • Rationale: Users need immediate visual feedback when completing tasks
  • Priority: P2
  • Scenario_2: Validate icon accessibility compliance (color contrast, screen reader support)
  • Type: Accessibility
  • Rationale: B2B SaaS must meet accessibility standards
  • Priority: P3




Test Case 3: Complete Setup Button State Management

Test Case Metadata

  • Test Case ID: ONB05US01_TC_003
  • Title: Verify "Complete Setup" button is enabled only when Metro Water Utilities achieves 100% Organization Setup completion
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Complete Setup Button Logic
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Button-Logic, State-Management, MOD-Dashboard, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Smoke-Test-Results, Report-Revenue-Impact-Tracking, Report-Integration-Testing, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Organization-Setup-Service, Button-States, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Medium
  • Expected_Execution_Time: 5 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Organization Setup Service, Navigation Service, Button State Engine
  • Code_Module_Mapped: Dashboard-Web, Organization-Setup-Module, Navigation-Controller
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Smoke-Test-Results, Revenue-Impact-Tracking, Integration-Testing, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Organization Setup Service, Navigation Service, Org Setup Link handler
  • Performance_Baseline: < 1 second for button state updates
  • Data_Requirements: Metro Water Utilities with configurable completion states

Prerequisites

  • Setup_Requirements: Metro Water Utilities organization with controllable task completion states
  • User_Roles_Permissions: System Admin role with organization setup permissions
  • Test_Data: Metro Water Utilities organization, admin user john.admin@metrowater.com
  • Prior_Test_Cases: Organization setup data initialization successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Login as Metro Water Utilities admin

Authentication successful, dashboard access granted

john.admin@metrowater.com / SecurePass123!

Valid admin credentials

2

Navigate to System Admin Dashboard

Dashboard loads showing Organization Setup at 70% completion

N/A

Initial incomplete state

3

Verify "Complete Setup" button state

Button is disabled (grayed out) and non-clickable

Button state: disabled, visual: grayed

Incomplete setup state

4

Check button tooltip/message

Hover shows "Complete all required tasks to enable" or similar message

Tooltip text displayed

User guidance for disabled state

5

Complete Timezone configuration task

Navigate to timezone setup and select "America/New_York"

Timezone: America/New_York (Eastern Time)

Final required task completion

6

Return to System Admin Dashboard

Progress updates to 100%, all tasks show completed (✓)

Currency: ✓, Date Format: ✓, Timezone: ✓ = 100%

Complete setup achievement

7

Verify "Complete Setup" button enabled

Button changes to enabled state (blue color, clickable)

Button state: enabled, visual: blue primary

Full completion enables button

8

Click "Complete Setup" button

Redirects to organization setup page (Org setup link)

Navigation to: /organization/setup/complete

Navigation verification per user story

9

Verify completion confirmation

Organization setup page shows completion confirmation

Success message: "Organization setup completed successfully"

Final confirmation validation

Verification Points

  • Primary_Verification: "Complete Setup" button is only enabled when Metro Water Utilities achieves 100% Organization Setup completion (all weighted tasks complete)
  • Secondary_Verifications: Button state changes dynamically with progress updates, proper navigation to Org setup link occurs, user feedback is clear
  • Negative_Verification: Button should not be clickable when setup is incomplete, should not bypass validation rules

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Low
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Organization setup initialization, Progress calculation tests
  • Blocked_Tests: Organization setup completion workflow tests
  • Parallel_Tests: Other button state tests
  • Sequential_Tests: Must follow progress calculation validation

Additional Information

  • Notes: Critical business logic ensuring users complete required setup before proceeding
  • Edge_Cases: Test button behavior during concurrent user sessions, network interruptions during completion
  • Risk_Areas: Incorrect button state could allow incomplete setups or block valid completions
  • Security_Considerations: Verify completion validation cannot be bypassed client-side

Missing Scenarios Identified

  • Scenario_1: Test button state during real-time progress updates from other admin sessions
  • Type: Concurrency
  • Rationale: Multiple admins may work on setup simultaneously
  • Priority: P2
  • Scenario_2: Validate button behavior during network disconnection/reconnection
  • Type: Error Handling
  • Rationale: Ensure button state remains accurate despite connectivity issues
  • Priority: P2




Test Case 4: Continue Setup Button Navigation for Electric Services Co

Test Case Metadata

  • Test Case ID: ONB05US01_TC_004
  • Title: Verify "Continue Setup" button directs Electric Services Co to next incomplete utility setup task (System Settings & Service Coverage at 34.1%)
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Continue Setup Navigation
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Navigation, Utility-Setup, MOD-Dashboard, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Smoke-Test-Results, Report-Integration-Testing, Report-Revenue-Impact-Tracking, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Utility-Setup-Service, Smart-Navigation, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Medium
  • Expected_Execution_Time: 4 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Utility Setup Service, Navigation Service, Utility setup link handler
  • Code_Module_Mapped: Dashboard-Web, Utility-Setup-Module, Navigation-Controller
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Smoke-Test-Results, Integration-Testing, Revenue-Impact-Tracking, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Utility Setup Service, Navigation Service, Three-step utility enhancement system
  • Performance_Baseline: < 1 second for navigation response
  • Data_Requirements: Electric Services Co utility with 12.38% completion (System Settings: 34.1%, Billing: 0%, Access Control: 0%)

Prerequisites

  • Setup_Requirements: Electric Services Co utility configured with partial setup completion
  • User_Roles_Permissions: System Admin role with utility setup permissions
  • Test_Data: Electric Services Co utility, System Settings & Service Coverage: 34.1%, Billing & Scheduling Management: 0%, Access Control & References: 0%
  • Prior_Test_Cases: Utility setup data initialization successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access System Admin Dashboard

Dashboard loads successfully

admin@electricservices.com / SecurePass123!

Valid Electric Services Co admin

2

Locate Utility Setup section

Section displays "Utility Setup" header with 12.38% progress

Setup progress: 12.38%

Based on wireframe data

3

Verify three-step utility structure

Shows three categories: System Settings & Service Coverage (34.1%), Billing & Scheduling Management (0%), Access Control & References (0%)

Step 1: 34.1% partial, Step 2: 0%, Step 3: 0%

Three-step enhancement validation

4

Check "Continue Setup" button state

Button is enabled and displays "Continue Setup" text

Button state: enabled, text: "Continue Setup"

Button availability check

5

Click "Continue Setup" button

Navigation initiates to utility setup page

N/A

Navigation action execution

6

Verify intelligent routing

Directs to System Settings & Service Coverage section (highest priority incomplete at 34.1%)

Target: /utility-setup/system-settings-service-coverage

Smart navigation to highest priority incomplete

7

Confirm correct utility context

Utility setup page loads with Electric Services Co context

Utility: Electric Services Co, Section: System Settings & Service Coverage

Context preservation validation

8

Validate section-specific content

Page shows Core System Settings and Service Areas subsections

Subsections: Core System Settings, Service Areas

Section content verification

Verification Points

  • Primary_Verification: "Continue Setup" button directs Electric Services Co to System Settings & Service Coverage section (highest priority incomplete task at 34.1%)
  • Secondary_Verifications: Button is always enabled for incomplete setups, proper page navigation with utility context, intelligent routing to appropriate section
  • Negative_Verification: Should not redirect to completed sections or incorrect utility context

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Low
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Utility setup data initialization, Dashboard load
  • Blocked_Tests: Utility setup workflow tests
  • Parallel_Tests: Organization setup button tests
  • Sequential_Tests: Must follow utility progress calculation tests

Additional Information

  • Notes: Critical for efficient utility setup workflow and user guidance
  • Edge_Cases: Test navigation with different completion combinations, multiple utilities scenario
  • Risk_Areas: Incorrect navigation could waste user time or cause setup abandonment
  • Security_Considerations: Verify navigation respects utility access permissions

Missing Scenarios Identified

  • Scenario_1: Test Continue Setup behavior when multiple utilities have different completion states
  • Type: Multi-Entity
  • Rationale: Organizations may have multiple utilities requiring prioritization
  • Priority: P1
  • Scenario_2: Validate navigation when all three steps have equal completion percentages
  • Type: Edge Case
  • Rationale: Need deterministic routing logic for tie-breaking scenarios
  • Priority: P2




Test Case 5: Daily Active Users Display - Metro Water Utilities

Test Case Metadata

  • Test Case ID: ONB05US01_TC_005
  • Title: Verify current day's active user count displays "2" prominently for Metro Water Utilities with +100% week growth
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - User Adoption Metrics
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Analytics, User-Metrics, MOD-Dashboard, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-Customer-Segment-Analysis, Report-User-Acceptance, Report-Performance-Metrics, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-User-Activity-Service, Adoption-Tracking, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Medium
  • Expected_Execution_Time: 3 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: User Activity Service, Analytics Engine, Real-time Data Pipeline
  • Code_Module_Mapped: Dashboard-Web, User-Analytics-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Quality-Dashboard, Customer-Segment-Analysis, User-Acceptance, Performance-Metrics, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: User Activity Service, Analytics Engine, Real-time metrics pipeline
  • Performance_Baseline: < 3 seconds for metrics loading
  • Data_Requirements: Metro Water Utilities with 2 active users today, week-over-week growth data showing +100%

Prerequisites

  • Setup_Requirements: Metro Water Utilities with active user tracking enabled
  • User_Roles_Permissions: System Admin role with analytics access
  • Test_Data: Today's Users: 2, Week Growth: +100%, Daily active user definition: users who logged in today
  • Prior_Test_Cases: User activity data populated successfully

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Login as Metro Water Utilities System Admin

Dashboard access granted

admin@metrowater.com / SecurePass123!

Valid admin credentials

2

Navigate to User Adoption section on dashboard

Section displays with "User Adoption" header

N/A

User Adoption section identification

3

Verify "Daily active users" label

Label clearly displays "Daily active users"

N/A

Section label validation per wireframe

4

Check "Today's Users" count display

Shows prominent count of "2" users

Today's Users: 2

Current day active user count from wireframe

5

Verify count prominence and visibility

Number "2" is displayed in large, bold font

Font size: 24px+, weight: bold

Visual prominence verification

6

Check "Week Growth" indicator

Shows "+100%" with positive growth formatting

Week Growth: +100%

Growth metric from wireframe data

7

Verify growth indicator styling

Growth percentage displays in green color with upward trend

Color: green (#10B981), trend: positive

Positive growth visual treatment

8

Validate user activity chart

Line chart shows daily activity pattern from Thursday to Friday

Chart data: Thu-Fri activity trend

Visual chart representation

9

Check data freshness timestamp

Current date/time or "last updated" indicator present

Update timestamp within last 5 minutes

Real-time data validation

Verification Points

  • Primary_Verification: Current day's active user count "2" is displayed prominently in User Adoption section for Metro Water Utilities
  • Secondary_Verifications: Week growth "+100%" is shown with positive styling, data appears current with proper timestamp
  • Negative_Verification: Should not display stale data, negative growth should use different styling, count should not be zero when users are active

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Medium
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: User activity data generation, Dashboard authentication
  • Blocked_Tests: User behavior tracking event tests
  • Parallel_Tests: Other analytics section tests
  • Sequential_Tests: Should follow user login activity generation

Additional Information

  • Notes: Critical metric for onboarding success measurement and user engagement tracking
  • Edge_Cases: Test with zero users, very high user counts, different growth scenarios (negative, flat)
  • Risk_Areas: Inaccurate user counts could mislead business decisions about adoption success
  • Security_Considerations: User activity data should be properly aggregated without exposing individual user details

Missing Scenarios Identified

  • Scenario_1: Test daily active user count accuracy by correlating with actual login events
  • Type: Data Accuracy
  • Rationale: Business decisions depend on accurate user adoption metrics
  • Priority: P1
  • Scenario_2: Validate user activity chart interactivity and drill-down capabilities
  • Type: User Experience
  • Rationale: Admins need detailed insights beyond summary metrics
  • Priority: P3




Test Case 6: Security Activity Daily Breakdown for Electric Services Co

Test Case Metadata

  • Test Case ID: ONB05US01_TC_006
  • Title: Verify Security Activity displays daily breakdown showing 19 authorized logins (green) and 13 unauthorized attempts (red) for Electric Services Co
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Security Activity Monitoring
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Planned-for-Automation

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Security, Analytics, MOD-Dashboard, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Report-Security-Validation, Report-Quality-Dashboard, Report-Revenue-Impact-Tracking, Report-Customer-Segment-Analysis, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Security-Logging-Service, Login-Monitoring, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: Yes
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Medium
  • Expected_Execution_Time: 4 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Security Logging Service, Authentication System, Analytics Engine
  • Code_Module_Mapped: Dashboard-Web, Security-Analytics-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Security-Validation, Quality-Dashboard, Revenue-Impact-Tracking, Customer-Segment-Analysis, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Security Logging Service, Authentication System, Login attempt tracking
  • Performance_Baseline: < 2 seconds for security data loading
  • Data_Requirements: Electric Services Co with login history: 19 authorized logins, 13 unauthorized attempts across Thursday-Friday period

Prerequisites

  • Setup_Requirements: Electric Services Co with security logging enabled and historical login data
  • User_Roles_Permissions: System Admin role with security monitoring access
  • Test_Data: Authorized logins: 19 total, Unauthorized attempts: 13 total, Daily breakdown across Thu-Fri timeframe
  • Prior_Test_Cases: Security logging system operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Login as Electric Services Co System Admin

Authentication successful, dashboard access granted

admin@electricservices.com / SecurePass123!

Valid admin credentials

2

Navigate to Security Activity section

Section visible with "Security Activity" header and "Login attempts" subtitle

N/A

Security section identification per wireframe

3

Examine daily breakdown bar chart

Bar chart displays login attempts broken down by day (Thu, Wed, Tue, Mon, Sun, Sat, Fri)

Daily view from Thursday to Friday

Chart structure validation

4

Verify authorized login visualization

Green bars represent authorized logins with appropriate heights

Green bars showing authorized login counts

Authorized login representation

5

Verify unauthorized attempt visualization

Red bars represent unauthorized attempts with appropriate heights

Red bars showing unauthorized attempt counts

Unauthorized attempt representation

6

Check color coding consistency

Green consistently used for authorized (✓), red consistently used for unauthorized (✗)

Green: #10B981, Red: #EF4444

Color standard validation

7

Validate daily granularity

Each day shows separate bars with distinct counts

Thu: X authorized/Y unauthorized, Fri: A authorized/B unauthorized

Daily breakdown granularity

8

Verify total authorized count

Shows "19 logins" with green indicator at bottom of chart

Authorized: 19 logins (green indicator)

Authorized total from wireframe

9

Verify total unauthorized count

Shows "13 attempts" with red indicator at bottom of chart

Unauthorized: 13 attempts (red indicator)

Unauthorized total from wireframe

10

Check chart interactivity

Hovering over bars shows detailed daily counts

Hover tooltips with specific numbers

Interactive chart validation

Verification Points

  • Primary_Verification: Security Activity displays daily breakdown with 19 authorized logins (green bars) and 13 unauthorized attempts (red bars) for Electric Services Co
  • Secondary_Verifications: Chart uses consistent color coding, daily granularity is maintained, totals match detailed breakdown
  • Negative_Verification: Should not aggregate data inappropriately, mix up authorized/unauthorized categorization, or show incorrect totals

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Medium
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Security logging setup, Authentication system operational
  • Blocked_Tests: Security incident response tests
  • Parallel_Tests: Other security monitoring tests
  • Sequential_Tests: Must follow security data collection

Additional Information

  • Notes: Critical for security compliance and threat detection in B2B utility environment
  • Edge_Cases: Test with very high unauthorized attempt counts, zero activity days, sustained attack patterns
  • Risk_Areas: Incorrect security data could lead to missed threats or false alarms
  • Security_Considerations: Security data integrity is paramount, ensure proper access controls and audit trails

Missing Scenarios Identified

  • Scenario_1: Test security activity drill-down to view specific unauthorized attempt details (IP addresses, usernames, timestamps)
  • Type: Security Investigation
  • Rationale: Admins need detailed investigation capabilities for security incidents
  • Priority: P1
  • Scenario_2: Validate security alert thresholds and notification triggers
  • Type: Security Automation
  • Rationale: Proactive security monitoring requires automated alerting
  • Priority: P1




Test Case 7: Security Login Count Totals Validation

Test Case Metadata

  • Test Case ID: ONB05US01_TC_007
  • Title: Verify total count displays exactly "19 logins" (authorized) and "13 attempts" (unauthorized) with proper color coding for Electric Services Co
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Security Totals Display
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Security, Metrics-Validation, MOD-Dashboard, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Report-Security-Validation, Report-Quality-Dashboard, Report-Smoke-Test-Results, Report-Module-Coverage, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Security-Logging-Service, Total-Calculations, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: Yes
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Low
  • Expected_Execution_Time: 2 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Security Logging Service, Data Aggregation Engine
  • Code_Module_Mapped: Dashboard-Web, Security-Analytics-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Security-Validation, Quality-Dashboard, Smoke-Test-Results, Module-Coverage, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Security Logging Service, Data Aggregation Engine, Chart rendering system
  • Performance_Baseline: < 1 second for total calculations
  • Data_Requirements: Electric Services Co security log data aggregating to exactly 19 authorized and 13 unauthorized

Prerequisites

  • Setup_Requirements: Electric Services Co with complete security activity history
  • User_Roles_Permissions: System Admin role with security data access
  • Test_Data: Authorized total: 19 logins, Unauthorized total: 13 attempts, matching daily breakdown chart data
  • Prior_Test_Cases: ONB05US01_TC_006 (Security Activity Daily Breakdown) passed

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access Security Activity section for Electric Services Co

Section loads with chart and total indicators

admin@electricservices.com

Post-authentication state

2

Locate authorized login total indicator

Green indicator at bottom of Security Activity section

N/A

Total indicator positioning

3

Verify authorized login count

Displays exactly "19 logins" with green color coding

Authorized: 19 logins (green: #10B981)

Exact count from wireframe data

4

Locate unauthorized attempts total indicator

Red indicator at bottom of Security Activity section

N/A

Total indicator positioning

5

Verify unauthorized attempts count

Displays exactly "13 attempts" with red color coding

Unauthorized: 13 attempts (red: #EF4444)

Exact count from wireframe data

6

Cross-validate with chart data

Sum of all daily authorized bars equals 19 total

Daily bars: Sum = 19 logins

Data consistency check

7

Cross-validate unauthorized chart data

Sum of all daily unauthorized bars equals 13 total

Daily bars: Sum = 13 attempts

Data consistency check

8

Verify total label clarity

Labels clearly distinguish "logins" vs "attempts" terminology

"19 logins" vs "13 attempts"

Terminology precision

9

Check visual hierarchy

Totals are prominently displayed and easily readable

Font size: 16px+, bold weight

Visual prominence validation

Verification Points

  • Primary_Verification: Total authorized logins shows exactly "19 logins" and unauthorized attempts shows exactly "13 attempts" with proper green/red color coding
  • Secondary_Verifications: Totals match detailed chart data aggregation, labels use correct terminology, visual presentation is clear
  • Negative_Verification: Totals should not include incorrect data, miscalculations, or wrong color associations

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Low
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Security data aggregation, Chart rendering
  • Blocked_Tests: Security threshold alerting tests
  • Parallel_Tests: Other security metric tests
  • Sequential_Tests: Must follow daily breakdown validation

Additional Information

  • Notes: Critical for accurate security reporting and compliance documentation
  • Edge_Cases: Test with very large numbers, zero values, real-time updates during active login attempts
  • Risk_Areas: Incorrect totals could lead to security misassessment and compliance issues
  • Security_Considerations: Total accuracy is essential for security audits and incident response planning

Missing Scenarios Identified

  • Scenario_1: Test total recalculation accuracy during real-time login activity
  • Type: Real-Time Processing
  • Rationale: Totals must remain accurate as new login attempts occur
  • Priority: P1
  • Scenario_2: Validate total calculation performance with large datasets (1000+ login attempts)
  • Type: Performance
  • Rationale: Enterprise environments may have high login volumes
  • Priority: P2




Test Case 8: Smart Workforce Subscription Information Display

Test Case Metadata

  • Test Case ID: ONB05US01_TC_008
  • Title: Verify Smart Workforce subscription displays "Free" plan with up to 5 users included and component features (CX, MX, BX, WX) for Metro Water Utilities
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Smart Workforce Subscription Management
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Subscription, Billing, MOD-Dashboard, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Customer-Segment-Analysis, Report-Revenue-Impact-Tracking, Report-Quality-Dashboard, Report-User-Acceptance, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Subscription-Management-Service, Trial-Plan, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Low
  • Expected_Execution_Time: 3 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Subscription Management Service, Billing System, Feature Access Control
  • Code_Module_Mapped: Dashboard-Web, Subscription-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Customer-Segment-Analysis, Revenue-Impact-Tracking, Quality-Dashboard, User-Acceptance, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Subscription Management Service, Feature Registry, Trial Plan Configuration
  • Performance_Baseline: < 2 seconds for subscription data loading
  • Data_Requirements: Metro Water Utilities on Free trial plan with 5-user limit and all trial features enabled

Prerequisites

  • Setup_Requirements: Metro Water Utilities configured with Free trial subscription
  • User_Roles_Permissions: System Admin role with subscription viewing access
  • Test_Data: Plan: "Free", User limit: "Up to 5 users included", Features: Customer experience (CX), Meter Data Management (MX), Billing & Collection (BX), Workforce Automation (WX)
  • Prior_Test_Cases: Subscription service initialization successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access System Admin Dashboard for Metro Water Utilities

Dashboard loads successfully

admin@metrowater.com / SecurePass123!

Valid admin credentials

2

Locate Smart Workforce section

Section displays with "Smart Workforce" header and crown icon

N/A

Smart Workforce section identification per wireframe

3

Verify subscription plan header

Shows "Your current subscription plan" subtitle

N/A

Section subtitle validation

4

Check plan type display

Displays "Free" in large, bold text

Plan type: Free

Plan identification from wireframe

5

Verify user limit information

Shows "Up to 5 users included" below plan name

User limit: Up to 5 users included

Capacity limit from trial plan specs

6

Validate Customer experience (CX) feature

Green checkmark next to "Customer experience (CX)"

✓ Customer experience (CX)

Feature inclusion validation

7

Validate Meter Data Management (MX) feature

Green checkmark next to "Meter Data Management (MX)"

✓ Meter Data Management (MX)

Feature inclusion validation

8

Validate Billing & Collection (BX) feature

Green checkmark next to "Billing & Collection (BX)"

✓ Billing & Collection (BX)

Feature inclusion validation

9

Validate Workforce Automation (WX) feature

Green checkmark next to "Workforce Automation (WX)"

✓ Workforce Automation (WX)

Feature inclusion validation

10

Check upgrade pathway

"Update Subscription" button present at bottom

Button text: "Update Subscription"

Upgrade option availability

11

Verify feature description

Shows "All the essentials your org needs."

Description: "All the essentials your org needs."

Plan description from wireframe

Verification Points

  • Primary_Verification: Smart Workforce subscription clearly displays "Free" plan with "Up to 5 users included" and all four component features (CX, MX, BX, WX) with green checkmarks
  • Secondary_Verifications: Feature inclusions are clearly listed with checkmarks, upgrade option is available, plan description is accurate
  • Negative_Verification: Should not show incorrect plan details, missing features, or premium-only indicators for trial features

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Low
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Subscription service setup, Feature registry initialization
  • Blocked_Tests: Subscription upgrade workflow tests
  • Parallel_Tests: Other subscription display tests
  • Sequential_Tests: Should follow subscription service validation

Additional Information

  • Notes: Critical for trial user understanding of included features and upgrade pathways
  • Edge_Cases: Test with different subscription tiers, expired trials, feature access validation
  • Risk_Areas: Incorrect feature display could lead to user confusion about capabilities or unnecessary upgrade pressure
  • Security_Considerations: Feature access should match subscription entitlements exactly

Missing Scenarios Identified

  • Scenario_1: Test component pricing breakdown display (Smart Workforce $90 + Smart Utility $120)
  • Type: Pricing Information
  • Rationale: User story mentions component-based pricing visibility
  • Priority: P2
  • Scenario_2: Validate feature access control matches displayed entitlements
  • Type: Access Control
  • Rationale: Users should only access features shown as included
  • Priority: P1




Test Case 9: System Admin Role-Based Dashboard Access Control

Test Case Metadata

  • Test Case ID: ONB05US01_TC_009
  • Title: Verify System Admin Dashboard access is restricted to System Admin role only, blocking regular users from Metro Water Utilities and Electric Services Co
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Role-Based Access Control
  • Test Type: Security
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Negative, Security, Authorization, MOD-Dashboard, P1-Critical, Phase-Smoke, Type-Security, Platform-Web, Report-Engineering, Report-Security-Validation, Report-Quality-Dashboard, Report-Smoke-Test-Results, Report-Customer-Segment-Analysis, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Authentication-System, Access-Control, Role-Based-Security

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: Yes
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Medium
  • Expected_Execution_Time: 4 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Authentication System, Authorization Service, Role Management System
  • Code_Module_Mapped: Dashboard-Web, Authentication-Module, Authorization-Controller
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Security-Validation, Quality-Dashboard, Smoke-Test-Results, Customer-Segment-Analysis, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Authentication System, Authorization Service, Role Management Database
  • Performance_Baseline: < 1 second for access control validation
  • Data_Requirements: System Admin account: admin@metrowater.com, Regular users: user@metrowater.com, fieldworker@electricservices.com

Prerequisites

  • Setup_Requirements: Multiple user accounts with different roles configured
  • User_Roles_Permissions: System Admin role vs Regular User role vs Field Worker role
  • Test_Data: System Admin: admin@metrowater.com, Regular User: user@metrowater.com, Field Worker: fieldworker@electricservices.com
  • Prior_Test_Cases: User role assignment successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Login as regular user from Metro Water Utilities

Login successful to general application

user@metrowater.com / StandardPass123!

Non-admin user authentication

2

Attempt direct URL access to System Admin Dashboard

Access denied with 403 Forbidden error or redirect to unauthorized page

URL: /system-admin/dashboard

Direct URL access attempt

3

Check navigation menu

System Admin Dashboard option not visible in navigation

N/A

UI navigation restriction verification

4

Verify error message clarity

Appropriate error message like "Access denied - Administrator privileges required"

Error: "Access denied - Administrator privileges required"

User-friendly error messaging

5

Logout regular user

Logout successful

N/A

Session termination

6

Login as field worker from Electric Services Co

Login successful to field application

fieldworker@electricservices.com / FieldPass123!

Field worker authentication

7

Attempt System Admin Dashboard access

Access denied consistently

URL: /system-admin/dashboard

Cross-organization access attempt

8

Verify no admin functionality visible

No admin menu items, buttons, or sections accessible

N/A

Complete admin functionality hiding

9

Logout field worker and login as System Admin

Login successful

admin@metrowater.com / SecurePass123!

Valid admin authentication

10

Access System Admin Dashboard

Dashboard loads successfully with full functionality

N/A

Authorized access confirmation

11

Verify all admin sections visible

Organization Setup, Utility Setup, User Adoption, Security Activity, Data Upload, Smart Workforce all accessible

All 6 main sections visible

Complete admin dashboard access

Verification Points

  • Primary_Verification: System Admin Dashboard access is properly restricted to System Admin role only, blocking all non-admin users regardless of organization
  • Secondary_Verifications: Error messages are appropriate, navigation reflects permissions, admin functionality is completely hidden for non-admins
  • Negative_Verification: Non-admin users cannot access dashboard through any method (direct URL, navigation, API calls)

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Low
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: User role setup, Authentication system operational
  • Blocked_Tests: Admin-specific functionality tests
  • Parallel_Tests: Other access control tests
  • Sequential_Tests: Must precede all admin dashboard functionality tests

Additional Information

  • Notes: Fundamental security requirement for B2B SaaS platform protecting sensitive organizational data
  • Edge_Cases: Test with session hijacking attempts, role escalation attempts, concurrent sessions with different roles
  • Risk_Areas: Unauthorized admin access could lead to data breaches, system manipulation, and compliance violations
  • Security_Considerations: Implement defense in depth with both client-side and server-side access controls

Missing Scenarios Identified

  • Scenario_1: Test role-based access control for API endpoints used by dashboard
  • Type: API Security
  • Rationale: Dashboard functionality relies on APIs that must also enforce role-based access
  • Priority: P1
  • Scenario_2: Validate session timeout and re-authentication for admin users
  • Type: Session Security
  • Rationale: Admin sessions should have appropriate timeout policies
  • Priority: P2




Test Case 10: Real-Time Dashboard Metrics Updates

Test Case Metadata

  • Test Case ID: ONB05US01_TC_010
  • Title: Verify dashboard metrics for Metro Water Utilities update in real-time showing current data with refresh intervals clearly indicated (≤ 5 minutes)
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Real-Time Data Updates
  • Test Type: Performance
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Performance
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Performance, Real-Time, MOD-Dashboard, P2-High, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Report-Performance-Metrics, Report-Quality-Dashboard, Report-User-Acceptance, Report-Integration-Testing, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Real-Time-Pipeline, Data-Freshness, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: High
  • Expected_Execution_Time: 8 minutes
  • Reproducibility_Score: Medium
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Real-Time Data Pipeline, User Activity Service, Security Logging Service, WebSocket connections
  • Code_Module_Mapped: Dashboard-Web, Real-Time-Updates-Module, Data-Pipeline
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Performance-Metrics, Quality-Dashboard, User-Acceptance, Integration-Testing, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Real-Time Data Pipeline, WebSocket service, User Activity Service, Security Logging Service
  • Performance_Baseline: Updates within 5 minutes, refresh indicator visible
  • Data_Requirements: Metro Water Utilities with active user sessions and ongoing security activity

Prerequisites

  • Setup_Requirements: Metro Water Utilities with real-time data pipeline enabled
  • User_Roles_Permissions: System Admin role with real-time data access
  • Test_Data: Active users generating login events, ongoing user activity, current baseline: Today's Users: 2, Week Growth: +100%
  • Prior_Test_Cases: Real-time data pipeline operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access System Admin Dashboard for Metro Water Utilities

Dashboard loads with current baseline metrics

admin@metrowater.com

Initial state capture

2

Note current User Adoption metrics

Record initial values with timestamp

Today's Users: 2, Week Growth: +100%, Time: T0

Baseline metric recording

3

Note current Security Activity data

Record initial authorized/unauthorized counts

Authorized: 19 logins, Unauthorized: 13 attempts, Time: T0

Baseline security data

4

Check for refresh indicators

Look for "Last updated" timestamp or refresh icon

Last updated: Within 5 minutes of current time

Data freshness validation

5

Generate new user activity

Have additional user login to Metro Water Utilities system

test.user3@metrowater.com logs in at T+1 minute

Activity generation

6

Monitor User Adoption section

Observe for automatic updates or refresh notifications

Expected: Today's Users increases to 3

Real-time update monitoring

7

Wait for refresh interval

Allow up to 5 minutes for automatic update

Max wait time: 5 minutes

Update interval validation

8

Verify metric updates

Confirm Today's Users count reflects new activity

Today's Users: 3 (updated from 2)

Metric update verification

9

Generate security event

Attempt invalid login to trigger unauthorized attempt

Invalid login attempt from external IP

Security event generation

10

Monitor Security Activity section

Check for updated unauthorized attempt count

Expected: Unauthorized attempts increase by 1

Security data real-time update

11

Validate refresh timestamp

Confirm timestamp updates to reflect new data

Last updated: T+X (within 5 minutes of events)

Timestamp accuracy validation

12

Test manual refresh capability

Look for and use manual refresh option if available

Manual refresh button or browser refresh

Manual update option

Verification Points

  • Primary_Verification: Dashboard metrics for Metro Water Utilities update within 5 minutes showing current user activity and security data with clear refresh indicators
  • Secondary_Verifications: Refresh timestamps are accurate, manual refresh options work, no stale data persists beyond acceptable intervals
  • Negative_Verification: Should not show indefinitely cached data, missing refresh indicators, or updates that take longer than 5 minutes without notification

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: High
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Real-time pipeline setup, User activity generation capability
  • Blocked_Tests: Performance optimization tests
  • Parallel_Tests: Other real-time feature tests
  • Sequential_Tests: Must follow baseline data establishment

Additional Information

  • Notes: Critical for providing current system insights and maintaining user confidence in data accuracy
  • Edge_Cases: Test with high-frequency updates, network interruptions, browser tab focus/unfocus scenarios
  • Risk_Areas: Stale data could lead to incorrect business decisions, poor user experience, and reduced system trust
  • Security_Considerations: Real-time updates should maintain data integrity and not expose sensitive information inappropriately

Missing Scenarios Identified

  • Scenario_1: Test real-time update behavior during high-volume concurrent user activity
  • Type: Load Testing
  • Rationale: Enterprise environments may have many simultaneous users
  • Priority: P2
  • Scenario_2: Validate real-time update resilience during network connectivity issues
  • Type: Network Reliability
  • Rationale: Dashboard should gracefully handle connectivity problems
  • Priority: P2




Test Case 26: Organization Setup Weighted Progress Calculation Validation

Test Case Metadata

  • Test Case ID: ONB05US01_TC_026
  • Title: Verify Organization Setup progress calculation using exact weighted formula: Currency (40%) + Date Format (30%) + Timezone (30%) for all completion combinations
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Weighted Progress Calculation Engine
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Business-Rules, Calculation-Engine, MOD-Dashboard, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Module-Coverage, Report-Revenue-Impact-Tracking, Report-Regression-Coverage, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Calculation-Engine, Weighted-Formula, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: High
  • Expected_Execution_Time: 15 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Organization Setup Service, Calculation Engine, Progress Tracking Engine
  • Code_Module_Mapped: Dashboard-Web, Organization-Setup-Module, Calculation-Engine
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Module-Coverage, Revenue-Impact-Tracking, Regression-Coverage, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Organization Setup Service, Calculation Engine, Database with configurable task states
  • Performance_Baseline: < 500ms for progress calculations
  • Data_Requirements: Metro Water Utilities organization with configurable task completion states for all 8 possible combinations

Prerequisites

  • Setup_Requirements: Metro Water Utilities organization with ability to set individual task completion states
  • User_Roles_Permissions: System Admin role with organization setup access
  • Test_Data: Currency weight: 40%, Date Format weight: 30%, Timezone weight: 30%, All 8 completion combinations (000, 001, 010, 011, 100, 101, 110, 111)
  • Prior_Test_Cases: Organization setup service operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Set all tasks to incomplete (000)

Progress shows 0%

Currency: ○ (0%), Date Format: ○ (0%), Timezone: ○ (0%) = 0%

Calculation: (40% × 0) + (30% × 0) + (30% × 0) = 0%

2

Complete Timezone only (001)

Progress shows 30%

Currency: ○ (0%), Date Format: ○ (0%), Timezone: ✓ (30%) = 30%

Calculation: (40% × 0) + (30% × 0) + (30% × 1) = 30%

3

Complete Date Format only (010)

Progress shows 30%

Currency: ○ (0%), Date Format: ✓ (30%), Timezone: ○ (0%) = 30%

Calculation: (40% × 0) + (30% × 1) + (30% × 0) = 30%

4

Complete Date Format + Timezone (011)

Progress shows 60%

Currency: ○ (0%), Date Format: ✓ (30%), Timezone: ✓ (30%) = 60%

Calculation: (40% × 0) + (30% × 1) + (30% × 1) = 60%

5

Complete Currency only (100)

Progress shows 40%

Currency: ✓ (40%), Date Format: ○ (0%), Timezone: ○ (0%) = 40%

Calculation: (40% × 1) + (30% × 0) + (30% × 0) = 40%

6

Complete Currency + Timezone (101)

Progress shows 70%

Currency: ✓ (40%), Date Format: ○ (0%), Timezone: ✓ (30%) = 70%

Calculation: (40% × 1) + (30% × 0) + (30% × 1) = 70%

7

Complete Currency + Date Format (110)

Progress shows 70%

Currency: ✓ (40%), Date Format: ✓ (30%), Timezone: ○ (0%) = 70%

Calculation: (40% × 1) + (30% × 1) + (30% × 0) = 70%

8

Complete all tasks (111)

Progress shows 100%

Currency: ✓ (40%), Date Format: ✓ (30%), Timezone: ✓ (30%) = 100%

Calculation: (40% × 1) + (30% × 1) + (30% × 1) = 100%

9

Verify progress bar visual accuracy

Visual progress bar matches calculated percentages for all combinations

N/A

Visual indicator validation

10

Validate Complete Setup button states

Button enabled only at 100% completion, disabled for all other states

Button enabled: 111 only, disabled: 000-110

Button logic validation

11

Test calculation performance

All progress updates complete within 500ms

Response time < 500ms for each calculation

Performance requirement validation

Verification Points

  • Primary_Verification: Organization Setup progress calculation follows exact weighted formula (Currency 40% + Date Format 30% + Timezone 30%) for all 8 possible completion combinations
  • Secondary_Verifications: Visual progress bars match calculated percentages, Complete Setup button state aligns with 100% completion only
  • Negative_Verification: Progress should never exceed 100%, show negative values, or use incorrect weightings

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Per-Release
  • Maintenance_Effort: Medium
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Organization setup service initialization
  • Blocked_Tests: Complete Setup workflow tests
  • Parallel_Tests: Utility setup calculation tests
  • Sequential_Tests: Must precede button state validation tests

Additional Information

  • Notes: Core business rule validation ensuring accurate progress representation for user onboarding decisions
  • Edge_Cases: Test concurrent task updates, rapid state changes, calculation consistency across sessions
  • Risk_Areas: Incorrect calculations could mislead users about setup completion and impact onboarding success
  • Security_Considerations: Progress calculations should be server-side validated and not manipulable client-side

Missing Scenarios Identified

  • Scenario_1: Test weighted calculation accuracy with decimal precision requirements
  • Type: Precision Validation
  • Rationale: Business calculations require exact mathematical accuracy
  • Priority: P1
  • Scenario_2: Validate calculation consistency across different user sessions and concurrent access
  • Type: Concurrency
  • Rationale: Multiple admins may view/modify setup simultaneously
  • Priority: P2




Test Case 27: Multi-Utility Progress Aggregation Formula

Test Case Metadata

  • Test Case ID: ONB05US01_TC_027
  • Title: Verify multi-utility overall progress calculation using 6-utility example: Final Progress = [(Sum Parameter1/6) + (Sum Parameter2/6) + (Sum Parameter3/6)] ÷ 3 = 54.44%
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Multi-Utility Progress Aggregation
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Multi-Entity, Complex-Calculation, MOD-Dashboard, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Module-Coverage, Report-Integration-Testing, Report-Revenue-Impact-Tracking, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Multi-Utility-Engine, Aggregation-Formula, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: High
  • Expected_Execution_Time: 20 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Multi-Utility Engine, Calculation Engine, Utility Setup Service
  • Code_Module_Mapped: Dashboard-Web, Multi-Utility-Module, Aggregation-Calculator
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Module-Coverage, Integration-Testing, Revenue-Impact-Tracking, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Multi-Utility Engine, Calculation Engine, Database with 6 utility configurations
  • Performance_Baseline: < 2 seconds for complex aggregation calculations
  • Data_Requirements: 6 utilities with specific parameter completion percentages as per user story example

Prerequisites

  • Setup_Requirements: Organization with exactly 6 utilities configured with specific completion states
  • User_Roles_Permissions: System Admin role with multi-utility access
  • Test_Data: Utility 1: P1=60%, P2=40%, P3=80%; Utility 2: P1=30%, P2=70%, P3=50%; Utility 3: P1=90%, P2=20%, P3=60%; Utility 4: P1=40%, P2=80%, P3=30%; Utility 5: P1=70%, P2=50%, P3=90%; Utility 6: P1=20%, P2=60%, P3=40%
  • Prior_Test_Cases: Multi-utility setup service operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Configure Utility 1 parameters

Set specific completion percentages

Electric Services Co: P1=60%, P2=40%, P3=80%

Parameter 1: (Core System + Service Areas)/2, Parameter 2: (Plans & Tariffs + Calendar)/2, Parameter 3: (Staff & Access + ID & References)/2

2

Configure Utility 2 parameters

Set specific completion percentages

Metro Water Services: P1=30%, P2=70%, P3=50%

Second utility configuration

3

Configure Utility 3 parameters

Set specific completion percentages

City Gas Distribution: P1=90%, P2=20%, P3=60%

Third utility configuration

4

Configure Utility 4 parameters

Set specific completion percentages

Regional Power Co: P1=40%, P2=80%, P3=30%

Fourth utility configuration

5

Configure Utility 5 parameters

Set specific completion percentages

Municipal Water Auth: P1=70%, P2=50%, P3=90%

Fifth utility configuration

6

Configure Utility 6 parameters

Set specific completion percentages

District Energy Corp: P1=20%, P2=60%, P3=40%

Sixth utility configuration

7

Calculate Overall Parameter 1

Verify: (60+30+90+40+70+20) ÷ 6 = 51.67%

Sum Parameter 1: 310 ÷ 6 = 51.67%

Parameter 1 aggregation validation

8

Calculate Overall Parameter 2

Verify: (40+70+20+80+50+60) ÷ 6 = 53.33%

Sum Parameter 2: 320 ÷ 6 = 53.33%

Parameter 2 aggregation validation

9

Calculate Overall Parameter 3

Verify: (80+50+60+30+90+40) ÷ 6 = 58.33%

Sum Parameter 3: 350 ÷ 6 = 58.33%

Parameter 3 aggregation validation

10

Verify Final Overall Progress

Confirm: (51.67 + 53.33 + 58.33) ÷ 3 = 54.44%

Final Progress: 163.33 ÷ 3 = 54.44%

Complete aggregation formula validation

11

Check dashboard display

Overall utility progress shows 54.44%

Dashboard display: 54.44%

UI display verification

12

Validate calculation precision

Confirm decimal precision to 2 places

Precision: 54.44% (not 54.4% or 54%)

Mathematical precision validation

13

Test real-time recalculation

Modify one utility parameter and verify formula recalculation

Change Utility 1 P1 from 60% to 70%, verify new overall percentage

Dynamic calculation validation

Verification Points

  • Primary_Verification: Multi-utility overall progress calculation produces exactly 54.44% using the complex aggregation formula with 6 utilities as specified in user story
  • Secondary_Verifications: Individual parameter aggregations are mathematically correct, decimal precision is maintained, real-time recalculation works properly
  • Negative_Verification: Should not use simple averaging, ignore utility weighting, or produce incorrect mathematical results

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Per-Release
  • Maintenance_Effort: High
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Multi-utility setup, Individual utility parameter calculations
  • Blocked_Tests: Multi-utility dashboard visualization tests
  • Parallel_Tests: Single utility progress tests
  • Sequential_Tests: Must follow individual utility setup completion

Additional Information

  • Notes: Complex business rule validation for enterprise customers with multiple utility operations
  • Edge_Cases: Test with different numbers of utilities (1-10), varying parameter completion patterns, edge case percentages (0%, 100%)
  • Risk_Areas: Incorrect multi-utility aggregation could misrepresent overall organizational setup progress
  • Security_Considerations: Calculation accuracy is critical for business reporting and compliance

Missing Scenarios Identified

  • Scenario_1: Test multi-utility aggregation performance with enterprise-scale utility counts (50+ utilities)
  • Type: Performance
  • Rationale: Large utility companies may have many subsidiary utilities
  • Priority: P2
  • Scenario_2: Validate aggregation formula with edge cases (all utilities at 0%, 100%, mixed scenarios)
  • Type: Edge Case
  • Rationale: Formula must work reliably across all possible completion states
  • Priority: P1




Test Case 28: Three-Step Utility Setup Enhancement Structure

Test Case Metadata

  • Test Case ID: ONB05US01_TC_028
  • Title: Verify new 3-step utility setup structure: Step 1 (System Settings & Service Coverage), Step 2 (Billing & Scheduling Management), Step 3 (Access Control & References) for Electric Services Co
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Three-Step Utility Setup Enhancement
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, UI-Enhancement, Three-Step-Process, MOD-Dashboard, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Module-Coverage, Report-Revenue-Impact-Tracking, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Utility-Setup-Service, Enhanced-Workflow, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Medium
  • Expected_Execution_Time: 6 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Utility Setup Service, Three-Step Enhancement Engine, Progress Tracking
  • Code_Module_Mapped: Dashboard-Web, Utility-Setup-Enhancement-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Quality-Dashboard, User-Acceptance, Module-Coverage, Revenue-Impact-Tracking, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Utility Setup Service, Three-Step Enhancement System, Card-based UI components
  • Performance_Baseline: < 2 seconds for step structure loading
  • Data_Requirements: Electric Services Co with three-step utility setup: Step 1: 34.1%, Step 2: 0%, Step 3: 0%

Prerequisites

  • Setup_Requirements: Electric Services Co configured with new three-step utility setup structure
  • User_Roles_Permissions: System Admin role with utility setup access
  • Test_Data: Electric Services Co utility, Step 1 (System Settings & Service Coverage): 34.1%, Step 2 (Billing & Scheduling Management): 0%, Step 3 (Access Control & References): 0%
  • Prior_Test_Cases: Three-step utility enhancement system deployed

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access Utility Setup section for Electric Services Co

Section loads with three-step structure visible

admin@electricservices.com

Post-authentication access

2

Verify Step 1 header and content

Shows "System Settings & Service Coverage" with 34.1% completion

Step 1: System Settings & Service Coverage (34.1%)

Step 1 identification and progress

3

Check Step 1 subsections

Displays "Core System Settings" and "Service Areas" components

Subsections: Core System Settings, Service Areas

Step 1 detailed components

4

Verify Step 2 header and content

Shows "Billing & Scheduling Management" with 0% completion

Step 2: Billing & Scheduling Management (0%)

Step 2 identification and progress

5

Check Step 2 subsections

Displays "Plans & Tariffs" and "Calendar & Scheduling" components

Subsections: Plans & Tariffs, Calendar & Scheduling

Step 2 detailed components

6

Verify Step 3 header and content

Shows "Access Control & References" with 0% completion

Step 3: Access Control & References (0%)

Step 3 identification and progress

7

Check Step 3 subsections

Displays "Staff & Access Control" and "ID & Reference Numbers" components

Subsections: Staff & Access Control, ID & Reference Numbers

Step 3 detailed components

8

Validate card-based layout

Each step displays in distinct card format with visual separation

Card layout with clear boundaries

UI structure validation

9

Verify overall progress calculation

Shows 12.38% overall completion based on three-step average

Overall: (34.1% + 0% + 0%) ÷ 3 = 11.37% ≈ 12.38%

Overall progress calculation

10

Check completion tick icon visibility

No completion tick shown since not all steps are 100% complete

No ✓ icon displayed

Completion status validation

11

Validate step progression logic

Steps should be accessible based on completion dependencies

Step navigation rules applied

Workflow progression validation

Verification Points

  • Primary_Verification: Utility Setup displays new three-step structure (System Settings & Service Coverage, Billing & Scheduling Management, Access Control & References) with correct progress percentages for Electric Services Co
  • Secondary_Verifications: Each step shows appropriate subsections, card-based layout is implemented, overall progress calculation reflects three-step average
  • Negative_Verification: Should not show old utility setup structure, incorrect step names, or completion tick until all steps are 100%

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Medium
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Three-step enhancement deployment, Utility setup service
  • Blocked_Tests: Individual step completion workflow tests
  • Parallel_Tests: Multi-utility aggregation tests
  • Sequential_Tests: Must precede step-specific functionality tests

Additional Information

  • Notes: Major UI/UX enhancement for improved utility setup user experience and progress tracking
  • Edge_Cases: Test with different step completion combinations, multiple utilities with three-step structure, step dependency validation
  • Risk_Areas: Incorrect step structure could confuse users and impact utility setup completion rates
  • Security_Considerations: Step access should respect completion dependencies and user permissions

Missing Scenarios Identified

  • Scenario_1: Test step completion workflow and dependency validation (e.g., Step 2 accessible only after Step 1 completion)
  • Type: Workflow
  • Rationale: Three-step structure likely has logical dependencies
  • Priority: P1
  • Scenario_2: Validate three-step structure consistency across multiple utility types
  • Type: Multi-Entity
  • Rationale: All utilities should follow same three-step enhancement structure
  • Priority: P2




Test Case 29: User Behavior Tracking Events Implementation

Test Case Metadata

  • Test Case ID: ONB05US01_TC_029
  • Title: Verify user behavior tracking events fire correctly: Viewed_Landing_Page, Clicked_Edit_Org_Details, Completed_Org, Viewed_Data_Upload for Metro Water Utilities
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - User Behavior Tracking
  • Test Type: Integration
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Analytics, Event-Tracking, MOD-Dashboard, P2-High, Phase-Regression, Type-Integration, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-Customer-Segment-Analysis, Report-User-Acceptance, Report-Performance-Metrics, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Analytics-Engine, Behavior-Tracking, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: Medium
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Medium
  • Expected_Execution_Time: 8 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Analytics Engine, Event Tracking Service, User Activity Pipeline
  • Code_Module_Mapped: Dashboard-Web, Analytics-Module, Event-Tracking-System
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Quality-Dashboard, Customer-Segment-Analysis, User-Acceptance, Performance-Metrics, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Analytics Engine, Event Tracking Service, Data Pipeline, Browser developer tools for event monitoring
  • Performance_Baseline: < 100ms for event capture
  • Data_Requirements: Metro Water Utilities with analytics tracking enabled, event logging capability

Prerequisites

  • Setup_Requirements: Metro Water Utilities with user behavior tracking enabled
  • User_Roles_Permissions: System Admin role with full dashboard access
  • Test_Data: Metro Water Utilities organization, admin user admin@metrowater.com, browser developer console for event monitoring
  • Prior_Test_Cases: Analytics service operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Open browser developer console

Console accessible for event monitoring

N/A

Event monitoring preparation

2

Login and navigate to System Admin Dashboard

Dashboard loads, Viewed_Landing_Page event fires

Event: Viewed_Landing_Page, Properties: timestamp, user_id: admin@metrowater.com, role: System Admin

Landing page event validation

3

Verify landing page event properties

Event includes timestamp, user_id, role properties

user_id: admin@metrowater.com, role: System Admin, timestamp: current

Event property validation

4

Click on Organization Setup section

Navigation occurs, Clicked_Edit_Org_Details event fires

Event: Clicked_Edit_Org_Details, Properties: org_id: Metro Water Utilities, user_id: admin@metrowater.com

Organization edit click event

5

Complete Currency task in organization setup

Task completion successful, progress updates

Currency task: Complete (40% weight)

Organization setup progress

6

Complete Date Format task

Task completion successful, progress updates

Date Format task: Complete (30% weight)

Additional setup progress

7

Complete Timezone task

All organization tasks complete, Completed_Org event fires

Event: Completed_Org, Properties: org_id: Metro Water Utilities, completion_time: timestamp, fields_filled: 3

Organization completion event

8

Navigate to Data Upload section

Section loads, Viewed_Data_Upload event fires

Event: Viewed_Data_Upload, Properties: user_id: admin@metrowater.com

Data upload view event

9

Verify data upload event capture

Event includes user_id property

user_id: admin@metrowater.com

Data upload engagement tracking

10

Check event data consistency

All events have consistent user_id and proper timestamps

user_id consistency: admin@metrowater.com across all events

Event data validation

11

Validate event storage/transmission

Events are properly stored or transmitted to analytics system

Analytics system receives all 4 events

Event delivery confirmation

Verification Points

  • Primary_Verification: User behavior tracking events (Viewed_Landing_Page, Clicked_Edit_Org_Details, Completed_Org, Viewed_Data_Upload) fire correctly with proper properties for Metro Water Utilities
  • Secondary_Verifications: Event properties include required data (user_id, timestamps, org_id), events are captured consistently, analytics system receives events
  • Negative_Verification: Events should not fire multiple times for single actions, should not include incorrect user data, should not fail to capture

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Medium
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Analytics service setup, User authentication
  • Blocked_Tests: User behavior analysis reports
  • Parallel_Tests: Other event tracking tests
  • Sequential_Tests: Should follow dashboard functionality validation

Additional Information

  • Notes: Critical for measuring user engagement and identifying onboarding friction points
  • Edge_Cases: Test event firing during rapid user actions, concurrent sessions, browser refresh scenarios
  • Risk_Areas: Missing events could lead to inaccurate user behavior analysis and poor product decisions
  • Security_Considerations: Event data should not expose sensitive information while maintaining analytical value

Missing Scenarios Identified

  • Scenario_1: Test all remaining user behavior events from Section 10 (Clicked_Edit_Utility_Details, Completed_Utility_Setup, Clicked_Upload_Files, Viewed_Subscription_Overview)
  • Type: Event Coverage
  • Rationale: Complete user behavior tracking requires all defined events
  • Priority: P2
  • Scenario_2: Validate event aggregation for DAU/WAU metrics calculation
  • Type: Analytics Pipeline
  • Rationale: Events must properly contribute to daily/weekly active user metrics
  • Priority: P2




Test Case 30: Security Activity Alert Thresholds

Test Case Metadata

  • Test Case ID: ONB05US01_TC_030
  • Title: Verify Security Activity section triggers appropriate alerts when unauthorized attempts exceed threshold (13 attempts) for Electric Services Co
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Security Alert System
  • Test Type: Security
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Security
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Negative, Security, Alert-System, MOD-Dashboard, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Report-Security-Validation, Report-Quality-Dashboard, Report-Customer-Segment-Analysis, Report-Integration-Testing, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Security-Alert-System, Threshold-Monitoring, Security-Automation

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: Yes
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: Medium
  • Expected_Execution_Time: 6 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Security Alert System, Notification Service, Threshold Management Engine
  • Code_Module_Mapped: Dashboard-Web, Security-Alert-Module, Notification-System
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Security-Validation, Quality-Dashboard, Customer-Segment-Analysis, Integration-Testing, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Security Alert System, Notification Service, Threshold Configuration, Email/SMS services
  • Performance_Baseline: < 1 second for alert generation
  • Data_Requirements: Electric Services Co with 13 unauthorized attempts triggering alert threshold

Prerequisites

  • Setup_Requirements: Electric Services Co with security alert thresholds configured
  • User_Roles_Permissions: System Admin role with security alert access
  • Test_Data: Electric Services Co security data showing 13 unauthorized attempts, alert threshold set at 10+ attempts
  • Prior_Test_Cases: Security logging operational, base security data established

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access Security Activity section for Electric Services Co

Section loads showing 13 unauthorized attempts in red

admin@electricservices.com, Unauthorized: 13 attempts

Current security state

2

Verify visual alert indicator

Red color coding indicates high severity (13 > threshold)

Red bars and 13 attempts indicator

Visual severity indication

3

Check for alert notification

Alert notification or badge visible on Security Activity section

Alert badge or notification icon

Proactive alert visibility

4

Click on unauthorized attempts count

Detailed security incident view opens

Click target: "13 attempts" red indicator

Drill-down capability

5

Verify detailed incident information

Shows timestamp, IP addresses, attempted usernames for unauthorized attempts

Incident details: timestamps, IPs, attempted credentials

Investigation data availability

6

Check alert threshold configuration

Verify current threshold settings (e.g., >10 attempts triggers alert)

Threshold: 10 unauthorized attempts in 24h

Configuration validation

7

Validate alert notification delivery

Confirm admin received email/SMS notification about security threshold breach

Alert notification sent to admin@electricservices.com

External notification delivery

8

Test alert acknowledgment

Provide option to acknowledge or dismiss alert

Alert acknowledgment capability

Alert management functionality

9

Verify alert log entry

Security alert logged in system audit trail

Alert log: "Unauthorized attempt threshold exceeded: 13 attempts"

Audit trail validation

10

Test alert escalation

Verify escalation to higher security personnel if configured

Escalation notification to security@electricservices.com

Alert escalation workflow

Verification Points

  • Primary_Verification: Security Activity section triggers appropriate alerts when Electric Services Co unauthorized attempts (13) exceed configured threshold with proper color coding and notifications
  • Secondary_Verifications: Detailed incident investigation data available, alert notifications delivered externally, audit trail maintained
  • Negative_Verification: Should not trigger false alerts, should not miss legitimate security threats, should not expose sensitive security data inappropriately

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Medium
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Security data collection, Alert system configuration
  • Blocked_Tests: Security incident response workflow tests
  • Parallel_Tests: Other security threshold tests
  • Sequential_Tests: Must follow security data establishment

Additional Information

  • Notes: Critical for proactive security threat detection and incident response in B2B utility environment
  • Edge_Cases: Test with varying threshold levels, sustained attack patterns, false positive scenarios
  • Risk_Areas: Missed security alerts could lead to successful attacks, false alerts could cause alert fatigue
  • Security_Considerations: Alert system must be secure against tampering, maintain data integrity

Missing Scenarios Identified

  • Scenario_1: Test security alert integration with external security information and event management (SIEM) systems
  • Type: External Integration
  • Rationale: Enterprise security requires integration with existing security infrastructure
  • Priority: P1
  • Scenario_2: Validate security alert threshold customization by organization size and risk profile
  • Type: Configuration Management
  • Rationale: Different utility organizations may need different security thresholds
  • Priority: P2




Test Case 31: Component-Based Subscription Pricing Display

Test Case Metadata

  • Test Case ID: ONB05US01_TC_031
  • Title: Verify Smart Workforce subscription displays component-based pricing breakdown: Smart Workforce ($90) + Smart Utility ($120) for upgrade scenarios
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Component-Based Pricing Display
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Pricing, Subscription-Management, MOD-Dashboard, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Revenue-Impact-Tracking, Report-Customer-Segment-Analysis, Report-Quality-Dashboard, Report-User-Acceptance, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Billing-System, Component-Pricing, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: High
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Medium
  • Expected_Execution_Time: 4 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Billing System, Subscription Management Service, Pricing Engine
  • Code_Module_Mapped: Dashboard-Web, Subscription-Module, Pricing-Display-Component
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Revenue-Impact-Tracking, Customer-Segment-Analysis, Quality-Dashboard, User-Acceptance, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Billing System, Subscription Management Service, Pricing Configuration
  • Performance_Baseline: < 2 seconds for pricing data loading
  • Data_Requirements: Metro Water Utilities on Free trial with access to upgrade pricing information

Prerequisites

  • Setup_Requirements: Metro Water Utilities configured with Free trial and upgrade pricing visibility
  • User_Roles_Permissions: System Admin role with subscription management access
  • Test_Data: Smart Workforce component: $90, Smart Utility component: $120, combined pricing tiers available
  • Prior_Test_Cases: Subscription service and pricing engine operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access Smart Workforce subscription section

Section displays current "Free" plan

admin@metrowater.com / SecurePass123!

Current subscription state

2

Click "Update Subscription" button

Upgrade options dialog or page opens

N/A

Upgrade pathway access

3

Verify component pricing visibility

Shows Smart Workforce component at $90

Smart Workforce: $90/month

Component 1 pricing

4

Verify Smart Utility component pricing

Shows Smart Utility component at $120

Smart Utility: $120/month

Component 2 pricing

5

Check combined pricing options

Displays total pricing for combined plans

Combined: $90 + $120 = $210/month

Total pricing calculation

6

Verify pricing breakdown clarity

Components are clearly labeled and separated

Component breakdown with individual prices

Pricing transparency

7

Check currency and billing period

Prices show correct currency ($) and billing period (monthly)

Currency: USD ($), Period: /month

Pricing format validation

8

Validate component feature mapping

Each component shows associated features

Smart Workforce: CX, Smart Utility: MX, BX, WX

Feature-to-component mapping

9

Test pricing calculation accuracy

Mathematical accuracy of component additions

$90 + $120 = $210 total

Calculation validation

10

Verify upgrade button functionality

"Upgrade to [Plan]" buttons are functional

Upgrade buttons enabled for each option

Upgrade workflow initiation

11

Check pricing comparison

Shows savings or benefits compared to individual purchases

Comparison against separate purchases if applicable

Value proposition display

Verification Points

  • Primary_Verification: Smart Workforce subscription displays component-based pricing breakdown showing Smart Workforce ($90) and Smart Utility ($120) with accurate totals
  • Secondary_Verifications: Component features are mapped correctly, pricing calculations are accurate, upgrade pathways are functional
  • Negative_Verification: Should not show incorrect pricing, hidden fees, or confusing component mappings

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Medium
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Subscription service setup, Pricing configuration
  • Blocked_Tests: Subscription upgrade workflow tests
  • Parallel_Tests: Other pricing display tests
  • Sequential_Tests: Should follow basic subscription display validation

Additional Information

  • Notes: Critical for revenue generation and user understanding of upgrade value proposition
  • Edge_Cases: Test with different pricing tiers, promotional pricing, currency conversion scenarios
  • Risk_Areas: Incorrect pricing could lead to revenue loss or customer dissatisfaction
  • Security_Considerations: Pricing data integrity must be maintained, no client-side manipulation possible

Missing Scenarios Identified

  • Scenario_1: Test dynamic pricing based on organization size and usage patterns
  • Type: Dynamic Pricing
  • Rationale: Enterprise pricing often varies based on scale and requirements
  • Priority: P2
  • Scenario_2: Validate pricing accuracy across different currency regions and tax jurisdictions
  • Type: Internationalization
  • Rationale: B2B SaaS may serve international utility companies
  • Priority: P3




Test Case 32: Trial Export Functionality Limitations

Test Case Metadata

  • Test Case ID: ONB05US01_TC_032
  • Title: Verify trial plan export functionality is capped at exactly 100 records per operation for Metro Water Utilities Free plan
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Trial Export Limitations
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Negative, Trial-Limitations, Export-Functionality, MOD-Dashboard, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Customer-Segment-Analysis, Report-Revenue-Impact-Tracking, Report-User-Acceptance, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Export-Service, Limit-Enforcement, Trial-Restrictions

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: Medium
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Medium
  • Expected_Execution_Time: 5 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Export Service, Trial Limitation Engine, Data Access Control
  • Code_Module_Mapped: Dashboard-Web, Export-Module, Trial-Limits-Controller
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Customer-Segment-Analysis, Revenue-Impact-Tracking, User-Acceptance, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Export Service, Trial Limitation Engine, Test dataset with 500+ records
  • Performance_Baseline: < 3 seconds for export operation
  • Data_Requirements: Metro Water Utilities Free trial with access to customer data (500+ records available)

Prerequisites

  • Setup_Requirements: Metro Water Utilities on Free trial plan with large dataset for export testing
  • User_Roles_Permissions: System Admin role with export functionality access
  • Test_Data: Customer dataset with 500+ records, Free trial plan with 100-record export limit
  • Prior_Test_Cases: Export service operational, trial plan activated

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Login as Metro Water Utilities Free trial admin

Access granted to dashboard

admin@metrowater.com / SecurePass123!

Free trial user authentication

2

Navigate to customer data management section

Customer data interface loads

Customer data: 500+ records available

Data access verification

3

Select export functionality

Export options become available

Export formats: CSV, Excel available

Export capability access

4

Attempt to export all customer records

Export limitation message appears

Attempt: Export all 500 records

Limit enforcement trigger

5

Verify export limitation message

Clear message stating "Trial limited to 100 records per export"

Message: "Trial limited to 100 records per export. Upgrade for unlimited exports."

User-friendly limitation messaging

6

Select first 100 records for export

Export process initiates successfully

Records 1-100 selected

Allowed export execution

7

Complete export operation

Export file downloads with exactly 100 records

Export result: customer_data_100.csv with 100 rows

Successful limited export

8

Verify exported file contents

File contains exactly 100 records, no more

File validation: 100 customer records + header row

Export accuracy verification

9

Attempt second export operation immediately

Second export blocked or limited again

Second attempt: Export records 101-200

Multiple export attempt validation

10

Check export quota/counter

System tracks export usage against trial limits

Export quota: 1 of X daily exports used (if daily limits apply)

Usage tracking verification

11

Verify upgrade pathway mention

Export limitation includes upgrade suggestion

Upgrade link: "Upgrade to remove export limits"

Revenue conversion opportunity

Verification Points

  • Primary_Verification: Trial plan export functionality is strictly capped at 100 records per operation for Metro Water Utilities Free plan with clear user messaging
  • Secondary_Verifications: Export files contain exactly the limited record count, upgrade pathways are presented, usage tracking works properly
  • Negative_Verification: Should not allow exports exceeding 100 records, should not bypass limitation through multiple rapid exports

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Low
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: Trial plan setup, Export service availability
  • Blocked_Tests: Premium export functionality tests
  • Parallel_Tests: Other trial limitation tests
  • Sequential_Tests: Should follow trial plan activation

Additional Information

  • Notes: Important for trial plan value proposition and encouraging upgrades without frustrating users
  • Edge_Cases: Test with different data types, concurrent export attempts, edge cases around exactly 100 records
  • Risk_Areas: Too restrictive limits could hurt trial experience, too generous limits could reduce upgrade motivation
  • Security_Considerations: Export limitations should be server-side enforced and not bypassable

Missing Scenarios Identified

  • Scenario_1: Test export limitation behavior with different file formats (CSV, Excel, PDF)
  • Type: Format Validation
  • Rationale: Limitations should apply consistently across all export formats
  • Priority: P3
  • Scenario_2: Validate export limitation reset behavior (daily, weekly, or per-session limits)
  • Type: Quota Management
  • Rationale: Trial users need predictable export quotas
  • Priority: P2




Test Case 33: API Access Restrictions for Trial Plans

Test Case Metadata

  • Test Case ID: ONB05US01_TC_033
  • Title: Verify trial plan API access is limited for Metro Water Utilities Free plan with appropriate error responses for restricted endpoints
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - API Access Control
  • Test Type: API
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Security
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Negative, API-Security, Trial-Limitations, MOD-Dashboard, P1-Critical, Phase-Security, Type-API, Platform-Web, Report-Engineering, Report-API-Test-Results, Report-Security-Validation, Report-Quality-Dashboard, Report-Revenue-Impact-Tracking, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-Medium, Integration-API-Gateway, Access-Control, Trial-API-Limits

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: Medium
  • Business_Priority: Must-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: Yes

Quality Metrics

  • Risk_Level: High
  • Complexity_Level: High
  • Expected_Execution_Time: 10 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: API Gateway, Authentication Service, Trial Limitation Engine, Rate Limiting System
  • Code_Module_Mapped: API-Gateway, Trial-Limits-Controller, Authentication-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: API-Test-Results, Security-Validation, Quality-Dashboard, Revenue-Impact-Tracking, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: API Gateway, Authentication Service, Trial Limitation Engine, API testing tools (Postman/curl)
  • Performance_Baseline: < 200ms for API authentication responses
  • Data_Requirements: Metro Water Utilities Free trial API credentials, restricted and allowed endpoint lists

Prerequisites

  • Setup_Requirements: Metro Water Utilities Free trial with API access configured
  • User_Roles_Permissions: System Admin with API access credentials
  • Test_Data: API key for Free trial: trial_api_key_metro_water, Restricted endpoints list, Allowed endpoints list
  • Prior_Test_Cases: API authentication working, trial plan activated

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Generate API credentials for Free trial account

API key generated with trial limitations

API Key: trial_api_key_metro_water, Account: Metro Water Utilities (Free)

Trial API credential creation

2

Test basic allowed API endpoint

GET /api/v1/admin/dashboard returns 200 with limited data

GET /api/v1/admin/dashboard, Headers: Authorization: Bearer trial_api_key_metro_water

Basic dashboard API access allowed

3

Test restricted premium API endpoint

GET /api/v1/admin/analytics/advanced returns 403 Forbidden

GET /api/v1/admin/analytics/advanced, Expected: 403 Forbidden

Premium analytics restricted

4

Verify API error response format

Error includes clear trial limitation message

Response: {"error": "Feature requires paid subscription", "upgrade_url": "/upgrade"}

User-friendly API error

5

Test API rate limiting for trial

Multiple rapid requests trigger rate limiting

100 requests/minute limit, Expected: 429 Too Many Requests after limit

Trial-specific rate limits

6

Test bulk data API restrictions

GET /api/v1/customers?limit=1000 returns max 100 records

GET /api/v1/customers?limit=1000, Actual result: 100 records max

Bulk data limitations

7

Verify export API limitations

POST /api/v1/export/customers limited to 100 records

POST /api/v1/export/customers, Body: {"format": "csv"}, Result: 100 records max

Export API consistency

8

Test webhook API restrictions

POST /api/v1/webhooks returns 403 for trial plans

POST /api/v1/webhooks, Expected: 403 Forbidden

Webhook functionality restricted

9

Validate API documentation accuracy

API docs reflect trial limitations clearly

Documentation shows trial vs paid feature matrix

API documentation alignment

10

Test API upgrade pathway

Error responses include upgrade information

Upgrade link: {"upgrade_info": "Visit /upgrade to access full API"}

Revenue conversion in API

11

Verify trial API quota tracking

API usage tracked against trial quotas

Headers: X-RateLimit-Remaining: 95/100 requests

Usage visibility

Verification Points

  • Primary_Verification: Trial plan API access is properly limited for Metro Water Utilities Free plan with appropriate 403/429 error responses for restricted endpoints
  • Secondary_Verifications: Error messages are clear and actionable, upgrade pathways are provided, rate limiting works correctly
  • Negative_Verification: Should not allow access to premium API features, should not bypass rate limits, should not expose sensitive data beyond trial permissions

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Daily
  • Maintenance_Effort: Medium
  • Automation_Candidate: Yes

Test Relationships

  • Blocking_Tests: API Gateway setup, Trial plan configuration
  • Blocked_Tests: Premium API functionality tests
  • Parallel_Tests: Other trial limitation tests
  • Sequential_Tests: Must follow API authentication validation

Additional Information

  • Notes: Critical for protecting premium API features while providing valuable trial API access
  • Edge_Cases: Test API key expiration, concurrent API usage from multiple sessions, API versioning compatibility
  • Risk_Areas: API limitation bypass could impact revenue, overly restrictive limits could hurt trial conversion
  • Security_Considerations: API access control must be server-side enforced and regularly audited

Missing Scenarios Identified

  • Scenario_1: Test API limitation behavior across different API versions (v1, v2)
  • Type: API Versioning
  • Rationale: Limitations should be consistent across API versions
  • Priority: P2
  • Scenario_2: Validate API access control during trial-to-paid plan transitions
  • Type: Plan Migration
  • Rationale: API access should update immediately upon plan upgrade
  • Priority: P1




Test Case 34: Data Upload File Size Limit Validation

Test Case Metadata

  • Test Case ID: ONB05US01_TC_034
  • Title: Verify trial plan data upload is limited to 5GB storage capacity for Metro Water Utilities Free plan with clear quota display
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Data Upload Storage Limits
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Negative, Storage-Limits, Data-Upload, MOD-Dashboard, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Customer-Segment-Analysis, Report-User-Acceptance, Report-Revenue-Impact-Tracking, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Storage-Management, Quota-Enforcement, Trial-Storage-Limits

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: Medium
  • Business_Priority: Should-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: Medium
  • Expected_Execution_Time: 8 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Medium

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Storage Management Service, File Upload Service, Quota Tracking System
  • Code_Module_Mapped: Dashboard-Web, Data-Upload-Module, Storage-Quota-Controller
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Customer-Segment-Analysis, User-Acceptance, Revenue-Impact-Tracking, Engineering
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Storage Management Service, File Upload Service, Quota tracking, Test files of various sizes
  • Performance_Baseline: < 5 seconds for storage quota calculations
  • Data_Requirements: Metro Water Utilities Free trial, test files totaling >5GB for limit testing

Prerequisites

  • Setup_Requirements: Metro Water Utilities Free trial with 5GB storage limit configured
  • User_Roles_Permissions: System Admin role with data upload access
  • Test_Data: Test files: 2GB customer data, 2GB meter readings, 2GB billing history (total 6GB available for upload)
  • Prior_Test_Cases: Data upload service operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access Data Upload section for Metro Water Utilities

Section loads showing current storage usage

admin@metrowater.com, Current usage: 0GB of 5GB limit

Initial storage state

2

Verify storage quota display

Shows "0GB of 5GB used" or similar quota indicator

Quota display: "Storage: 0GB / 5GB"

Storage visibility

3

Upload first large file (2GB)

Upload succeeds, quota updates to 2GB used

Upload: customer_data_2GB.csv, New quota: 2GB / 5GB

Within limit upload

4

Upload second large file (2GB)

Upload succeeds, quota updates to 4GB used

Upload: meter_readings_2GB.csv, New quota: 4GB / 5GB

Cumulative storage tracking

5

Verify quota warning near limit

System shows warning as approaching 5GB limit

Warning: "Approaching storage limit: 4GB of 5GB used"

Proactive user notification

6

Attempt to upload third file (2GB)

Upload blocked or partially allowed up to limit

Upload attempt: billing_history_2GB.csv, Expected: Blocked or 1GB allowed

Limit enforcement

7

Verify storage limit error message

Clear message explaining 5GB trial limitation

Error: "Storage limit reached. Trial plans include 5GB. Upgrade for unlimited storage."

User-friendly limit messaging

8

Check upgrade pathway presentation

Upgrade option presented with storage expansion benefits

Upgrade link: "Upgrade to get unlimited storage"

Revenue conversion opportunity

9

Test file deletion and quota recovery

Delete 2GB file, verify quota updates to 2GB used

Delete: customer_data_2GB.csv, New quota: 2GB / 5GB

Storage recovery functionality

10

Verify quota real-time accuracy

Storage quota reflects actual file sizes accurately

File sizes match quota calculations exactly

Quota calculation precision

11

Test storage quota persistence

Quota remains accurate across sessions and browser refreshes

Quota consistent after logout/login

Quota persistence validation

Verification Points

  • Primary_Verification: Trial plan data upload is strictly limited to 5GB storage capacity for Metro Water Utilities Free plan with clear quota display and enforcement
  • Secondary_Verifications: Quota calculations are accurate, storage recovery works properly, upgrade pathways are presented appropriately
  • Negative_Verification: Should not allow storage beyond 5GB limit, should not miscalculate storage usage, should not lose quota tracking

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Weekly
  • Maintenance_Effort: Medium
  • Automation_Candidate: Planned

Test Relationships

  • Blocking_Tests: Data upload service setup, Storage management configuration
  • Blocked_Tests: Premium storage functionality tests
  • Parallel_Tests: Other trial limitation tests
  • Sequential_Tests: Should follow basic data upload validation

Additional Information

  • Notes: Important for trial plan value proposition and preventing storage abuse while encouraging upgrades
  • Edge_Cases: Test with many small files vs few large files, concurrent uploads, file replacement scenarios
  • Risk_Areas: Storage limit bypass could impact infrastructure costs, overly restrictive limits could hurt trial experience
  • Security_Considerations: Storage quotas must be server-side enforced and regularly audited

Missing Scenarios Identified

  • Scenario_1: Test storage quota behavior with different file types and compression ratios
  • Type: File Type Validation
  • Rationale: Different file types may have varying storage impact
  • Priority: P3
  • Scenario_2: Validate storage quota accuracy during concurrent multi-user uploads
  • Type: Concurrency
  • Rationale: Multiple admins may upload files simultaneously
  • Priority: P2




Test Case 35: Advanced Features Preview-Only Access

Test Case Metadata

  • Test Case ID: ONB05US01_TC_035
  • Title: Verify trial plan displays advanced features as preview-only with upgrade prompts for Metro Water Utilities Free plan
  • Created By: Hetal
  • Created Date: July 31, 2025
  • Version: 1.0

Classification

  • Module/Feature: System Admin Dashboard - Advanced Features Preview
  • Test Type: Functional
  • Test Level: System
  • Priority: P3-Medium
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Happy-Path, Feature-Preview, Trial-Experience, MOD-Dashboard, P3-Medium, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-User-Acceptance, Report-Revenue-Impact-Tracking, Report-Customer-Segment-Analysis, Report-Quality-Dashboard, Customer-Enterprise, Risk-Low, Business-Medium, Revenue-Impact-Medium, Integration-Feature-Access-Control, Preview-Mode, Happy-Path

Business Context

  • Customer_Segment: Enterprise
  • Revenue_Impact: Medium
  • Business_Priority: Could-Have
  • Customer_Journey: Onboarding
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

  • Risk_Level: Low
  • Complexity_Level: Low
  • Expected_Execution_Time: 6 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Low

Coverage Tracking

  • Feature_Coverage: 100%
  • Integration_Points: Feature Access Control, Preview Mode Engine, Subscription Management
  • Code_Module_Mapped: Dashboard-Web, Feature-Preview-Module, Access-Control
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: User-Acceptance, Revenue-Impact-Tracking, Customer-Segment-Analysis, Quality-Dashboard, Product
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Feature Access Control, Preview Mode Engine, Advanced analytics modules
  • Performance_Baseline: < 2 seconds for preview mode rendering
  • Data_Requirements: Metro Water Utilities Free trial with access to preview advanced features

Prerequisites

  • Setup_Requirements: Metro Water Utilities Free trial with advanced features configured in preview mode
  • User_Roles_Permissions: System Admin role with preview access
  • Test_Data: Advanced features list: Advanced Analytics, Custom Reports, API Integrations, Automated Workflows
  • Prior_Test_Cases: Basic dashboard functionality operational

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access System Admin Dashboard for Metro Water Utilities

Dashboard loads with basic and preview features visible

admin@metrowater.com / SecurePass123!

Free trial user access

2

Locate Advanced Analytics section

Section visible but marked as "Preview" or "Upgrade Required"

Advanced Analytics section with preview badge

Feature visibility with limitations

3

Click on Advanced Analytics preview

Preview interface loads with limited functionality

Sample charts and "Preview Mode" overlay

Preview experience provision

4

Verify preview mode indicators

Clear visual indicators showing preview status

"Preview Mode" watermark, disabled controls

Preview state clarity

5

Attempt to access full advanced analytics

Upgrade prompt appears instead of full functionality

"Upgrade to access full Advanced Analytics" dialog

Feature gate enforcement

6

Check Custom Reports preview

Custom report builder visible but limited

Report builder with "Preview" banner and upgrade prompts

Preview functionality scope

7

Test API Integrations preview

API integration section shows capabilities but requires upgrade

API documentation visible, setup requires upgrade

Technical preview access

8

Verify Automated Workflows preview

Workflow builder accessible in read-only preview mode

Workflow templates visible, editing requires upgrade

Process preview availability

9

Validate upgrade prompts consistency

All advanced features consistently prompt for upgrade

Uniform "Upgrade to unlock" messaging across features

Consistent user experience

10

Check upgrade pathway integration

Upgrade buttons link to appropriate subscription plans

"Upgrade Now" buttons lead to subscription page

Revenue conversion integration

11

Test preview feature educational value

Previews provide enough information to demonstrate value

Feature descriptions, benefits, sample outputs visible

Trial conversion optimization

Verification Points

  • Primary_Verification: Trial plan displays advanced features as preview-only with clear upgrade prompts for Metro Water Utilities Free plan
  • Secondary_Verifications: Preview mode provides educational value without full functionality, upgrade pathways are consistently presented
  • Negative_Verification: Should not provide full advanced feature access, should not confuse users about feature availability

Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Template for recording actual behavior]
  • Execution_Date: [When test was executed]
  • Executed_By: [Who performed the test]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Evidence references]

Execution Analytics

  • Execution_Frequency: Monthly
  • Maintenance_Effort: Low
  • Automation_Candidate: No

Test Relationships

  • Blocking_Tests: Feature access control setup, Subscription management
  • Blocked_Tests: Full feature functionality tests
  • Parallel_Tests: Other preview mode tests
  • Sequential_Tests: Should follow basic trial functionality validation

Additional Information

  • Notes: Important for trial conversion by demonstrating advanced feature value without providing free access
  • Edge_Cases: Test preview mode with different user roles, feature combinations, browser compatibility
  • Risk_Areas: Too generous previews could reduce upgrade motivation, too restrictive previews could hurt trial conversion
  • Security_Considerations: Preview mode should not expose sensitive data or create security vulnerabilities

Missing Scenarios Identified

  • Scenario_1: Test preview mode behavior during trial-to-paid transitions
  • Type: Plan Migration
  • Rationale: Features should unlock immediately upon subscription upgrade
  • Priority: P2
  • Scenario_2: Validate preview mode educational content accuracy and completeness
  • Type: Content Validation
  • Rationale: Preview content must accurately represent full feature capabilities
  • Priority: P3




API Test Cases (Critical Level ≥7)

API Test Case 1: Dashboard Data Retrieval Performance

Test Case ID: ONB05US01_API_TC_001
Title: Verify GET /api/v1/admin/dashboard returns complete Metro Water Utilities data within 500ms
Priority: P1-Critical
Test Type: API Performance

Endpoint: GET /api/v1/admin/dashboard
Authentication: Bearer token for admin@metrowater.com
Expected Response Time: < 500ms

Test Data:

  • Organization: Metro Water Utilities (75% setup completion)
  • Utility: Electric Services Co (12.38% setup completion)
  • User Metrics: Today's Users: 2, Week Growth: +100%
  • Security Data: 19 authorized logins, 13 unauthorized attempts

Validation Criteria:

  • Response code: 200 OK
  • Response time: < 500ms
  • Data completeness: All dashboard sections included
  • Data accuracy: Matches expected Metro Water Utilities values
  • Schema validation: Response structure matches API specification

API Test Case 2: Organization Progress Calculation API

Test Case ID: ONB05US01_API_TC_002
Title: Verify GET /api/v1/admin/organization/progress calculates weighted progress using business rules
Priority: P1-Critical
Test Type: API Functional

Endpoint: GET /api/v1/admin/organization/progress
Authentication: Bearer token for admin@metrowater.com
Expected Response Time: < 300ms

Test Data:

  • Currency: Complete (40% weight)
  • Date Format: Complete (30% weight)
  • Timezone: Incomplete (30% weight)
  • Expected Result: 70% progress

Validation Criteria:

  • Response code: 200 OK
  • Progress calculation: Exactly 70% based on weighted formula
  • Individual task status: Accurate completion states
  • Calculation performance: < 300ms response time

API Test Case 3: Multi-Utility Aggregation Formula API

Test Case ID: ONB05US01_API_TC_003
Title: Verify GET /api/v1/admin/utilities/progress-aggregate implements complex 6-utility formula
Priority: P1-Critical
Test Type: API Functional

Endpoint: GET /api/v1/admin/utilities/progress-aggregate
Authentication: Bearer token for admin@metrowater.com
Expected Response Time: < 800ms

Test Data:

  • 6 utilities with specific parameter combinations
  • Expected Final Progress: 54.44%
  • Complex aggregation formula validation

Validation Criteria:

  • Response code: 200 OK
  • Aggregation accuracy: Exactly 54.44% result
  • Formula implementation: Correct parameter averaging
  • Performance: < 800ms for complex calculation




Complete Test Execution Summary

Total Test Coverage: 35 Enhanced Test Cases + 3 Critical API Tests

Core Dashboard Functionality (TC_001-010):

  • Organization Setup weighted progress (TC_001, TC_026)
  • Visual status indicators (TC_002)
  • Button state management (TC_003, TC_004)
  • User adoption metrics (TC_005, TC_029)
  • Security monitoring (TC_006, TC_007, TC_030)
  • Subscription display (TC_008, TC_031)
  • Access control (TC_009, TC_033)
  • Real-time updates (TC_010)

Data Upload Features (TC_011-020):

  • File upload functionality with "Go to Data Upload" button
  • Multi-format support (CSV, Excel, XML)
  • Drag-and-drop interface
  • Smart Recognition processing
  • Data Mapping capabilities
  • Smart Validation engine
  • Direct integration workflow
  • Real-time feedback
  • Template management
  • 5GB storage limits (TC_034)

Trial Plan Management (TC_021-025, TC_032-035):

  • Free tier provisioning (TC_021)
  • 2-user concurrent limits (TC_022)
  • 30-day auto-expiration (TC_023)
  • Basic Analytics access (TC_024)
  • Email Support availability (TC_025)
  • 100-record export limits (TC_032)
  • API access restrictions (TC_033)
  • 5GB storage limits (TC_034)
  • Preview-only advanced features (TC_035)

Enhanced Business Logic (TC_026-031):

  • Weighted progress calculations (TC_026)
  • Multi-utility aggregation formula (TC_027)
  • Three-step utility enhancement (TC_028)
  • User behavior tracking events (TC_029)
  • Security alert thresholds (TC_030)
  • Component-based pricing (TC_031)

Browser & Device Compatibility Matrix

Test Category

Chrome

Firefox

Safari

Edge

Desktop

Tablet

Mobile

Core Dashboard (TC_001-010)

Data Upload (TC_011-020)

Trial Features (TC_021-025, TC_032-035)

Enhanced Logic (TC_026-031)

API Tests (API_TC_001-003)

N/A

N/A

Legend: ✓ = Full Support, ○ = Limited/View Only, N/A = Not Applicable

Test Suite Execution Strategy

Smoke Test Suite (Daily - 8 Test Cases):

  • ONB05US01_TC_001 (Organization Progress)
  • ONB05US01_TC_003 (Complete Setup Button)
  • ONB05US01_TC_004 (Continue Setup Button)
  • ONB05US01_TC_006 (Security Activity)
  • ONB05US01_TC_009 (Access Control)
  • ONB05US01_TC_021 (Trial Plan)
  • ONB05US01_API_TC_001 (Dashboard API)
  • ONB05US01_API_TC_002 (Progress Calculation API)

Regression Test Suite (Pre-Release - 20 Test Cases):

  • All P1-Critical and P2-High priority test cases
  • Core business logic validation
  • Integration point testing
  • Security and access control validation

Full Test Suite (Weekly - All 38 Test Cases):

  • Complete test coverage including P3-Medium priority
  • Cross-browser compatibility testing
  • Performance and load validation
  • User experience and accessibility testing

Performance Benchmarks

Component

Target Performance

Critical Threshold

Dashboard Load

< 2 seconds

< 5 seconds

Progress Calculations

< 500ms

< 1 second

API Response Times

< 500ms

< 2 seconds

File Upload Processing

< 5 seconds/MB

< 15 seconds/MB

Real-time Updates

< 30 seconds

< 2 minutes

Multi-Utility Aggregation

< 800ms

< 3 seconds

Integration Dependencies

Critical Dependencies:

  • Organization Setup Service
  • Utility Setup Service
  • User Activity Service
  • Security Logging Service
  • Data Upload Service
  • Subscription Management Service
  • Real-Time Data Pipeline
  • Analytics Engine

External Dependencies:

  • Email/SMS Notification Services
  • File Processing Services
  • Authentication/Authorization Systems
  • Billing and Payment Systems

This comprehensive test suite ensures 100% coverage of all 35 acceptance criteria with enhanced business logic validation, realistic test data consistency, and complete 17 BrowserStack report support for enterprise B2B utility SaaS requirements.