Skip to main content

Utility management (ONB02US06)


1.Coverage Problem StatementSummary

Core Problem

Users lack visibility into the detailed configuration process for utility setup, making it difficult to understand the exact progress and remaining steps.

Pain Points
  • Inability to track specific configuration steps
  • Unclear which steps are completed or pending
  • No clear indication of mandatory vs. optional configuration steps

2. Who Are the Users Facing the Problem?

System Admin

  • Responsible for setting up and managing utility configurations
  • Needs to track progress of multiple utility setups
  • Requires clear visibility into configuration process

3. Jobs To Be Done

For System Admin:

  • When I need to set up a new utility,
  • But I cannot see the specific steps completed in the configuration process,
  • Help me understand the exact progress of each utility setup,
  • So that I can efficiently manage and complete the configuration.

4. Solution

Key Capability Areas
  1. ProgressTotal TrackingCoverage
    • Detailed: step-by-step100% configuration(34 progressTest Cases/17 Acceptance Criteria * 100)
    • VisualTotal indicatorTest forCases: completed34 and(26 pendingFunctional steps+ 5 Performance/Integration + 3 Security)
    • Step completion status

5. Major Steps Involved

  1. Navigate to Setup Dashboard
  2. Select a utility to configure
  3. View detailed configuration steps
  4. Complete each configuration step
  5. Track overall and individual step progress
  6. Receive guidance on remaining steps

6. Flow Diagram

image.png

7. Business Rules

  • All 6 configuration steps must be clearly defined
  • Progress percentage must accurately reflect completed steps
  • Mandatory steps must be clearly distinguished
  • Users cannot complete utility setup without finishing mandatory steps
  • Required Fields:
    • Utility Name (marked with asterisk *)
    • Email (marked with asterisk *)
    • Contact Number (marked with asterisk *)
    • City (marked with asterisk *)
    • Address (marked with asterisk *)
  • Optional Fields:
    • Website URL
    • Logo Upload
  • Field Validations:
    • Utility Name: Must be filled with a valid utility name
    • Email: Must be a valid email format (example shows contacts@example.com)
    • Contact Number: Must follow proper phone number format (example shows (123) 456-7890)
    • City: Must be selected from a dropdown menu
    • Address: Must contain a complete address
    • Website URL: Should follow proper URL format if provided (example shows https://www.example.com)
  • User Actions:
    • "Cancel" button: Likely discards form data and closes the dialog
    • "Save Utility" button: Submits the form data and adds the utility to the system
    • "Click to upload logo" area: Allows users to upload a utility company logo
  • UI Elements:
    • Modal/Dialog box with close (X) button in top-right corner
    • Dropdown selection for City
    • Text input fields for other data
    • File upload mechanism for the logo

8. Sample Data

  • Utility Name: Metropolitan Water District
  • Email: contact@metrowater.com
  • Contact Number: (415) 555-8734
  • City: San Francisco
  • Address: 1234 Reservoir Avenue, San Francisco, CA 94110
  • Website URL: https://www.metrowater.com
  • Logo Upload: [Metropolitan Water District logo file]

9.Total Acceptance Criteria

    : 17
  1. ThePriority systemDistribution: mustP1-Critical display(47%) a+ P2-High (35%) + P3-Medium (18%)
  2. Test Scenario Analysis

    A. Functional Test Scenarios

    • Core Functionality: Setup dashboard, utility configuration, progress tracking
    • Business Rules: Progress calculations, field validations, status indicators
    • User Journeys: Complete utility setup workflow
    • Integration Points: Organization setup dependency, country/state/city dropdown population
    • Data Flow: Utility data creation, progress calculation, status updates

    B. Non-Functional Test Scenarios

    • Performance: Dashboard load times, form submission, progress calculations
    • Security: Form validation, file upload security, data protection
    • Compatibility: Cross-browser, responsive design
    • Usability: Navigation flow, error handling, guidance tooltips
    • Reliability: Data integrity, calculation accuracy, state persistence

    C. Edge Case & Error Scenarios

    • Boundary Conditions: Field character limits, file size limits
    • Invalid Inputs: Malformed emails, invalid phone numbers, unauthorized file types
    • System Failures: Network issues, upload failures
    • Data Inconsistencies: Incomplete configurations, progress calculation edge cases






    Test Cases

    ONB02US06_TC_001

    Title: Verify detailed breakdown of 6 configuration steps display

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_001
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

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

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • 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: 2 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: Low
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Organization setup module
    • Code_Module_Mapped: Setup Dashboard
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Organization setup completed
    • Performance_Baseline: <1s
    • Data_Requirements: Valid organization setup data

    Prerequisites

    • Setup_Requirements: Organization setup completed
    • User_Roles_Permissions: System Admin
    • Test_Data: Valid system admin credentials
    • Prior_Test_Cases: Organization setup completion

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Login as System Admin

    Login successful, dashboard accessible

    Username: admin@test.com, Password: Test123!

    Valid credentials

    2

    Navigate to Setup Dashboard

    Setup Dashboard loads successfully

    N/A

    Check URL routing

    3

    Verify configuration steps display

    System displays exactly 6 configuration steps clearly labeled

    N/A

    Count and verify step names

    4

    Check step breakdown detail

    Each step mustshows havedetailed abreakdown with clear descriptions

    N/A

    Verify readability

    Verification Points

    • Primary_Verification: System displays exactly 6 configuration steps with detailed breakdown
    • Secondary_Verifications: Steps are clearly labeled and organized
    • Negative_Verification: No missing or extra steps beyond 6




    ONB02US06_TC_002

    Title: Verify each step has clear status (Not Started, In Progress, Completed)

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_002
    • UsersCreated mustBy: beSarvesh
    • Created ableDate: toJune 17, 2025
    • Version: 1.0

    Classification

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

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • 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: 3 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: Low
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Progress tracking system
    • Code_Module_Mapped: Progress Tracking
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Setup dashboard access
    • Performance_Baseline: <1s
    • Data_Requirements: Fresh utility setup state

    Prerequisites

    • Setup_Requirements: Clean setup state
    • User_Roles_Permissions: System Admin
    • Test_Data: Various utility completion states
    • Prior_Test_Cases: ONB02US06_TC_001

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access Setup Dashboard with new utility

    All steps show "Not Started" status

    Utility: New Test Utility

    Fresh state

    2

    Complete first configuration step

    First step shows "Completed", others "Not Started"

    Complete basic info

    Status update

    3

    Partially complete second step

    Second step shows "In Progress", first "Completed"

    Partial form data

    Mid-state verification

    4

    Verify status consistency

    Each step accurately reflects its completion state

    N/A

    Cross-validation

    Verification Points

    • Primary_Verification: Each step displays correct status (Not Started, In Progress, Completed)
    • Secondary_Verifications: Status updates reflect actual completion state
    • Negative_Verification: No incorrect status displays




    ONB02US06_TC_003

    Title: Verify users can see which steps are mandatory

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_003
    • TheCreated overallBy: progress percentage must match completed stepsSarvesh
    • UsersCreated shouldDate: receiveJune guidance17, on incomplete steps2025
    • TheVersion: 1.0

    Classification

    • Module/Feature: Setup Dashboard
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Planned-for-Automation

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: Business rules engine
    • Code_Module_Mapped: Step Validation
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Setup dashboard access
    • Performance_Baseline: <1s
    • Data_Requirements: Step configuration data

    Prerequisites

    • Setup_Requirements: Setup dashboard mustaccessible
    • User_Roles_Permissions: beSystem intuitiveAdmin
    • Test_Data: andStep easymandatory/optional toconfiguration
    • Prior_Test_Cases: navigateONB02US06_TC_001

10.Test Process ChangesProcedure

AspectCurrent ProcessNew ProcessImpact

ProgressStep Tracking#

Opaque

Transparent step-by-step

Improved user understanding (+50% clarity)

Step VisibilityAction

Limited

Detailed step status

Enhanced user control (+40% efficiency

11.Expected Impact from Solving This Problem

MetricImprovement

User ConfidenceResult

IncreasedTest by Data

60%Comments

1

Access Setup Dashboard

Dashboard loads with step indicators

N/A

Initial state

2

Review each configuration step

Mandatory steps clearly marked with visual indicators

N/A

Visual distinction

3

Identify optional steps

Optional steps distinguished from mandatory ones

N/A

Clear differentiation

4

Verify mandatory step indicators

All required steps have consistent mandatory marking

N/A

Consistency check

ConfigurationVerification CompletionPoints

  • Primary_Verification: RateMandatory steps are clearly distinguished with visual indicators
  • Secondary_Verifications: Optional steps are clearly marked as non-mandatory
  • Negative_Verification: No ambiguity between mandatory and optional steps




ONB02US06_TC_004

Title: Verify overall progress percentage matches completed steps with formula

Test Case Metadata

  • Test Case ID: ONB02US06_TC_004
  • Created By: Sarvesh
  • Created Date: June 17, 2025
  • Version: 1.0

Classification

  • Module/Feature: Progress Tracking
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

Business Context

  • Customer_Segment: All
  • 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: 5 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Low
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 20%
  • Integration_Points: Progress calculation engine
  • Code_Module_Mapped: Progress Calculator
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Progress calculation service
  • Performance_Baseline: <1s
  • Data_Requirements: Multiple utility completion states

Prerequisites

  • Setup_Requirements: Multiple utilities with different completion states
  • User_Roles_Permissions: System Admin
  • Test_Data: Various utility progress percentages
  • Prior_Test_Cases: ONB02US06_TC_001, ONB02US06_TC_002

Test Procedure

Step #

Improved by Action

35%Expected Result

Test Data

Comments

User Satisfaction1

EnhancedCreate byutility with 0 steps completed

45

12. User Behavior Tracking

MetricEventPurpose

Step Completion Time

ConfigurationProgress Stepshows Completed0% using formula: (0/6)*100 = 0%

UnderstandUtility: stepTest complexityUtility A

Baseline

Abandoned Configurations2

SetupComplete Process3 Abandonedout of 6 steps

IdentifyProgress frictionshows points50% using formula: (3/6)*100 = 50%

Complete: Basic Info, Contact, Address

Mid-progress

Guidance Interaction3

HelpComplete Tooltipall Viewed6 steps

MeasureProgress usershows support100% needusing formula: (6/6)*100 = 100%

Complete all configuration steps

Full completion

4

Verify overall progress calculation

Overall progress = (Sum of individual utilities progress) / (Number of utilities)

Multiple utilities with varying progress

Formula validation

13.Verification WireframePoints

https://orgflow-simplifier.lovable.app/


14. Enhancement In The Latest Release

Setup Dashboard - Business Rules
1.
  • Primary_Verification: Overall Setup Progress
  • Definition: Displays the average setup completionprogress percentage across all configured utilities.
  • Progress Calculation:
    Overall Setup Progress 
  • image.png
  • Status Indicator:
    • If progress is 100%, status = "Complete."
    • If progress is less than 100%, status = "In Progress."
2. Configured Utilities List
  • Utility Display:
    • Each configured utility card must show:
      • Utility Name
      • Description
      • Setup Progress Bar and %
      • Activation Status (Active / Inactive)
      • "Edit" and "Continue Setup" buttons
  • Activation Toggle:
    • Users can activate or deactivate a utility instantly by switching the toggle.
    • No minimum progress % required to activate/deactivate.
  • Progress Visibility:
    • Setup Progress must be displayed as a horizontal progress bar along with a numerical percentage.
3. Add/Edit New Utility Form
  • State:
    • Must select from predefined dropdown options which will come from selected country in organisation setup.
  • City:
    • Must select from predefined dropdown options based on selected State.
  • GST/HST/VAGST Registration:
    • Optional field.
    • If entered, alphanumeric only; max 30 characters.
4. Welcome to your Setup Dashboard
  • Display the hardcode text
    • image.png
UI Rules
  • The Icons should be Same which are outline with background icon
  • The animations should work as same in the given lovable design.

Acceptance criteria

  1. The system must display the average setup completion percentage across all configured utilities
  2. The system must calculate overall setup progress using the formula: (Sum of individual utility progress) / (Number of configured utilities)
  3. TheSecondary_Verifications: Individual utility progress = (Completed steps / Total steps) * 100
  4. Negative_Verification: Progress never exceeds 100% or shows negative values



  5. ONB02US06_TC_005

    Title: Verify users receive guidance on incomplete steps

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_005
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

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

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • 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: 3 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: Low
    • Failure_Impact: High

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: Help system
    • Code_Module_Mapped: Guidance System
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: No
    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Guidance tooltip system
    • Performance_Baseline: <1s
    • Data_Requirements: Incomplete utility configurations

    Prerequisites

    • Setup_Requirements: Utilities with incomplete steps
    • User_Roles_Permissions: System Admin
    • Test_Data: Partially completed utilities
    • Prior_Test_Cases: ONB02US06_TC_002

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access utility with incomplete steps

    System identifies incomplete steps

    Utility with 3/6 steps completed

    Partial completion

    2

    Hover over incomplete step

    Guidance tooltip appears with next actions

    Incomplete step indicator

    Tooltip display

    3

    Click on incomplete step

    Detailed guidance panel opens with step requirements

    Step 4: Logo Upload

    Detailed guidance

    4

    Review guidance content

    Clear instructions provided for completing the step

    N/A

    Content quality

    Verification Points

    • Primary_Verification: Users receive clear guidance on incomplete steps
    • Secondary_Verifications: Guidance includes specific next actions and requirements
    • Negative_Verification: No guidance shown for completed steps




    ONB02US06_TC_006

    Title: Verify configuration dashboard is intuitive and easy to navigate

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_006
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Setup Dashboard
    • Test Type: UI
    • Test Level: System
    • Priority: P2-High
    • Execution Phase: Acceptance
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Acceptance, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, HappyPath

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: UI framework
    • Code_Module_Mapped: Dashboard UI
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: No
    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080, Tablet-1024x768, Mobile-375x667
    • Dependencies: Dashboard framework
    • Performance_Baseline: <1s
    • Data_Requirements: Sample utility data

    Prerequisites

    • Setup_Requirements: Dashboard accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Multiple utilities in different states
    • Prior_Test_Cases: ONB02US06_TC_001

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access setup dashboard

    Dashboard loads with clear layout and organization

    N/A

    Initial impression

    2

    Navigate between different sections

    Smooth transitions, clear navigation paths

    Various dashboard sections

    Navigation flow

    3

    Test responsive design

    Dashboard adapts to different screen sizes

    Desktop, Tablet, Mobile views

    Responsive behavior

    4

    Evaluate overall user experience

    Interface is intuitive, elements are logically placed

    N/A

    UX assessment

    Verification Points

    • Primary_Verification: Dashboard is intuitive and easy to navigate
    • Secondary_Verifications: Clear visual hierarchy, logical element placement
    • Negative_Verification: No confusing navigation patterns or hidden functionality




    ONB02US06_TC_007

    Title: Verify average setup completion percentage display across utilities

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_007
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

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

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • 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: Low
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 20%
    • Integration_Points: Progress calculation service
    • Code_Module_Mapped: Progress Calculator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Progress calculation service
    • Performance_Baseline: <1s
    • Data_Requirements: Multiple utilities with different completion states

    Prerequisites

    • Setup_Requirements: Multiple configured utilities
    • User_Roles_Permissions: System Admin
    • Test_Data: Utilities with varying progress percentages
    • Prior_Test_Cases: ONB02US06_TC_004

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create multiple utilities with different progress

    System tracks individual utility progress

    Utility A: 50%, Utility B: 75%, Utility C: 100%

    Setup state

    2

    Access setup dashboard

    Dashboard displays average setup completion percentage

    N/A

    Dashboard view

    3

    Verify calculation accuracy

    Average = (50% + 75% + 100%) / 3 = 75%

    Three utilities with known progress

    Formula verification

    4

    Add new utility with 0% progress

    Average recalculates to (50% + 75% + 100% + 0%) / 4 = 56.25%

    New utility with no progress

    Dynamic calculation

    Verification Points

    • Primary_Verification: Average setup completion = (Sum of individual utility progress) / (Number of configured utilities)
    • Secondary_Verifications: Percentage updates dynamically when utilities are added/modified
    • Negative_Verification: Calculation handles division by zero and edge cases




    ONB02US06_TC_008

    Title: Verify overall setup progress calculation formula implementation

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_008
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Progress Tracking
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • 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: 6 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: Low
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 25%
    • Integration_Points: Progress calculation engine
    • Code_Module_Mapped: Progress Calculator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Progress calculation service
    • Performance_Baseline: <1s
    • Data_Requirements: Multiple utilities with precise progress values

    Prerequisites

    • Setup_Requirements: Clean system muststate
    • User_Roles_Permissions: showSystem Admin
    • Test_Data: Utilities with calculated progress values
    • Prior_Test_Cases: ONB02US06_TC_007

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create single utility, complete 0 steps

    Individual progress = (0/6)*100 = 0%, Overall = 0%

    Utility: Metropolitan Water District

    Baseline

    2

    Complete 2 steps

    Individual progress = (2/6)*100 = 33.33%, Overall = 33.33%

    Complete: Basic Info, Contact

    Partial progress

    3

    Add second utility, complete 6 steps

    Utility2 progress = (6/6)*100 = 100%, Overall = (33.33+100)/2 = 66.67%

    Second utility fully completed

    Two utilities

    4

    Add third utility, complete 3 steps

    Utility3 progress = (3/6)*100 = 50%, Overall = (33.33+100+50)/3 = 61.11%

    Third utility half completed

    Three utilities

    Verification Points

    • Primary_Verification: Overall Setup Progress = (Sum of individual utility progress) / (Number of configured utilities)
    • Secondary_Verifications: Individual utility progress = (Completed steps / Total steps) * 100
    • Negative_Verification: Formula handles decimal precision and rounding correctly




    ONB02US06_TC_009

    Title: Verify status asshows "Complete" when progress reaches 100%

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_009
    • TheCreated systemBy: mustSarvesh
    • Created showDate: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Status Indicator
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: Status calculation service
    • Code_Module_Mapped: Status Calculator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Status calculation service
    • Performance_Baseline: <1s
    • Data_Requirements: Fully completed utility

    Prerequisites

    • Setup_Requirements: Utility with all steps completable
    • User_Roles_Permissions: System Admin
    • Test_Data: Complete utility configuration data
    • Prior_Test_Cases: ONB02US06_TC_008

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create new utility

    Initial status asshows "In Progress", progress = 0%

    Utility: Metropolitan Water District

    Initial state

    2

    Complete 5 out of 6 steps

    Status remains "In Progress", progress = 83.33%

    Complete all except logo

    Near completion

    3

    Complete final step (6/6)

    Status changes to "Complete", progress = 100%

    Upload logo file

    Full completion

    4

    Verify status consistency

    Status = "Complete" when progress = 100%

    N/A

    Status validation

    Verification Points

    • Primary_Verification: Status shows "Complete" when progress reaches exactly 100%
    • Secondary_Verifications: Status updates immediately upon completion
    • Negative_Verification: Status only shows "Complete" at 100%, not before




    ONB02US06_TC_010

    Title: Verify status shows "In Progress" when progress is less than 100%

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_010
    • TheCreated By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Status Indicator
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: Status calculation service
    • Code_Module_Mapped: Status Calculator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Status calculation service
    • Performance_Baseline: <1s
    • Data_Requirements: Partially completed utilities

    Prerequisites

    • Setup_Requirements: Utilities with various completion states
    • User_Roles_Permissions: System Admin
    • Test_Data: Partial utility configuration data
    • Prior_Test_Cases: ONB02US06_TC_009

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create new utility with 0% progress

    Status shows "In Progress"

    Utility: Metropolitan Water District

    Initial state

    2

    Complete 1 step (16.67% progress)

    Status remains "In Progress"

    Complete: Utility Name

    Low progress

    3

    Complete 3 steps (50% progress)

    Status remains "In Progress"

    Complete: Name, Email, Contact

    Mid progress

    4

    Complete 5 steps (83.33% progress)

    Status remains "In Progress"

    Complete all except logo

    High progress

    Verification Points

    • Primary_Verification: Status shows "In Progress" for any progress < 100%
    • Secondary_Verifications: Status remains consistent across different progress levels
    • Negative_Verification: Status never shows "Complete" until 100% reached




    ONB02US06_TC_011

    Title: Verify utility card displays Name, Description, Progress Bar, and Activation Status

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_011
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Utility Cards
    • Test Type: UI
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Smoke
    • Automation Status: Planned-for-Automation

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Smoke, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Daily-Usage
    • Compliance_Required: No
    • SLA_Related: Yes

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: UI rendering system
    • Code_Module_Mapped: mustUtility displayCard eachComponent
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: UI rendering framework
    • Performance_Baseline: <1s
    • Data_Requirements: Configured utility with complete data

    Prerequisites

    • Setup_Requirements: At least one configured utility
    • User_Roles_Permissions: System Admin
    • Test_Data: Complete utility information
    • Prior_Test_Cases: ONB02US06_TC_007

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access utilities dashboard

    Dashboard displays configured utilities as acards

    N/A

    Card layout

    2

    Verify utility name display

    Card shows "Metropolitan Water District"

    Utility Name: Metropolitan Water District

    Name visibility

    3

    Check description field

    Card displays utility description clearly

    Description: Water supply services

    Description display

    4

    Validate progress bar

    Horizontal progress bar shows with percentage (e.g., 75%)

    Current progress: 75%

    Visual progress

    5

    Check activation status

    Card shows "Active" or "Inactive" status clearly

    Status: Active

    Status indicator

    Verification Points

    • Primary_Verification: Each utility card containing Utilitydisplays Name, Description, Setup Progress Bar with percentage,%, and Activation Status (Active/Inactive)
    • TheSecondary_Verifications: All elements are clearly visible and properly formatted
    • Negative_Verification: No missing or overlapping elements in card layout




    ONB02US06_TC_012

    Title: Verify Edit and Continue Setup buttons functionality

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_012
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Utility Cards
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Planned-for-Automation

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Daily-Usage
    • Compliance_Required: No
    • SLA_Related: Yes

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Form navigation system
    • Code_Module_Mapped: mustButton provideActions
    • Requirement_Coverage: "Edit"Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Form navigation system
    • Performance_Baseline: <1s
    • Data_Requirements: Utilities with different completion states

    Prerequisites

    • Setup_Requirements: Utilities with partial and complete configurations
    • User_Roles_Permissions: System Admin
    • Test_Data: Utility configurations in various states
    • Prior_Test_Cases: ONB02US06_TC_011

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Locate utility card with incomplete setup

    Card displays "Continue Setup" buttonsbutton

    Utility: for50% eachcomplete

    Partial setup

    2

    Click "Continue Setup" button

    System navigates to next incomplete step

    N/A

    Navigation flow

    3

    Locate utility card with complete setup

    Card displays "Edit" button

    Utility: 100% complete

    Complete setup

    4

    Click "Edit" button

    System opens utility edit form

    N/A

    Edit functionality

    5

    Verify button states

    Buttons are enabled and responsive

    N/A

    UI responsiveness

    Verification Points

    • Primary_Verification: Edit and Continue Setup buttons function correctly and navigate appropriately
    • TheSecondary_Verifications: Button states match utility completion status
    • Negative_Verification: Buttons are not disabled or non-functional




    ONB02US06_TC_013

    Title: Verify activation toggle switch functionality

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_013
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Activation Toggle
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Daily-Usage
    • Compliance_Required: No
    • SLA_Related: Yes

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: State management system
    • Code_Module_Mapped: mustToggle allowController
    • Requirement_Coverage: usersComplete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: State management service
    • Performance_Baseline: <1s
    • Data_Requirements: Utility with activation capability

    Prerequisites

    • Setup_Requirements: Configured utility available
    • User_Roles_Permissions: System Admin
    • Test_Data: Utility in active/inactive state
    • Prior_Test_Cases: ONB02US06_TC_011

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Locate utility with "Active" status

    Toggle switch shows "ON" position

    Utility: Metropolitan Water District

    Active state

    2

    Click toggle to activatedeactivate

    Switch ormoves to "OFF", status changes to "Inactive" instantly

    N/A

    Deactivation

    3

    Click toggle to reactivate

    Switch moves to "ON", status changes to "Active" instantly

    N/A

    Reactivation

    4

    Verify state persistence

    Status remains consistent after page refresh

    N/A

    Persistence check

    Verification Points

    • Primary_Verification: Users can activate/deactivate utilities instantly using a toggle switch
    • TheSecondary_Verifications: systemToggle muststate reflects current activation status
    • Negative_Verification: Toggle does not require minimum progress percentage




    ONB02US06_TC_014

    Title: Verify no minimum progress requirement for activation toggle

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_014
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Activation Toggle
    • Test Type: Functional
    • Test Level: System
    • Priority: P2-High
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, Negative

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: Medium
    • Business_Priority: Should-Have
    • Customer_Journey: Daily-Usage
    • Compliance_Required: No
    • SLA_Related: No

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: Business rules engine
    • Code_Module_Mapped: Activation Controller
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: No
    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Business rules service
    • Performance_Baseline: <1s
    • Data_Requirements: New utility with 0% progress

    Prerequisites

    • Setup_Requirements: Utility with minimal configuration
    • User_Roles_Permissions: System Admin
    • Test_Data: Utility with 0% setup progress
    • Prior_Test_Cases: ONB02US06_TC_013

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Create new utility with 0% progress

    Utility created successfully

    Utility: Test Utility Zero Progress

    Minimal setup

    2

    Locate activation toggle

    Toggle switch is available and enabled

    N/A

    Toggle accessibility

    3

    Attempt to activate orutility

    Toggle deactivateswitches to "Active" without restriction

    N/A

    No blocking

    4

    Verify activation success

    Utility status shows "Active" despite 0% progress

    N/A

    Business rule validation

    Verification Points

    • Primary_Verification: Activation toggle works regardless of progress percentage
    • Secondary_Verifications: No minimum progress validation prevents activation
    • Negative_Verification: System does not block activation for incomplete utilities
    • The




    ONB02US06_TC_015

    Title: system must displayVerify setup progress displays as a horizontal progress bar with numerical percentage

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_015
    • TheCreated By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Progress Display
    • Test Type: UI
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Smoke
    • Automation Status: Planned-for-Automation

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Smoke, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, HappyPath

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: UI rendering system
    • Code_Module_Mapped: mustProgress provideBar aComponent
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: UI rendering framework
    • Performance_Baseline: <1s
    • Data_Requirements: Utilities with various progress levels

    Prerequisites

    • Setup_Requirements: Utilities with different completion percentages
    • User_Roles_Permissions: System Admin
    • Test_Data: Progress values at different levels
    • Prior_Test_Cases: ONB02US06_TC_004

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    View utility with 0% progress

    Horizontal progress bar shows empty, displays "0%"

    Utility with 0 completed steps

    Minimum state

    2

    View utility with 50% progress

    Horizontal progress bar shows half-filled, displays "50%"

    Utility with 3/6 completed steps

    Mid-range

    3

    View utility with 100% progress

    Horizontal progress bar shows completely filled, displays "100%"

    Utility with 6/6 completed steps

    Maximum state

    4

    Verify visual consistency

    All progress bars use consistent horizontal layout and styling

    N/A

    Visual standards

    Verification Points

    • Primary_Verification: Setup progress displays as horizontal progress bar with numerical percentage
    • Secondary_Verifications: Progress bar visual accurately represents percentage value
    • Negative_Verification: No vertical or alternative progress indicators used




    ONB02US06_TC_016

    Title: Verify State field with predefined dropdown based on country selection

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_016
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Location Selection
    • Test Type: Functional
    • Test Level: Integration
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-External-Dependency, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Onboarding
    • Compliance_Required: Yes
    • 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: 15%
    • Integration_Points: Organization setup module
    • Code_Module_Mapped: Location Service
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Organization setup service, location data service
    • Performance_Baseline: <1s
    • Data_Requirements: Organization with country selection

    Prerequisites

    • Setup_Requirements: Organization setup with country selected
    • User_Roles_Permissions: System Admin
    • Test_Data: Country selection from organization setup
    • Prior_Test_Cases: Organization setup completion

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access Add/Edit Utility form

    Form loads with State dropdown field

    N/A

    Form availability

    2

    Click State dropdown

    Dropdown shows predefined options based on theorganization's country

    Country: United States

    Country dependency

    3

    Verify state options

    Only states/provinces for selected country appear

    Expected: California, Texas, New York, etc.

    Filtered list

    4

    Select a state

    State selection successful, dropdown closes

    Selected: California

    Selection functionality

    Verification Points

    • Primary_Verification: State field contains predefined dropdown options based on country selected in organisationorganization setup
    • TheSecondary_Verifications: systemState mustoptions provideare afiltered and relevant to organization's country
    • Negative_Verification: States from other countries are not displayed




    ONB02US06_TC_017

    Title: Verify City field with predefined dropdown based on selected State

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_017
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Location Selection
    • Test Type: Functional
    • Test Level: Integration
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-External-Dependency, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Onboarding
    • Compliance_Required: Yes
    • 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: 15%
    • Integration_Points: Location data service
    • Code_Module_Mapped: Location Service
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Location data service, state selection
    • Performance_Baseline: <1s
    • Data_Requirements: State selection dependency

    Prerequisites

    • Setup_Requirements: State selected in utility form
    • User_Roles_Permissions: System Admin
    • Test_Data: State selection (e.g., California)
    • Prior_Test_Cases: ONB02US06_TC_016

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Select state from dropdown

    State selection successful

    Selected State: California

    State dependency

    2

    Click City dropdown

    City dropdown becomes enabled and populated

    N/A

    Cascade activation

    3

    Verify city options

    Cities relevant to selected state appear

    Expected: San Francisco, Los Angeles, San Diego

    Filtered cities

    4

    Select a city

    City selection successful

    Selected City: San Francisco

    Selection complete

    Verification Points

    • Primary_Verification: City field provides predefined dropdown options based on theselected State
    • Secondary_Verifications: City options are filtered and relevant to selected Statestate
    • TheNegative_Verification: systemCities mustfrom provideother anstates are not displayed




    ONB02US06_TC_018

    Title: Verify required fields validation with asterisk marking

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_018
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Form Validation
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Negative

    Business Context

    • Customer_Segment: All
    • 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: 5 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: High
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 20%
    • Integration_Points: Form validation service
    • Code_Module_Mapped: Form Validator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: QA
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Form validation service
    • Performance_Baseline: <1s
    • Data_Requirements: Form validation rules

    Prerequisites

    • Setup_Requirements: Add/Edit Utility form accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Required field validation scenarios
    • Prior_Test_Cases: ONB02US06_TC_016

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access Add Utility form

    Form displays with required fields marked with asterisk (*)

    N/A

    Visual indicators

    2

    Verify required field marking

    Utility Name*, Email*, Contact Number*, City*, Address* show asterisk

    Required fields list

    Field identification

    3

    Submit form with empty required fields

    Validation errors appear for all required fields

    Leave required fields empty

    Validation trigger

    4

    Fill one required field, submit

    Validation errors appear for remaining empty required fields

    Fill only Utility Name: Metropolitan Water District

    Partial validation

    Verification Points

    • Primary_Verification: Required fields (Utility Name, Email, Contact Number, City, Address) are marked with asterisk *
    • Secondary_Verifications: Form validation prevents submission without required fields
    • Negative_Verification: Optional fields do not show asterisk marking




    ONB02US06_TC_019

    Title: Verify optional GST/HST/VAGSTfields Registrationfunctionality (Website URL, Logo Upload)

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_019

    • Created By: Sarvesh

    • Created Date: June 17, 2025

    • Version: 1.0

    Classification

    • Module/Feature: Form Validation

    • Test Type: Functional

    • Test Level: System

    • Priority: P2-High

    • Execution Phase: Regression

    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All

    • Revenue_Impact: Medium

    • 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: Low

    • Failure_Impact: Medium

    Coverage Tracking

    • Feature_Coverage: 10%

    • Integration_Points: File upload service

    • Code_Module_Mapped: Optional Fields Handler

    • Requirement_Coverage: Complete

    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: QA

    • Report_Categories: Quality-Dashboard, Module-Coverage

    • Trend_Tracking: Yes

    • Executive_Visibility: No

    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging

    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest

    • Device/OS: Windows 10/11, macOS 12+

    • Screen_Resolution: Desktop-1920x1080

    • Dependencies: File upload service

    • Performance_Baseline: <1s

    • Data_Requirements: Optional field test data

    Prerequisites

    • Setup_Requirements: Add/Edit Utility form accessible

    • The

      User_Roles_Permissions: systemSystem mustAdmin

    • Test_Data: Optional field values and files

    • Prior_Test_Cases: ONB02US06_TC_018

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access Add Utility form

    Form displays optional fields without asterisk marking

    N/A

    Optional field identification

    2

    Submit form with only required fields filled

    Form submission successful without optional fields

    Required fields: Name: Metropolitan Water District, Email: contact@metrowater.com, Contact: (415) 555-8734, City: San Francisco, Address: 1234 Reservoir Avenue

    Successful submission

    3

    Add optional Website URL

    URL field accepts valid format

    Website URL: https://www.metrowater.com

    URL validation

    4

    Upload optional logo

    File upload successful with supported formats

    Logo file: PNG/JPG format

    File upload

    Verification Points

    • Primary_Verification: Optional fields (Website URL, Logo Upload) do not prevent form submission when empty

    • Secondary_Verifications: Optional fields accept onlyvalid alphanumericdata characterswhen provided

    • Negative_Verification: Form does not require optional fields for GST/HST/VAGSTcompletion




    ONB02US06_TC_020

    Title: RegistrationVerify field validation rules implementation

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_020
    • TheCreated systemBy: mustSarvesh
    • Created limitDate: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Form Validation
    • Test Type: Functional
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Negative

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 25%
    • Integration_Points: Validation service
    • Code_Module_Mapped: Field Validator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: QA
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Validation service
    • Performance_Baseline: <1s
    • Data_Requirements: Valid and invalid test data

    Prerequisites

    • Setup_Requirements: Form validation rules configured
    • User_Roles_Permissions: System Admin
    • Test_Data: Valid and invalid field data
    • Prior_Test_Cases: ONB02US06_TC_018

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Enter invalid email format

    Validation error: "Invalid email format"

    Email: invalid-email

    Email validation

    2

    Enter valid email format

    No validation error, field accepts input

    Email: contact@metrowater.com

    Valid email

    3

    Enter invalid phone format

    Validation error: "Invalid phone format"

    Phone: 123abc

    Phone validation

    4

    Enter valid phone format

    No validation error, field accepts input

    Phone: (415) 555-8734

    Valid phone

    5

    Enter invalid URL format

    Validation error: "Invalid URL format"

    URL: invalid-url

    URL validation

    6

    Enter valid URL format

    No validation error, field accepts input

    URL: https://www.metrowater.com

    Valid URL

    Verification Points

    • Primary_Verification: Field validations enforce proper formats for Email, Contact Number, Website URL
    • Secondary_Verifications: Error messages are clear and helpful
    • Negative_Verification: Invalid data is rejected with appropriate error messages




    ONB02US06_TC_021

    Title: Verify GST/HST/VAGST Registration field functionality

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_021
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Tax Registration
    • Test Type: Functional
    • Test Level: System
    • Priority: P2-High
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, HappyPath

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Tax validation service
    • Code_Module_Mapped: Tax Field Handler
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: QA
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: No
    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Tax validation service
    • Performance_Baseline: <1s
    • Data_Requirements: Tax registration test data

    Prerequisites

    • Setup_Requirements: Add/Edit Utility form accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Various tax registration formats
    • Prior_Test_Cases: ONB02US06_TC_019

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Locate GST/HST/VAGST Registration field

    Field is present and marked as optional

    N/A

    Field presence

    2

    Enter alphanumeric value within limit

    Field accepts valid alphanumeric input

    GST: ABC123DEF456

    Valid input

    3

    Enter 30-character alphanumeric value

    Field accepts maximum length input

    GST: ABCDEFGHIJ1234567890KLMNOPQRST

    Max length

    4

    Attempt to maximumenter 31+ characters

    Field restricts input to 30 characters maximum

    GST: ABCDEFGHIJ1234567890KLMNOPQRSTU+

    Length restriction

    5

    Enter special characters

    Field rejects special characters, shows validation error

    GST: ABC@123#DEF

    Invalid characters

    Verification Points

    • Primary_Verification: GST/HST/VAGST Registration field accepts alphanumeric only, max 30 characters
    • TheSecondary_Verifications: Field is optional and doesn't prevent form submission when empty
    • Negative_Verification: Field rejects special characters and enforces character limit




    ONB02US06_TC_022

    Title: Verify hardcoded welcome text display

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_022
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Welcome Message
    • Test Type: UI
    • Test Level: System
    • Priority: P3-Medium
    • Execution Phase: Acceptance
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P3-Medium, Phase-Acceptance, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium, Revenue-Impact-Low, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: Low
    • Business_Priority: Could-Have
    • Customer_Journey: Onboarding
    • Compliance_Required: No
    • SLA_Related: No

    Quality Metrics

    • Risk_Level: Low
    • Complexity_Level: Low
    • Expected_Execution_Time: 1 minute
    • Reproducibility_Score: High
    • Data_Sensitivity: None
    • Failure_Impact: Low

    Coverage Tracking

    • Feature_Coverage: 5%
    • Integration_Points: Content management system
    • Code_Module_Mapped: Welcome Text Component
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: No
    • Executive_Visibility: No
    • Customer_Impact_Level: Low

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Content rendering system
    • Performance_Baseline: <1s
    • Data_Requirements: Hardcoded text content

    Prerequisites

    • Setup_Requirements: Setup dashboard accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Expected welcome text content
    • Prior_Test_Cases: ONB02US06_TC_001

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Access Setup Dashboard

    Dashboard loads successfully

    N/A

    Initial access

    2

    Locate welcome message area

    "Welcome to your Setup Dashboard" text is displayed prominently

    Expected text: "Welcome to your Setup Dashboard"

    Text presence

    3

    Verify text formatting

    Text is properly formatted and readable

    N/A

    Visual presentation

    4

    Check text consistency

    Same welcome text appears consistently across sessions

    N/A

    Consistency check

    Verification Points

    • Primary_Verification: Hardcoded welcome text "Welcome to your Setup Dashboard" is displayed
    • Secondary_Verifications: Text is properly formatted and positioned
    • Negative_Verification: No dynamic or variable text elements in welcome message




    ONB02US06_TC_023

    Title: Verify outline icons with background consistency

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_023
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: UI Design
    • Test Type: UI
    • Test Level: System
    • Priority: P3-Medium
    • Execution Phase: Acceptance
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P3-Medium, Phase-Acceptance, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium, Revenue-Impact-Low, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: Low
    • Business_Priority: Could-Have
    • Customer_Journey: Onboarding
    • Compliance_Required: No
    • SLA_Related: No

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 5%
    • Integration_Points: Design system
    • Code_Module_Mapped: Icon Component
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: No
    • Executive_Visibility: No
    • Customer_Impact_Level: Low

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Design system must display the hardcoded text as given in business rulecomponents
    • ThePerformance_Baseline: system<1s
    • Data_Requirements: mustIcon design specifications

    Prerequisites

    • Setup_Requirements: Dashboard with icons accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Design guidelines reference
    • Prior_Test_Cases: ONB02US06_TC_006

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Review dashboard icons

    All icons use outline iconsstyle with background

    N/A

    Icon style verification

    2

    Check icon consistency

    Icons maintain consistent outline and background design

    N/A

    Design consistency

    3

    Verify design guidelines compliance

    Icons match specified design system standards

    Reference: Lovable design

    Design compliance

    4

    Test different icon states

    Icons maintain style across hover, active, and default states

    N/A

    State consistency

    Verification Points

    • Primary_Verification: Icons use outline style with background consistent with design guidelines
    • TheSecondary_Verifications: systemIcon mustdesign implementis consistent across all dashboard elements
    • Negative_Verification: No filled or inconsistent icon styles present




    ONB02US06_TC_024

    Title: Verify animations matching the providedmatch design specifications

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_024
  • Created By: Sarvesh
  • Created Date: June 17, 2025
  • Version: 1.0
  • Classification

    • Module/Feature: UI Animations
    • Test Type: UI
    • Test Level: System
    • Priority: P3-Medium
    • Execution Phase: Acceptance
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P3-Medium, Phase-Acceptance, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium, Revenue-Impact-Low, Integration-End-to-End, HappyPath

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: Low
    • Business_Priority: Could-Have
    • Customer_Journey: Onboarding
    • Compliance_Required: No
    • SLA_Related: No

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 5%
    • Integration_Points: Animation framework
    • Code_Module_Mapped: Animation Controller
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Product
    • Report_Categories: Quality-Dashboard, Module-Coverage
    • Trend_Tracking: No
    • Executive_Visibility: No
    • Customer_Impact_Level: Low

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Animation framework
    • Performance_Baseline: <1s
    • Data_Requirements: Animation specifications

    Prerequisites

    • Setup_Requirements: Dashboard with animations accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Animation design reference
    • Prior_Test_Cases: ONB02US06_TC_006

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Navigate through dashboard sections

    Page transitions animate smoothly

    N/A

    Transition animations

    2

    Interact with buttons and controls

    Hover and click animations work as designed

    N/A

    Interactive animations

    3

    Compare with design reference

    Animations match specifications from Lovable design

    Reference: Lovable design animations

    Design compliance

    4

    Test animation performance

    Animations run smoothly without lag or stuttering

    N/A

    Performance validation

    Verification Points

    • Primary_Verification: Animations work as specified in the Lovable design reference
    • Secondary_Verifications: Animations are smooth and enhance user experience
    • Negative_Verification: No broken, missing, or jarring animation effects




    WireframePerformance & Integration Test Cases

    ONB02US06_TC_025

    https://docs.google.com/presentation/d/1errs1E2ZCPORWhFyuNlNWVKYQ6oh6rBb8caMeR0oR2g/edit?usp=sharingTitle: Verify dashboard loading performance under 1 second

    https:Test Case Metadata

    • Test Case ID: ONB02US06_TC_025
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Performance
    • Test Type: Performance
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Performance
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Performance

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Daily-Usage
    • Compliance_Required: No
    • SLA_Related: Yes

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 20%
    • Integration_Points: Performance monitoring system
    • Code_Module_Mapped: Dashboard Loader
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Quality-Dashboard, Performance-Metrics
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Performance monitoring tools
    • Performance_Baseline: <1s
    • Data_Requirements: Multiple utilities for load testing

    Prerequisites

    • Setup_Requirements: Performance monitoring enabled
    • User_Roles_Permissions: System Admin
    • Test_Data: Multiple utilities with varying completion states
    • Prior_Test_Cases: ONB02US06_TC_001

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Clear browser cache

    Cache cleared successfully

    N/A

    Clean state

    2

    Navigate to Setup Dashboard

    Dashboard loads in <1 second

    N/A

    Performance measurement

    3

    Measure load time with 10 utilities

    Dashboard loads in <1 second with multiple utilities

    10 utilities with varying progress

    Load testing

    4

    Test with network throttling

    Dashboard loads acceptably under slow connections

    Simulate 3G connection

    Network performance

    Verification Points

    • Primary_Verification: Dashboard loading time < 1 second under normal conditions
    • Secondary_Verifications: Performance maintained with multiple utilities
    • Negative_Verification: No performance degradation with data volume




    ONB02US06_TC_026

    Title: Verify utility creation/editing performance under 1 second

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_026
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Performance
    • Test Type: Performance
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Performance
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Performance

    Business Context

    • Customer_Segment: All
    • 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: 15%
    • Integration_Points: Database performance
    • Code_Module_Mapped: Utility CRUD Operations
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Quality-Dashboard, Performance-Metrics
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Database performance monitoring
    • Performance_Baseline: <1s
    • Data_Requirements: Utility form data

    Prerequisites

    • Setup_Requirements: Database performance monitoring enabled
    • User_Roles_Permissions: System Admin
    • Test_Data: Complete utility form data
    • Prior_Test_Cases: ONB02US06_TC_025

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Fill utility creation form completely

    Form accepts all data

    Utility Name: Metropolitan Water District, Email: contact@metrowater.com, Contact: (415) 555-8734, City: San Francisco, Address: 1234 Reservoir Avenue

    Complete data

    2

    Submit new utility creation

    Utility created and saved in <1 second

    N/A

    Creation performance

    3

    Edit existing utility

    Form loads existing data in <1 second

    N/A

    Edit performance

    4

    Save utility modifications

    Changes saved in <1 second

    Modified data

    Save performance

    Verification Points

    • Primary_Verification: Utility creation/editing operations complete in <1 second
    • Secondary_Verifications: Form responsiveness maintained during operations
    • Negative_Verification: No timeout or delay issues during CRUD operations




    ONB02US06_TC_027

    Title: Verify progress calculation performance under 1 second

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_027
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Performance
    • Test Type: Performance
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Performance
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Performance

    Business Context

    • Customer_Segment: All
    • 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: Low
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Calculation engine performance
    • Code_Module_Mapped: Progress Calculator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Quality-Dashboard, Performance-Metrics
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Calculation engine monitoring
    • Performance_Baseline: <1s
    • Data_Requirements: Multiple utilities for calculation testing

    Prerequisites

    • Setup_Requirements: Multiple utilities with different progress states
    • User_Roles_Permissions: System Admin
    • Test_Data: 50+ utilities with varying progress
    • Prior_Test_Cases: ONB02US06_TC_008

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Complete a configuration step

    Individual progress recalculates in <1 second using formula: (completed steps / total steps) * 100

    Complete step 3 of 6

    Individual calculation

    2

    View overall progress dashboard

    Overall progress calculation displays in <1 second using formula: (Sum of all utility progress) /preview- (Number of utilities)

    50 utilities with different progress

    Bulk calculation

    3

    Add new utility

    Progress recalculation with new utility in <1 second

    Add 51st utility

    Dynamic calculation

    4

    Delete utility

    Progress recalculation after deletion in <1 second

    Remove one utility

    Deletion calculation

    Verification Points

    • Primary_Verification: Progress calculations (individual and overall) complete in <1 second
    • Secondary_Verifications: Real-time calculation updates without lag
    • Negative_Verification: No calculation delays with large datasets




    ONB02US06_TC_028

    Title: Verify file upload performance under 1 second

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_028
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Performance
    • Test Type: Performance
    • Test Level: Integration
    • Priority: P2-High
    • Execution Phase: Performance
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-External-Dependency, Performance

    Business Context

    • Customer_Segment: All
    • 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: 3 minutes
    • Reproducibility_Score: Medium
    • Data_Sensitivity: Low
    • Failure_Impact: Medium

    Coverage Tracking

    • Feature_Coverage: 10%
    • Integration_Points: File upload service
    • Code_Module_Mapped: File Upload Handler
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

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

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: File upload service
    • Performance_Baseline: <1s
    • Data_Requirements: Test logo files

    Prerequisites

    • Setup_Requirements: File upload functionality accessible
    • User_Roles_Permissions: System Admin
    • Test_Data: Various logo file sizes and formats
    • Prior_Test_Cases: ONB02US06_TC_019

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Upload small logo file (50KB)

    File uploads and processes in <1 second

    PNG file, 50KB

    Small file

    2

    Upload medium logo file (200KB)

    File uploads and processes in <1 second

    JPG file, 200KB

    Medium file

    3

    Upload large logo file (500KB)

    File uploads within acceptable time

    PNG file, 500KB

    Large file

    4

    Test upload progress indicator

    Progress indicator updates smoothly

    Various file sizes

    User feedback

    Verification Points

    • Primary_Verification: Logo file uploads complete in <1 second for typical file sizes
    • Secondary_Verifications: Upload progress provides adequate user feedback
    • Negative_Verification: No upload failures or timeouts for supported file sizes




    ONB02US06_TC_029

    Title: Verify API endpoints for utility CRUD operations

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_029
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: API Integration
    • Test Type: API
    • Test Level: Integration
    • Priority: P1-Critical
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Regression, Type-API, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-External-Dependency, API

    Business Context

    • Customer_Segment: All
    • 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: 6 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: High
    • Failure_Impact: Critical

    Coverage Tracking

    • Feature_Coverage: 25%
    • Integration_Points: Backend API services
    • Code_Module_Mapped: Utility API Controller
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Quality-Dashboard, API-Coverage
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Backend API services
    • Performance_Baseline: <1s
    • Data_Requirements: API test data sets

    Prerequisites

    • Setup_Requirements: API endpoints accessible
    • User_Roles_Permissions: System Admin API access
    • Test_Data: Complete utility data payloads
    • Prior_Test_Cases: ONB02US06_TC_026

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    POST /api/utilities (Create)

    API returns 201 Created with utility object

    {"name": "Metropolitan Water District", "email": "contact@metrowater.com", "phone": "(415) 555-8734", "city": "San Francisco", "address": "1234 Reservoir Avenue"}

    Create operation

    2

    GET /api/utilities/:id (Read)

    API returns 200 OK with utility details

    Utility ID from step 1

    Read operation

    3

    PUT /api/utilities/:id (Update)

    API returns 200 OK with updated utility

    {"email": "updated@metrowater.com"}

    Update operation

    4

    DELETE /api/utilities/:id (Delete)

    API returns 204 No Content

    Utility ID from step 1

    Delete operation

    Verification Points

    • Primary_Verification: All CRUD API operations return correct HTTP status codes and data
    • Secondary_Verifications: API responses include proper data validation and error handling
    • Negative_Verification: Invalid requests return appropriate error codes (400, 404, 422)




    Security Test Cases

    ONB02US06_TC_030

    Title: Verify input validation prevents injection attacks

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_030
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

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

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Security

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 20%
    • Integration_Points: Security validation service
    • Code_Module_Mapped: Input Validator
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Security-Dashboard, Quality-Dashboard
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Security validation service
    • Performance_Baseline: <1s
    • Data_Requirements: Malicious input test cases

    Prerequisites

    • Setup_Requirements: Security validation enabled
    • User_Roles_Permissions: System Admin
    • Test_Data: SQL injection and XSS attack vectors
    • Prior_Test_Cases: ONB02US06_TC_020

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Enter SQL injection in utility name

    Input rejected, validation error displayed

    Name: '; DROP TABLE utilities; -coresetting-updated.lovable.app/-

    SQL injection attempt

    2

    Enter XSS script in description

    Script sanitized or rejected

    Description: <script>alert('XSS')</script>

    XSS attempt

    3

    Enter malicious file upload

    File rejected with appropriate error

    File: malicious.exe

    File security

    4

    Test CSRF protection

    Form submission requires valid CSRF token

    Invalid CSRF token

    CSRF protection

    Verification Points

    • Primary_Verification: All malicious inputs are properly validated and rejected
    • Secondary_Verifications: Error messages don't reveal system information
    • Negative_Verification: No successful injection or script execution




    ONB02US06_TC_031

    Title: Verify file upload security restrictions

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_031
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Security
    • Test Type: Security
    • Test Level: System
    • Priority: P1-Critical
    • Execution Phase: Security
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Security

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: File security service
    • Code_Module_Mapped: File Upload Security
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Security-Dashboard, Quality-Dashboard
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: File security scanning service
    • Performance_Baseline: <1s
    • Data_Requirements: Various file types for testing

    Prerequisites

    • Setup_Requirements: File upload security enabled
    • User_Roles_Permissions: System Admin
    • Test_Data: Malicious and valid file samples
    • Prior_Test_Cases: ONB02US06_TC_030

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Upload executable file

    File rejected with security error

    File: test.exe

    Executable rejection

    2

    Upload oversized image

    File rejected due to size limit

    File: 10MB image

    Size limitation

    3

    Upload valid image formats

    Files accepted successfully

    Files: PNG, JPG, GIF

    Valid formats

    4

    Test file content validation

    Files scanned for malicious content

    File with embedded script

    Content security

    Verification Points

    • Primary_Verification: Only safe file types (PNG, JPG, GIF) are accepted for logo upload
    • Secondary_Verifications: File size limits are enforced
    • Negative_Verification: Executable files and malicious content are blocked




    ONB02US06_TC_032

    Title: Verify user authorization and access control

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_032
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

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

    Enhanced Tags Tags: MOD-ONB, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Security

    Business Context

    • Customer_Segment: All
    • Revenue_Impact: High
    • Business_Priority: Must-Have
    • Customer_Journey: Daily-Usage
    • 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: 15%
    • Integration_Points: Authentication service
    • Code_Module_Mapped: Access Control
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: Engineering
    • Report_Categories: Security-Dashboard, Quality-Dashboard
    • Trend_Tracking: Yes
    • Executive_Visibility: Yes
    • Customer_Impact_Level: High

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Authentication and authorization service
    • Performance_Baseline: <1s
    • Data_Requirements: Different user role accounts

    Prerequisites

    • Setup_Requirements: Multiple user roles configured
    • User_Roles_Permissions: System Admin, Regular User accounts
    • Test_Data: User credentials for different roles
    • Prior_Test_Cases: ONB02US06_TC_031

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Login as System Admin

    Access granted to utility management features

    Admin credentials

    Admin access

    2

    Access utility creation form

    Form accessible and functional

    N/A

    Admin permissions

    3

    Login as Regular User

    Limited access to utility features

    User credentials

    User access

    4

    Attempt utility creation as Regular User

    Access denied or restricted functionality

    N/A

    Permission enforcement

    Verification Points

    • Primary_Verification: System Admin role has full access to utility management features
    • Secondary_Verifications: Access control is properly enforced based on user roles
    • Negative_Verification: Unauthorized users cannot access restricted functionality




    Edge Cases & Error Scenarios

    ONB02US06_TC_033

    Title: Verify system behavior with maximum character limits

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_033
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Edge Cases
    • Test Type: Functional
    • Test Level: System
    • Priority: P2-High
    • Execution Phase: Regression
    • Automation Status: Automated

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, Negative

    Business Context

    • Customer_Segment: All
    • 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: 4 minutes
    • Reproducibility_Score: High
    • Data_Sensitivity: Medium
    • Failure_Impact: Medium

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Validation service
    • Code_Module_Mapped: Input Validation
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: QA
    • Report_Categories: Quality-Dashboard, Edge-Cases
    • Trend_Tracking: Yes
    • Executive_Visibility: No
    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Validation service
    • Performance_Baseline: <1s
    • Data_Requirements: Maximum length test strings

    Prerequisites

    • Setup_Requirements: Form validation enabled
    • User_Roles_Permissions: System Admin
    • Test_Data: Maximum length test strings
    • Prior_Test_Cases: ONB02US06_TC_021

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Enter maximum allowed characters in Utility Name

    Field accepts input at character limit

    255 character string

    Max length test

    2

    Attempt to exceed character limit in Utility Name

    Field restricts input beyond limit

    256+ character string

    Overflow prevention

    3

    Enter exactly 30 characters in GST field

    Field accepts maximum length

    ABCDEFGHIJ1234567890KLMNOPQRST

    GST max length

    4

    Test boundary conditions for all fields

    All fields handle max length appropriately

    Various max length strings

    Boundary testing

    Verification Points

    • Primary_Verification: All fields properly enforce maximum character limits
    • Secondary_Verifications: User receives clear feedback when limits are reached
    • Negative_Verification: No data truncation or corruption at boundary conditions




    ONB02US06_TC_034

    Title: Verify system handling of network connectivity issues

    Test Case Metadata

    • Test Case ID: ONB02US06_TC_034
    • Created By: Sarvesh
    • Created Date: June 17, 2025
    • Version: 1.0

    Classification

    • Module/Feature: Error Handling
    • Test Type: Functional
    • Test Level: System
    • Priority: P2-High
    • Execution Phase: Regression
    • Automation Status: Manual

    Enhanced Tags Tags: MOD-ONB, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-End-to-End, Negative

    Business Context

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

    Quality Metrics

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

    Coverage Tracking

    • Feature_Coverage: 15%
    • Integration_Points: Network error handling
    • Code_Module_Mapped: Error Handler
    • Requirement_Coverage: Complete
    • Cross_Platform_Support: Web

    Stakeholder Reporting

    • Primary_Stakeholder: QA
    • Report_Categories: Quality-Dashboard, Error-Handling
    • Trend_Tracking: Yes
    • Executive_Visibility: No
    • Customer_Impact_Level: Medium

    Requirements Traceability

    Test Environment

    • Environment: Staging
    • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
    • Device/OS: Windows 10/11, macOS 12+
    • Screen_Resolution: Desktop-1920x1080
    • Dependencies: Network simulation tools
    • Performance_Baseline: N/A
    • Data_Requirements: Network connectivity scenarios

    Prerequisites

    • Setup_Requirements: Network simulation capability
    • User_Roles_Permissions: System Admin
    • Test_Data: Form data for testing
    • Prior_Test_Cases: ONB02US06_TC_025

    Test Procedure

    Step #

    Action

    Expected Result

    Test Data

    Comments

    1

    Simulate network disconnection during form submission

    Graceful error handling with retry option

    Complete utility form data: Name: Metropolitan Water District, Email: contact@metrowater.com

    Network failure

    2

    Test slow network conditions

    Loading indicators and timeout handling

    N/A

    Performance degradation

    3

    Simulate server unavailability

    Appropriate error message displayed

    N/A

    Server error

    4

    Test automatic retry mechanisms

    System attempts to reconnect and retry

    N/A

    Recovery testing

    Verification Points

    • Primary_Verification: System handles network issues gracefully with appropriate user feedback
    • Secondary_Verifications: Data is not lost during network interruptions
    • Negative_Verification: No system crashes or data corruption during network issues




    Test Suite Definitions

    Smoke Test Suite

    Execution Criteria: P1 priority, basic functionality validation
     Test Cases: ONB02US06_TC_001, ONB02US06_TC_002, ONB02US06_TC_006, ONB02US06_TC_011, ONB02US06_TC_015
     Execution Frequency: Every build deployment
     Expected Duration: 15 minutes

    Regression Test Suite

    Execution Criteria: P1-P2 priority, automated tests
     Test Cases: All functional test cases (TC_001 through TC_024)
     Execution Frequency: Before each release
     Expected Duration: 2 hours

    Performance Test Suite

    Execution Criteria: Performance-critical operations
     Test Cases: ONB02US06_TC_025, ONB02US06_TC_026, ONB02US06_TC_027, ONB02US06_TC_028
     Execution Frequency: Weekly performance testing
     Expected Duration: 30 minutes

    Security Test Suite

    Execution Criteria: Security-critical validations
     Test Cases: ONB02US06_TC_030, ONB02US06_TC_031, ONB02US06_TC_032
     Execution Frequency: Before major releases
     Expected Duration: 45 minutes

    API Test Suite

    Execution Criteria: API integration validation
     Test Cases: ONB02US06_TC_029
     Execution Frequency: Continuous integration
     Expected Duration: 10 minutes

    Full Test Suite

    Execution Criteria: Complete feature coverage
     Test Cases: All 34 test cases
     Execution Frequency: Major release cycles
     Expected Duration: 4 hours




    Execution Matrix

    Browser/Device Coverage

    Test Case Category

    Chrome 115+

    Firefox 110+

    Safari 16+

    Edge Latest

    Mobile

    Smoke Tests

    Functional Tests

    Selected

    Performance Tests

    Security Tests

    API Tests

    Environment Coverage

    • Development: Smoke tests only
    • Staging: Full test suite
    • Production: Smoke tests + selected regression tests




    Dependency Map

    Test Execution Dependencies

    1. Organization Setup → ONB02US06_TC_016, ONB02US06_TC_017
    2. Basic Dashboard Access → ONB02US06_TC_001 → All subsequent tests
    3. Progress Calculation → ONB02US06_TC_004 → ONB02US06_TC_007, ONB02US06_TC_008
    4. Form Validation → ONB02US06_TC_018 → ONB02US06_TC_019, ONB02US06_TC_020

    External System Dependencies

    • Organization Setup Module: Required for country/state/city dropdowns
    • Authentication Service: Required for user access control
    • File Upload Service: Required for logo upload functionality
    • Location Data Service: Required for state/city dropdown population