New Connection Configuration (CIS01US16)
Total test cases - 15
Total Acceptance criteria- 15
Total Coverage -100%
Test Scenario Summary
This document provides comprehensive test scenarios and detailed test cases for the New Connection Configuration feature, ensuring complete coverage of all 15 acceptance criteria and supporting all 17 BrowserStack test management reports.
Test Case 1: Access New Connection Configuration
Test Case ID: CIS01US16_TC_001
Title: Verify authorized System Administrator can access New Connection Configuration through Settings → New Connection tab
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: Integration
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, UI, Database, MOD-Settings, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Module-Coverage, Report-Smoke-Test-Results, Report-User-Acceptance, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Settings-Module, Settings-Access-Control
Business Context
Customer_Segment: Enterprise/SMB/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: 2 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: Critical
Coverage Tracking
Feature_Coverage: 100% of access functionality
Integration_Points: Settings Module, User Authentication, Role-based Access
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Engineering
Report_Categories: Quality-Dashboard, Module-Coverage, Smoke-Test-Results, User-Acceptance, Engineering
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High
Requirements Traceability
Related_Requirements: AC1 - System access authorization, Problem Statement - System Administrator role requirements, User Story Section 5 - System Administrator Flow Step 1
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_011 (Unauthorized Access Prevention)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: User authentication system, Settings module, Role-based permissions
Performance_Baseline: Page load within 3 seconds
Data_Requirements: Valid System Administrator credentials
Prerequisites
Setup_Requirements: System Administrator role configured with New Connection Configuration permissions
User_Roles_Permissions: System Administrator access level
Test_Data: Admin credentials: admin@waterutil.com / Admin123!, WaterUtil utility company context
Prior_Test_Cases: User login functionality validation
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Launch Chrome browser and navigate to WaterUtil application URL | WaterUtil login page displays with company branding and login form | https://app.waterutil.complatform-staging.bynry.com/ | Verify WaterUtil logo and branding elements |
2 | Enter System Administrator credentials in Username and Password fields | Credentials accepted, login button enabled | admin@waterutil.com / Admin123! | Verify password masking |
3 | Click "Sign In" button | Login successful, WaterUtil Dashboard displays with navigation menu |
| Verify dashboard loads within 3 seconds |
4 | Locate "Settings" menu item in left navigation panel | Settings menu visible with gear icon, clickable state |
| Settings should be prominently displayed |
5 | Click on "Settings" menu item | Settings page opens displaying available configuration tabs |
| Page title shows "Settings" with WaterUtil branding |
6 | Verify "New Connection" tab is visible in settings tabs | New Connection tab displayed with connection icon, positioned as first tab |
| Tab should be highlighted or distinctive |
7 | Click on "New Connection" tab | New Connection Configuration page loads with three main sections visible |
| Response Time, Address Display, Document Types sections |
8 | Verify page header and description | Header shows "New Connection Configuration" with descriptive subtitle |
| Subtitle: "Manage and configure system-wide settings..." |
Verification Points
Primary_Verification: System Administrator successfully accesses New Connection Configuration page through Settings → New Connection navigation path
Secondary_Verifications: Page loads within performance baseline, all UI elements render correctly, navigation breadcrumb displays proper hierarchy
Negative_Verification: No error messages displayed, no broken UI elements, no unauthorized access warnings
Test Case 2: Three Configuration Sections Display
Test Case ID: CIS01US16_TC_002
Title: Verify New Connection Configuration displays three distinct sections: Response Time Configuration, Address Display Configuration, and Document Types Configuration
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: UI
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, UI, Visual-Validation, MOD-Settings, P1-Critical, Phase-Smoke, Type-UI, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-Module-Coverage, Report-Smoke-Test-Results, Report-User-Acceptance, Customer-All, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Integration-UI-Framework, Layout-Validation
Business Context
Customer_Segment: All
Revenue_Impact: Medium
Business_Priority: Must-Have
Customer_Journey: Onboarding
Compliance_Required: Yes
SLA_Related: Yes
Quality Metrics
Risk_Level: Medium
Complexity_Level: Low
Expected_Execution_Time: 1 minute
Reproducibility_Score: High
Data_Sensitivity: Low
Failure_Impact: High
Coverage Tracking
Feature_Coverage: 100% of UI section layout
Integration_Points: Settings UI Framework, CSS Grid System
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, Module-Coverage, Smoke-Test-Results, User-Acceptance, Product
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High
Requirements Traceability
Related_Requirements: AC2 - Three distinct configuration sections, Solution Section - Key Capability Areas, User Story Section 5 - System Administrator Flow Steps 2-4
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_001 (Access prerequisite)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Settings module UI framework, CSS styling system
Performance_Baseline: Section rendering within 1 second
Data_Requirements: Default configuration values loaded
Prerequisites
Setup_Requirements: System Administrator successfully logged in and navigated to New Connection Configuration
User_Roles_Permissions: System Administrator access
Test_Data: Default configuration state with no custom modifications
Prior_Test_Cases: CIS01US16_TC_001 must pass
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Access New Connection Configuration page as System Administrator | Page loads successfully displaying main configuration interface | admin@waterutil.com credentials | From successful AC1 execution |
2 | Verify Response Time Configuration section header and icon | Section displays with header "Response Time Configuration" and clock icon |
| Section positioned at top of page |
3 | Verify Response Time Configuration section content | Section contains three input fields: Acknowledgment Time (hours), Response Time (hours), Resolution Time (hours) | Default values: 24, 48, 168 | Each field clearly labeled with hours specification |
4 | Verify Address Display Configuration section header and icon | Section displays with header "Address Display Configuration" and location pin icon |
| Section positioned in middle area |
5 | Verify Address Display Configuration section content | Section contains Address Components area, Display Format options (Single Line, Two Lines, Three Lines), and Address Preview panel |
| Components dropdown and drag-drop area visible |
6 | Verify Document Types Configuration section header and icon | Section displays with header "Document Types Configuration" and document icon |
| Section positioned at bottom |
7 | Verify Document Types Configuration section content | Section contains Selected Document Types area, dropdown for adding documents, and Document Selection Summary panel |
| Summary shows totals for required/optional documents |
8 | Verify visual separation between sections | Each section has clear visual boundaries with consistent spacing and styling |
| Sections should not overlap or appear merged |
9 | Verify section order matches specification | Sections appear in order: Response Time → Address Display → Document Types |
| Vertical layout with logical flow |
10 | Verify responsive layout at 1920x1080 resolution | All sections fit properly within viewport without horizontal scrolling | Desktop resolution: 1920x1080 | All content visible without scrolling |
Verification Points
Primary_Verification: All three configuration sections are clearly visible, properly labeled, and distinctly separated on the New Connection Configuration page
Secondary_Verifications: Section icons display correctly, content areas are functional, visual hierarchy is maintained, section ordering matches specification
Negative_Verification: No missing sections, no overlapping content, no broken layout elements, no visual inconsistencies
Test Case 3: Response Time Business Rule Enforcement
Test Case ID: CIS01US16_TC_003
Title: Verify system enforces business rule that acknowledgment time < response time < resolution time with proper validation messaging
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated
Tags: Negative, Consumer/Onboarding Services, Validation, Business-Logic, MOD-Settings, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Regression-Coverage, Report-API-Test-Results, Report-Customer-Segment-Analysis, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Business-Rules, SLA-Validation
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: 3 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: Critical
Coverage Tracking
Feature_Coverage: 100% of SLA time validation business rules
Integration_Points: Validation Engine, Business Rule Framework, SLA Management
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Engineering
Report_Categories: Quality-Dashboard, Regression-Coverage, Engineering, API-Test-Results, Customer-Segment-Analysis
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical
Requirements Traceability
Related_Requirements: AC3 - Response time business rule enforcement, Business Rules Section 7 - Response Time Configuration Rules, Sample Data Section 8 - Response Time samples
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_012 (Save Configuration validation)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Business rule validation engine, Form validation framework
Performance_Baseline: Validation response within 200ms
Data_Requirements: Clean configuration state for testing validation rules
Prerequisites
Setup_Requirements: New Connection Configuration page loaded with default values
User_Roles_Permissions: System Administrator access
Test_Data: Default SLA values (Acknowledgment: 24, Response: 48, Resolution: 168), Invalid test sequences for validation testing
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Response Time Configuration section | Section displays with current values: Acknowledgment: 24, Response: 48, Resolution: 168 hours | Default configuration values | Verify baseline state before testing |
2 | Clear Acknowledgment Time field and enter invalid high value | Field accepts input, validation pending until sequence check | Acknowledgment Time: 72 | Higher than default response time (48) |
3 | Tab to Response Time field (keeping current value 48) | System validates sequence: Acknowledgment (72) > Response (48), displays validation error message | Response Time: 48 (unchanged) | AC3: "Response time must be greater than acknowledgment time" |
4 | Verify error message content and styling | Red error message displays: "Response time must be greater than acknowledgment time" with error icon |
| Error should be prominently displayed |
5 | Verify error field highlighting | Acknowledgment Time and Response Time fields highlighted with red border indicating validation failure |
| Visual feedback for user correction |
6 | Correct Acknowledgment Time to valid value | Enter 36 hours, error message clears, field highlighting removed | Acknowledgment Time: 36 | Lower than Response Time (48) |
7 | Clear Resolution Time field and enter invalid low value | Field accepts input, validation pending until sequence check | Resolution Time: 24 | Lower than Response Time (48) |
8 | Tab away from Resolution Time field | System validates sequence: Resolution (24) < Response (48), displays validation error message |
| AC3: "Resolution time must be greater than response time" |
9 | Verify resolution error message content | Red error message displays: "Resolution time must be greater than response time" with error icon |
| Specific error for resolution validation |
10 | Test complete invalid sequence | Enter Acknowledgment: 100, Response: 50, Resolution: 25 hours | Invalid sequence: 100 > 50 > 25 | Multiple validation errors should display |
11 | Verify multiple error handling | System displays both acknowledgment and resolution validation errors simultaneously |
| Multiple errors should coexist |
12 | Correct to valid sequence and verify error clearance | Enter Acknowledgment: 24, Response: 48, Resolution: 168 hours | Valid sequence: 24 < 48 < 168 | All errors should clear automatically |
Verification Points
Primary_Verification: System correctly enforces the business rule that acknowledgment time < response time < resolution time with appropriate validation messages
Secondary_Verifications: Error messages are clear and specific, field highlighting indicates validation issues, multiple errors can be displayed simultaneously, validation clears when values become valid
Negative_Verification: Cannot save configuration with invalid time relationships, validation prevents form submission, no false positive validations
Test Case 4: Drag-and-Drop Address Component Interface
Test Case ID: CIS01US16_TC_004
Title: Verify drag-and-drop interface for arranging address components works correctly with real-time order updates and visual feedback
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: UI
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Manual
Tags: Happy-Path, Consumer Services, UI, Drag-Drop-Interaction, MOD-Settings, P1-Critical, Phase-Regression, Type-UI, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Cross-Browser-Results, Report-Module-Coverage, Customer-All, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Integration-UI-Components, Address-Management
Business Context
Customer_Segment: All
Revenue_Impact: Medium
Business_Priority: Must-Have
Customer_Journey: Onboarding
Compliance_Required: Yes
SLA_Related: No
Quality Metrics
Risk_Level: Medium
Complexity_Level: High
Expected_Execution_Time: 4 minutes
Reproducibility_Score: High
Data_Sensitivity: Low
Failure_Impact: High
Coverage Tracking
Feature_Coverage: 100% of drag-drop address component functionality
Integration_Points: UI Framework, Address Management System, Real-time Preview
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, User-Acceptance, Product, Cross-Browser-Results, Module-Coverage
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: High
Requirements Traceability
Related_Requirements: AC4 - Drag-and-drop interface provision, Business Rules Section 7 - Address Display Configuration Rules, User Story Section 4 - Address Display Standardization
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_006 (Real-time Preview)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: JavaScript drag-drop library, Address component management system
Performance_Baseline: Drag operations complete within 100ms, visual feedback immediate
Data_Requirements: Address components: Unit, Address line, Region, Country, State, City, Zone, Division, Area, Sub area, Premise, Zipcode
Prerequisites
Setup_Requirements: New Connection Configuration page loaded with Address Display Configuration section visible
User_Roles_Permissions: System Administrator access
Test_Data: Clean address component state, Sample components: Unit, State, City, Region for testing drag operations
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Address Display Configuration section | Section displays with "Add address component..." dropdown and empty component area |
| Initial state with no components selected |
2 | Click "Add address component..." dropdown | Dropdown opens showing all 12 available address components with descriptions | Available: Unit, Address line, Region, Country, State, City, Zone, Division, Area, Sub area, Premise, Zipcode | All components should be selectable |
3 | Select "Unit" from dropdown | Unit component appears in component list with drag handle (≡), description "Unit or apartment number", Order: 1 | Unit component | Verify drag handle icon visibility |
4 | Add "State" component using dropdown | State component appears below Unit with drag handle, description "State or province", Order: 2 | State component | Components should stack vertically |
5 | Add "City" component using dropdown | City component appears below State with drag handle, description "City or municipality", Order: 3 | City component | Order numbers auto-increment |
6 | Hover over Unit component drag handle | Mouse cursor changes to move/grab cursor, component highlights for drag feedback |
| Visual feedback for draggable state |
7 | Drag Unit component below State component | During drag: visual placeholder shows drop position, Unit component follows mouse movement |
| Visual drag feedback essential |
8 | Drop Unit component in position 2 | Component order updates: State (Order: 1), Unit (Order: 2), City (Order: 3), order numbers re-sequence automatically |
| Real-time order update verification |
9 | Drag City component to top position (above State) | City moves to Order: 1, State becomes Order: 2, Unit becomes Order: 3 |
| Test drag to top position |
10 | Verify drag operation visual feedback | During drag: drop zones highlighted, invalid drop areas show rejection feedback |
| User should understand valid drop zones |
11 | Test drag cancellation by dragging outside component area and releasing | Component returns to original position, order remains unchanged |
| Drag cancellation functionality |
12 | Verify final component order in UI | Components display in final order: City (1), State (2), Unit (3) with correct descriptions and remove icons | Final order: City, State, Unit | Visual verification of drag results |
Verification Points
Primary_Verification: Drag-and-drop interface allows users to successfully reorder address components with automatic order number updates and visual feedback
Secondary_Verifications: Drag handles are visible and functional, drop zones provide clear visual feedback, order numbers update automatically, components maintain integrity during drag operations
Negative_Verification: Cannot drag components outside designated areas, drag cancellation works properly, invalid drop positions are rejected
Test Case 5: Three Address Display Format Options
Test Case ID: CIS01US16_TC_005
Title: Verify three address display format options (Single Line, Two Lines, Three Lines) work correctly with proper address distribution and formatting
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer Services, UI, Display-Logic, MOD-Settings, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-Module-Coverage, Report-User-Acceptance, Report-Customer-Segment-Analysis, Customer-All, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Integration-Display-Engine, Address-Formatting
Business Context
Customer_Segment: All
Revenue_Impact: Medium
Business_Priority: Must-Have
Customer_Journey: Onboarding
Compliance_Required: Yes
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: 100% of address display format options
Integration_Points: Address Display Engine, Preview System, Format Logic
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, Module-Coverage, Product, User-Acceptance, Customer-Segment-Analysis
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: High
Requirements Traceability
Related_Requirements: AC5 - Three display format options, Business Rules Section 7 - Address display format selection, Sample Data Section 8 - Address Display Configuration sample
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_004 (Component ordering), CIS01US16_TC_006 (Real-time preview)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Address formatting engine, Preview rendering system
Performance_Baseline: Format changes apply within 100ms
Data_Requirements: Sample address components: Unit, State, City, Region, Country, Zipcode for testing different line distributions
Prerequisites
Setup_Requirements: Address Display Configuration section with multiple components already added for format testing
User_Roles_Permissions: System Administrator access
Test_Data: Address components configured: Unit (205), State (Western Province), City (Colombo), Region (Central), Country (Sri Lanka), Zipcode (10400)
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002, CIS01US16_TC_004
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Address Display Configuration section with pre-configured components | Section displays with components: Unit, State, City, Region, Country, Zipcode in current order | Sample components: Unit (205), State (Western Province), City (Colombo), Region (Central), Country (Sri Lanka), Zipcode (10400) | Ensure sufficient components for multi-line testing |
2 | Locate Display Format options in Address Preview panel | Three radio button options visible: "Single Line", "Two Lines", "Three Lines" with Single Line selected by default |
| Default selection should be clearly indicated |
3 | Verify Single Line format selection and preview | Single Line radio button selected, address preview shows: "Unit 205, Western Province, Colombo, Central, Sri Lanka, 10400" | Single line format with comma separators | All components in one continuous line |
4 | Click "Two Lines" radio button option | Two Lines option becomes selected, Single Line deselects, preview updates immediately |
| Radio button exclusivity verification |
5 | Verify Two Lines format address preview | Address preview displays in two lines with even distribution: Line 1: "Unit 205, Western Province, Colombo" Line 2: "Central, Sri Lanka, 10400" | Two-line distribution: 3 components per line | Components distributed evenly across lines |
6 | Click "Three Lines" radio button option | Three Lines option becomes selected, Two Lines deselects, preview updates immediately |
| Immediate format change |
7 | Verify Three Lines format address preview | Address preview displays in three lines with balanced distribution: Line 1: "Unit 205, Western Province" Line 2: "Colombo, Central" Line 3: "Sri Lanka, 10400" | Three-line distribution: 2 components per line | Even distribution across three lines |
8 | Test format changes with different component counts | Add one more component (Area), verify all three formats redistribute components appropriately | Add Area component: "Pettah" | Test format logic with odd number of components |
9 | Verify format consistency with component reordering | Drag components to new order, verify all three format options maintain proper distribution | Reorder: City first, then Unit, State, etc. | Format logic should adapt to new order |
10 | Test format selection persistence | Switch between formats multiple times, verify each maintains proper preview and selection state | Cycle: Single → Two → Three → Single | No format corruption or selection errors |
11 | Verify format information display | Each format option shows helpful description or component distribution information |
| User guidance for format selection |
12 | Test format preview with maximum components | Add all available components, test each format handles maximum component count | All 12 components if possible | Stress test format distribution logic |
Verification Points
Primary_Verification: All three address display format options (Single Line, Two Lines, Three Lines) work correctly with proper address component distribution and real-time preview updates
Secondary_Verifications: Radio button selection works properly, format changes are immediate, component distribution is logical and balanced, format selection persists during component modifications
Negative_Verification: Only one format can be selected at a time, no format corruption with component changes, no preview errors with different component counts
Test Case 6: Real-time Address Preview Updates
Test Case ID: CIS01US16_TC_006
Title: Verify real-time address preview updates immediately when configuration changes are made to components, order, or display format
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer Services, UI, Real-time-Updates, MOD-Settings, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-Performance-Metrics, Report-User-Acceptance, Report-Engineering, Customer-All, Risk-Medium, Business-Should-Have, Revenue-Impact-Low, Integration-Real-time-Engine, Preview-System
Business Context
Customer_Segment: All
Revenue_Impact: Low
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: Medium
Coverage Tracking
Feature_Coverage: 100% of real-time preview functionality
Integration_Points: Real-time Preview Engine, Address Display System, UI Event Handlers
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, Performance-Metrics, Product, User-Acceptance, Engineering
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium
Requirements Traceability
Related_Requirements: AC6 - Real-time address preview, Business Rules Section 7 - Address preview real-time updates, Solution Section 4 - Configuration Preview and Validation
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_004 (Drag-drop), CIS01US16_TC_005 (Format options)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: JavaScript event handlers, Real-time preview engine, Address formatting system
Performance_Baseline: Preview updates within 100ms of configuration changes
Data_Requirements: Sample address data: "Unit 205, Sunrise Apartments, North Central, Western Province, Colombo, Pettah" for consistent preview testing
Prerequisites
Setup_Requirements: Address Display Configuration section loaded with Address Preview panel visible
User_Roles_Permissions: System Administrator access
Test_Data: Sample address components and data for preview: Unit (205), Premise (Sunrise Apartments), Region (North Central), State (Western Province), City (Colombo), Area (Pettah)
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Address Display Configuration with empty component state | Address Preview panel displays with "Sample Address Display:" label and empty preview area |
| Baseline state for preview testing |
2 | Add Unit component via dropdown | Preview immediately updates to display: "Unit 205" with sample data | Unit component with sample: "205" | Immediate single component preview |
3 | Add State component via dropdown | Preview immediately updates to display: "Unit 205, Western Province" | State component with sample: "Western Province" | Two-component preview with comma separator |
4 | Measure preview update timing | Preview update occurs within 100ms of component addition (use browser dev tools timing) |
| Performance requirement validation |
5 | Add City component via dropdown | Preview immediately updates to display: "Unit 205, Western Province, Colombo" | City component with sample: "Colombo" | Three-component preview update |
6 | Change display format from Single Line to Two Lines | Preview immediately reformats to two lines: Line 1: "Unit 205" Line 2: "Western Province, Colombo" | Two Lines format selection | Real-time format change in preview |
7 | Drag Unit component to bottom position (below City) | Preview immediately reflects new order: Line 1: "Western Province" Line 2: "Colombo, Unit 205" | Drag Unit to position 3 | Real-time drag-drop preview update |
8 | Change back to Single Line format | Preview immediately displays: "Western Province, Colombo, Unit 205" in single line | Single Line format selection | Format change with new component order |
9 | Remove State component using remove (X) button | Preview immediately updates to: "Colombo, Unit 205" | Remove Western Province component | Real-time component removal |
10 | Add multiple components rapidly in sequence | Preview updates for each addition without delay or lag: Add Region, Area, Premise | Rapid additions: Region (North Central), Area (Pettah), Premise (Sunrise Apartments) | Stress test rapid changes |
11 | Test preview with Three Lines format | Preview immediately shows three-line distribution with current components | Three Lines format with 5 components | Multi-line real-time formatting |
12 | Verify preview information panel | Address Display Information panel shows: "This address format will be used consistently across the entire platform..." |
| Contextual information display |
Verification Points
Primary_Verification: Address preview updates in real-time (within 100ms) for all configuration changes including component additions, removals, reordering, and format changes
Secondary_Verifications: Preview displays accurate sample data, format changes are reflected immediately, component order changes update preview correctly, no lag or delay in updates
Negative_Verification: Preview never shows outdated information, no preview corruption during rapid changes, no JavaScript errors during real-time updates
Test Case 7: Document Type Selection and Status Management
Test Case ID: CIS01US16_TC_007
Title: Verify selection of multiple document types with individual required/optional designation and proper status management
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, Document-Management, Configuration, MOD-Settings, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-Module-Coverage, Report-Customer-Segment-Analysis, Report-User-Acceptance, Customer-All, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Integration-Document-System, Compliance-Management
Business Context
Customer_Segment: All
Revenue_Impact: Medium
Business_Priority: Must-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: Medium
Failure_Impact: High
Coverage Tracking
Feature_Coverage: 100% of document type selection and status management
Integration_Points: Document Management System, Onboarding Forms, Compliance Framework
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, Module-Coverage, Product, Customer-Segment-Analysis, User-Acceptance
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: High
Requirements Traceability
Related_Requirements: AC7 - Document type selection with required/optional designation, Business Rules Section 7 - Document Types Configuration Rules, Sample Data Section 8 - Document Types Configuration sample
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_008 (Document Summary)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Document type management system, Utility document configuration
Performance_Baseline: Document selection response within 200ms
Data_Requirements: Configured document types from utility setup: National ID, Address Proof, Passport, Income Proof, Bank Statement, Utility Bill
Prerequisites
Setup_Requirements: Document Types Configuration section loaded with utility-configured document types available
User_Roles_Permissions: System Administrator access
Test_Data: Available document types configured in utility setup with descriptions: National ID (Government issued identity), Address Proof (Current address verification), Passport (Valid passport), Income Proof (Salary/income certificate)
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Document Types Configuration section | Section displays with "Selected Document Types" area, "Add document type..." dropdown, and "Document Selection Summary" panel |
| Initial empty state for document selection |
2 | Click "Add document type..." dropdown | Dropdown opens showing all configured document types from utility setup with descriptions | Available options: National ID, Address Proof, Passport, Income Proof, Bank Statement, Utility Bill | All utility-configured documents should be available |
3 | Select "National ID" from dropdown | Document appears in Selected Document Types list with: Document name, description "Government issued national identity card", Required checkbox (unchecked), Remove (X) button | National ID selection | First document addition verification |
4 | Verify Required checkbox functionality for National ID | Click Required checkbox - becomes checked with blue checkmark, document shows required status | National ID Required checkbox | Required status toggle verification |
5 | Add "Address Proof" document from dropdown | Document appears below National ID with description "Document proving current address", Required checkbox unchecked | Address Proof selection | Second document addition |
6 | Set Address Proof as required | Check Required checkbox for Address Proof, verify both documents now show required status | Address Proof Required checkbox | Multiple required documents |
7 | Add "Passport" document and leave as optional | Passport appears with description "Valid passport document", Required checkbox remains unchecked | Passport selection (optional) | Optional document verification |
8 | Add "Income Proof" document and leave as optional | Income Proof appears with description "Salary slip or income certificate", Required checkbox unchecked | Income Proof selection (optional) | Second optional document |
9 | Verify document list display and organization | Four documents displayed in selection order: National ID (Required), Address Proof (Required), Passport (Optional), Income Proof (Optional) | Complete document list | Document organization verification |
10 | Test Required status toggle functionality | Change Passport from optional to required, then back to optional, verify status changes correctly | Toggle Passport Required status | Status change functionality |
11 | Test document removal functionality | Click Remove (X) button for Passport document, document removed from list, summary updates immediately | Remove Passport document | Document removal verification |
12 | Verify document type uniqueness | Attempt to add National ID again from dropdown, option should be disabled or not available | National ID (already selected) | Prevent duplicate document types |
13 | Test bulk status changes | Change multiple document statuses rapidly, verify all changes apply correctly | Toggle required status for multiple documents | Bulk operation testing |
14 | Verify document descriptions display | All selected documents show proper descriptions from utility configuration | Document descriptions visible | Proper documentation for users |
Verification Points
Primary_Verification: Multiple document types can be selected with individual required/optional status management and proper removal functionality
Secondary_Verifications: Document descriptions display correctly, required/optional status toggles work properly, document uniqueness is enforced, removal operations update immediately
Negative_Verification: Cannot add duplicate document types, cannot break document list integrity, status changes are properly persisted
Test Case 8: Document Selection Summary Display
Test Case ID: CIS01US16_TC_008
Title: Verify document selection summary displays accurate total count and required vs optional breakdown with real-time updates
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, Summary-Display, Real-time-Updates, MOD-Settings, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Module-Coverage, Report-Performance-Metrics, Customer-All, Risk-Low, Business-Should-Have, Revenue-Impact-Low, Integration-Summary-Engine, Document-Analytics
Business Context
Customer_Segment: All
Revenue_Impact: Low
Business_Priority: Should-Have
Customer_Journey: Onboarding
Compliance_Required: Yes
SLA_Related: No
Quality Metrics
Risk_Level: Low
Complexity_Level: Low
Expected_Execution_Time: 2 minutes
Reproducibility_Score: High
Data_Sensitivity: Low
Failure_Impact: Medium
Coverage Tracking
Feature_Coverage: 100% of document selection summary functionality
Integration_Points: Document Management System, Summary Calculation Engine
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, User-Acceptance, Product, Module-Coverage, Performance-Metrics
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium
Requirements Traceability
Related_Requirements: AC8 - Document selection summary display, Business Rules Section 7 - Document summary calculation, Sample Data Section 8 - Document summary examples
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_007 (Document Selection)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Document calculation engine, Real-time summary updates
Performance_Baseline: Summary updates within 50ms of document changes
Data_Requirements: Various document configurations for testing summary calculations
Prerequisites
Setup_Requirements: Document Types Configuration section with Document Selection Summary panel visible
User_Roles_Permissions: System Administrator access
Test_Data: Test document combinations: National ID (Required), Address Proof (Required), Passport (Optional), Income Proof (Optional) for summary calculations
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002, CIS01US16_TC_007
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Document Types Configuration with empty state | Document Selection Summary panel displays: "Required Documents: (none), Optional Documents: (none), Total Selected: 0 document types" | Empty document state | Baseline summary for empty configuration |
2 | Add National ID document and set as required | Summary immediately updates to: "Required Documents: • National ID, Optional Documents: (none), Total Selected: 1 document types, Required: 1 document types, Optional: 0 document types" | National ID (Required) | First required document addition |
3 | Add Address Proof document and set as required | Summary updates to: "Required Documents: • National ID • Address Proof, Optional Documents: (none), Total Selected: 2 document types, Required: 2 document types, Optional: 0 document types" | Address Proof (Required) | Second required document |
4 | Add Passport document and leave as optional | Summary updates to: "Required Documents: • National ID • Address Proof, Optional Documents: • Passport, Total Selected: 3 document types, Required: 2 document types, Optional: 1 document types" | Passport (Optional) | First optional document |
5 | Add Income Proof document and leave as optional | Summary updates to: "Required Documents: • National ID • Address Proof, Optional Documents: • Passport • Income Proof, Total Selected: 4 document types, Required: 2 document types, Optional: 2 document types" | Income Proof (Optional) | Second optional document |
6 | Change Passport from optional to required | Summary immediately updates to: "Required Documents: • National ID • Address Proof • Passport, Optional Documents: • Income Proof, Total Selected: 4 document types, Required: 3 document types, Optional: 1 document types" | Toggle Passport to Required | Status change reflection |
7 | Change Address Proof from required to optional | Summary updates to: "Required Documents: • National ID • Passport, Optional Documents: • Address Proof • Income Proof, Total Selected: 4 document types, Required: 2 document types, Optional: 2 document types" | Toggle Address Proof to Optional | Required to optional change |
8 | Remove Passport document completely | Summary updates to: "Required Documents: • National ID, Optional Documents: • Address Proof • Income Proof, Total Selected: 3 document types, Required: 1 document types, Optional: 2 document types" | Remove Passport document | Document removal impact |
9 | Remove all documents to return to empty state | Summary returns to: "Required Documents: (none), Optional Documents: (none), Total Selected: 0 document types" | Remove all documents | Complete reset verification |
10 | Test summary update timing | Measure summary update speed during document changes (should be < 50ms) | Various document operations | Performance requirement |
11 | Verify summary styling and formatting | Summary displays with proper bullet points, clear sections, and appropriate spacing | Current document state | Visual presentation quality |
12 | Test summary with maximum documents | Add multiple documents, verify summary handles large lists properly | 6+ document types if available | Scalability testing |
Verification Points
Primary_Verification: Document selection summary accurately displays real-time counts and breakdown of required vs optional documents
Secondary_Verifications: Summary updates immediately with document changes, proper formatting and organization, correct mathematical calculations
Negative_Verification: Summary never shows incorrect counts, no calculation errors, no display corruption with rapid changes
Test Case 9: Configuration Input Validation
Test Case ID: CIS01US16_TC_009
Title: Verify comprehensive validation of all configuration inputs before allowing save operation with clear error messaging
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated
Tags: Negative, Consumer/Onboarding Services, Validation, Input-Validation, MOD-Settings, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Regression-Coverage, Report-API-Test-Results, Report-Security-Validation, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Validation-Engine, Data-Integrity
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: 100% of configuration validation rules
Integration_Points: Validation Engine, Business Rules Framework, Data Integrity System
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Engineering
Report_Categories: Quality-Dashboard, Regression-Coverage, Engineering, API-Test-Results, Security-Validation
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical
Requirements Traceability
Related_Requirements: AC9 - Configuration input validation before save, Business Rules Section 7 - All validation rules, User Story Section 5 - Validation and Save Configuration step
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_012 (Save Configuration)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Validation engine, Business rule framework, Form validation system
Performance_Baseline: Validation feedback within 200ms
Data_Requirements: Invalid test data sets for comprehensive validation testing
Prerequisites
Setup_Requirements: New Connection Configuration page with all sections accessible and Save Configuration button visible
User_Roles_Permissions: System Administrator access
Test_Data: Invalid data sets: Empty fields, invalid time sequences, missing required selections
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Clear all Response Time Configuration fields | All time fields empty: Acknowledgment, Response, Resolution | Empty values | Test empty field validation |
2 | Attempt to save configuration with empty time fields | Validation errors display: "Acknowledgment time is required", "Response time is required", "Resolution time is required"; Save button remains disabled or shows error | Empty time fields | Required field validation |
3 | Enter invalid time sequence in Response Time fields | Validation error displays: "Response time sequence invalid - Acknowledgment < Response < Resolution required" | Ack: 48, Resp: 24, Res: 168 (invalid sequence) | Business rule validation |
4 | Enter negative values in time fields | Validation errors display: "Time values must be positive integers greater than 0" | Ack: -5, Resp: -10, Res: -20 | Negative value validation |
5 | Enter zero values in time fields | Validation errors display: "Time values must be greater than 0" | Ack: 0, Resp: 0, Res: 0 | Zero value validation |
6 | Enter non-numeric values in time fields | Validation errors display: "Time values must be numeric" | Ack: "abc", Resp: "xyz", Res: "test" | Data type validation |
7 | Fix time validation errors with valid sequence | Time validation errors clear, time fields show valid green state | Ack: 24, Resp: 48, Res: 168 | Error clearance verification |
8 | Test Address Display validation - no components selected | System allows save (address components are optional for basic configuration) | No address components | Optional field validation |
9 | Add address components but select no display format | Validation error displays: "Display format must be selected when address components are configured" | Components added, no format selected | Conditional validation |
10 | Select display format, validation error clears | Address Display section validates successfully | Single Line format selected | Conditional validation clearance |
11 | Test comprehensive validation with multiple errors | Multiple validation messages display simultaneously, organized by section | Multiple invalid inputs across sections | Multi-error display |
12 | Attempt save with validation errors present | Save operation blocked, error message: "Please correct all validation errors before saving" | Various validation errors active | Save prevention with errors |
13 | Fix all validation errors and attempt save | All validation clears, save operation proceeds successfully | Valid configuration data | Validation success flow |
Verification Points
Primary_Verification: Comprehensive validation prevents saving invalid configurations and provides clear error messaging for all validation failures
Secondary_Verifications: Multiple errors display simultaneously, validation errors clear when corrected, save operation blocked with active errors
Negative_Verification: Cannot save with any validation errors present, no false positive validations, no validation bypass possible
Test Case 10: Platform-Wide Configuration Application
Test Case ID: CIS01US16_TC_010
Title: Verify configuration changes apply immediately across all platform interfaces upon successful save operation
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Integration
Test Level: System
Priority: P1-Critical
Execution Phase: Acceptance
Automation Status: Manual
Tags: Happy-Path, Consumer/Onboarding Services, Integration, Cross-Module, MOD-Settings, P1-Critical, Phase-Acceptance, Type-Integration, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Integration-Testing, Report-User-Acceptance, Report-Customer-Segment-Analysis, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Platform-Wide, Configuration-Propagation
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: 8 minutes
Reproducibility_Score: High
Data_Sensitivity: High
Failure_Impact: Critical
Coverage Tracking
Feature_Coverage: 100% of platform-wide configuration application
Integration_Points: Customer Onboarding, Consumer Accounts, Service Requests, Dashboard, Mobile Interface
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Engineering
Report_Categories: Quality-Dashboard, Integration-Testing, Engineering, User-Acceptance, Customer-Segment-Analysis
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical
Requirements Traceability
Related_Requirements: AC10 - Platform-wide configuration application, Solution Section 5 - System-Wide Application, Solution Section 7 - Integration and Consistency
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_012 (Save Configuration)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: All platform modules, Configuration propagation system, Module integration framework
Performance_Baseline: Configuration propagation within 30 seconds across all modules
Data_Requirements: Test configuration: Unit, State, City (Two Lines format), SLA times: Ack: 12hrs, Resp: 24hrs, Res: 72hrs, Documents: National ID (Req), Passport (Opt)
Prerequisites
Setup_Requirements: Access to all platform modules for integration testing, test customer data available
User_Roles_Permissions: System Administrator access with module navigation permissions
Test_Data: Specific test configuration for platform-wide verification, test customer records for validation
Prior_Test_Cases: CIS01US16_TC_009 (Validation), CIS01US16_TC_012 (Save functionality)
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Configure complete New Connection settings and save | Configuration saved successfully: Address format (Unit, State, City - Two Lines), SLA times (12/24/72 hrs), Documents (National ID required, Passport optional) | Complete test configuration | Baseline configuration for integration testing |
2 | Navigate to Customer Onboarding module | Module loads successfully, navigation breadcrumb shows path | Navigate to Consumer Onboarding menu | Integration point 1 verification |
3 | Start new customer onboarding process | New customer form displays with configured address format and document requirements | Initiate new customer process | Form should reflect configuration |
4 | Verify address input fields use configured format | Address collection form displays Unit, State, City fields arranged in Two Lines format as configured | Address input form | Address configuration integration |
5 | Verify document requirements match configuration | Document upload section requires National ID (marked required), Passport shown as optional | Document requirements section | Document configuration integration |
6 | Navigate to Consumer Accounts module | Module loads, existing customer records display | Consumer Accounts menu | Integration point 2 verification |
7 | View existing customer profile address display | Customer addresses display using Two Lines format: "Unit 205, Western Province" "Colombo" | Sample customer record | Address display consistency |
8 | Navigate to Service Requests / New Connection module | New connection request form loads | Services → New Connection | Integration point 3 verification |
9 | Verify SLA times display in new connection form | Form shows configured SLA commitments: Acknowledgment: 12 hours, Response: 24 hours, Resolution: 72 hours | New connection SLA display | SLA configuration integration |
10 | Verify new connection address collection | Address form uses configured format and components | Address collection in service form | Consistent address handling |
11 | Navigate to Dashboard module | Dashboard loads with summary information | Main Dashboard | Integration point 4 verification |
12 | Verify dashboard SLA displays use configured times | SLA widgets and metrics show 12/24/72 hour commitments | Dashboard SLA widgets | Dashboard integration |
13 | Test configuration persistence across user sessions | Logout, login again, verify configuration remains applied | Fresh login session | Session persistence verification |
14 | Verify configuration updates are immediate (no caching issues) | All modules immediately reflect configuration without requiring cache refresh | Cross-module verification | Real-time propagation testing |
Verification Points
Primary_Verification: Configuration changes are immediately applied and consistently displayed across all platform interfaces including Customer Onboarding, Consumer Accounts, Service Requests, and Dashboard
Secondary_Verifications: Address formats are consistent across modules, SLA times propagate correctly, document requirements are enforced uniformly, no caching delays affect configuration application
Negative_Verification: No old configuration persists anywhere, no module shows inconsistent formatting, no configuration propagation failures
Test Case 11: Unauthorized Access Prevention
Test Case ID: CIS01US16_TC_011
Title: Verify system prevents unauthorized users from accessing New Connection Configuration interface with proper security controls
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Security
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Automated
Tags: Negative, Auth Services, Security, Access-Control, MOD-Settings, P1-Critical, Phase-Smoke, Type-Security, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Security-Validation, Report-Smoke-Test-Results, Report-Customer-Segment-Analysis, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Security-Framework, Role-Based-Access
Business Context
Customer_Segment: All
Revenue_Impact: High
Business_Priority: Must-Have
Customer_Journey: Onboarding
Compliance_Required: Yes
SLA_Related: No
Quality Metrics
Risk_Level: High
Complexity_Level: Medium
Expected_Execution_Time: 4 minutes
Reproducibility_Score: High
Data_Sensitivity: High
Failure_Impact: Critical
Coverage Tracking
Feature_Coverage: 100% of unauthorized access prevention
Integration_Points: Authentication System, Role Management, Security Framework
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Engineering
Report_Categories: Quality-Dashboard, Security-Validation, Engineering, Smoke-Test-Results, Customer-Segment-Analysis
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical
Requirements Traceability
Related_Requirements: AC11 - Unauthorized access prevention, Problem Statement - System Administrator role requirements, User Story Section 6 - User Role-Based Access
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_001 (Authorized access)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Authentication system, Role-based access control, Security audit logging
Performance_Baseline: Security validation response within 100ms
Data_Requirements: Multiple user roles: Customer Service Representative, Utility Administrator, Customer Service Manager for access testing
Prerequisites
Setup_Requirements: Multiple user accounts configured with different role levels
User_Roles_Permissions: Test accounts: CSR (Customer Service Representative), Utility Admin, CSM (Customer Service Manager)
Test_Data: Test credentials: csr@waterutil.com/CSR123!, utility@waterutil.com/Util123!, csm@waterutil.com/CSM123!
Prior_Test_Cases: User authentication system validation
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Login as Customer Service Representative | Login successful, dashboard displays with limited navigation options | csr@waterutil.com / CSR123! | CSR role should have restricted access |
2 | Navigate to Settings menu | Settings page accessible but with limited configuration options | Settings menu navigation | Role-based menu filtering |
3 | Check for New Connection tab visibility | New Connection tab is either hidden or disabled for CSR role | New Connection tab inspection | Tab should not be accessible |
4 | Attempt direct URL access to configuration page | System redirects to unauthorized access page or displays 403 Forbidden error | https://app.waterutil.com/settings/new-connection | Direct URL access prevention |
5 | Verify unauthorized access error message | Clear error message: "You do not have permission to access New Connection Configuration. Contact your administrator." | Error message content | User-friendly error messaging |
6 | Logout CSR and login as Utility Administrator | Login successful, expanded navigation menu displays | utility@waterutil.com / Util123! | Utility Admin should have broader access |
7 | Check New Connection tab availability for Utility Admin | New Connection tab is visible and accessible (role should have access) | New Connection tab for Utility Admin | Role should have access rights |
8 | Access New Connection Configuration as Utility Admin | Configuration page loads successfully with full functionality | Full configuration interface | Verify proper access for authorized role |
9 | Logout and login as Customer Service Manager | Login successful, CSM dashboard displays | csm@waterutil.com / CSM123! | CSM role access testing |
10 | Test CSM access to New Connection configuration | Access should be view-only or denied based on role configuration | New Connection access attempt | CSM role may have limited access |
11 | Test API endpoint security without authentication | Direct API call returns 401 Unauthorized response | GET /api/config/new-connection (no auth header) | API security verification |
12 | Test API endpoint with invalid role | API call with CSR token returns 403 Forbidden response | API call with CSR authentication token | API role-based access control |
13 | Verify security audit logging | Configuration access attempts are logged with user, role, timestamp, and result | Security audit log entries | Security event logging |
14 | Test session security during unauthorized access attempts | User session remains secure, no elevation of privileges | Unauthorized access attempts | Session integrity verification |
Verification Points
Primary_Verification: Unauthorized users (CSR, CSM) cannot access New Connection Configuration interface through any method including direct navigation, URL access, or API calls
Secondary_Verifications: Appropriate error messages displayed, security audit logging captures access attempts, authorized roles maintain proper access
Negative_Verification: No privilege escalation possible, no security bypass methods available, no sensitive data exposure during access denial
Test Case 12: Save Configuration Button Functionality
Test Case ID: CIS01US16_TC_012
Title: Verify "Save Configuration" button commits all changes simultaneously with proper loading states and error handling
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, Save-Operation, Data-Persistence, MOD-Settings, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Report-Quality-Dashboard, Report-Module-Coverage, Report-Performance-Metrics, Report-User-Acceptance, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Data-Layer, Configuration-Management
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: 3 minutes
Reproducibility_Score: High
Data_Sensitivity: High
Failure_Impact: Critical
Coverage Tracking
Feature_Coverage: 100% of save configuration functionality
Integration_Points: Database Layer, Configuration Management System, Validation Engine
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Engineering
Report_Categories: Quality-Dashboard, Module-Coverage, Engineering, Performance-Metrics, User-Acceptance
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical
Requirements Traceability
Related_Requirements: AC12 - Save Configuration button functionality, User Story Section 5 - Save Configuration step, Business Rules Section 7 - Configuration persistence requirements
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_009 (Validation), CIS01US16_TC_010 (Platform-wide application)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Database system, Configuration management API, Validation framework
Performance_Baseline: Save operation completion within 2 seconds
Data_Requirements: Complete valid configuration for save testing
Prerequisites
Setup_Requirements: New Connection Configuration with valid data in all sections ready for save operation
User_Roles_Permissions: System Administrator access
Test_Data: Valid configuration: Response times (24/48/168), Address format (Unit, State, City - Two Lines), Documents (National ID required, Passport optional)
Prior_Test_Cases: CIS01US16_TC_001 through CIS01US16_TC_009
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Configure all three sections with valid data | All sections configured: Response Time (24/48/168 hrs), Address Display (Unit, State, City - Two Lines), Documents (National ID required, Passport optional) | Complete valid configuration | Prepare comprehensive configuration for save |
2 | Verify Save Configuration button state and visibility | Button displays as "Save Configuration" with enabled state, positioned prominently at bottom of page | Save button inspection | Button should be clearly visible and accessible |
3 | Click "Save Configuration" button | Save operation initiates immediately, button shows loading state: "Saving..." with spinner icon | Save button click | Visual feedback for save operation |
4 | Verify button disabled state during save | Button becomes disabled during save operation to prevent multiple simultaneous save attempts | Button state during save | Prevent double-click issues |
5 | Monitor save operation timing | Save operation completes within 2 seconds with success indication | Performance monitoring | Save performance requirement |
6 | Verify save operation success feedback | Loading state clears, button returns to normal state, success message appears | Save completion feedback | User confirmation of successful save |
7 | Verify data persistence after save | Refresh page, all configured settings remain saved and display correctly | Page refresh verification | Database persistence confirmation |
8 | Test partial configuration save | Make changes to only one section (Response Time), verify save updates only changed data | Partial save: Change Ack time to 12 hrs | Selective save functionality |
9 | Test save operation with validation errors | Save button remains disabled or shows validation message when errors present | Invalid data causing validation errors | Save prevention with errors |
10 | Test save operation error handling | Simulate database error, verify appropriate error message and recovery | Database connectivity issue simulation | Error handling verification |
11 | Verify save operation atomic nature | All changes save together or all fail together (no partial saves in error conditions) | Complete configuration save | Transaction atomicity |
12 | Test save button accessibility | Button accessible via keyboard navigation (Tab + Enter), screen reader compatible | Keyboard navigation and accessibility | Accessibility compliance |
Verification Points
Primary_Verification: Save Configuration button successfully commits all configuration changes simultaneously with proper loading states and user feedback
Secondary_Verifications: Data persists correctly after save, button provides proper visual feedback, error conditions handled gracefully, performance meets requirements
Negative_Verification: Cannot trigger multiple save operations, save prevented with validation errors, no data corruption in error scenarios
Test Case 13: Save Confirmation Message Display
Test Case ID: CIS01US16_TC_013
Title: Verify system displays clear confirmation message upon successful configuration save with proper styling and auto-dismissal
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: UI
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, UI-Feedback, User-Experience, MOD-Settings, P2-High, Phase-Regression, Type-UI, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Module-Coverage, Report-Performance-Metrics, Customer-All, Risk-Low, Business-Should-Have, Revenue-Impact-Low, Integration-User-Interface, Feedback-System
Business Context
Customer_Segment: All
Revenue_Impact: Low
Business_Priority: Should-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: Low
Failure_Impact: Medium
Coverage Tracking
Feature_Coverage: 100% of save confirmation messaging functionality
Integration_Points: UI Framework, Notification System, User Feedback Components
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, User-Acceptance, Product, Module-Coverage, Performance-Metrics
Trend_Tracking: No
Executive_Visibility: No
Customer_Impact_Level: Medium
Requirements Traceability
Related_Requirements: AC13 - Save confirmation message display, User Story Section 5 - Confirm successful save with system notification, Solution Section 4 - Configuration Preview and Validation
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_012 (Save Configuration)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: UI notification system, CSS styling framework
Performance_Baseline: Confirmation message appears within 100ms of save completion
Data_Requirements: Valid configuration data for successful save operation
Prerequisites
Setup_Requirements: New Connection Configuration with valid data ready for save operation
User_Roles_Permissions: System Administrator access
Test_Data: Valid configuration ensuring successful save operation
Prior_Test_Cases: CIS01US16_TC_012 (Save Configuration functionality)
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Complete valid configuration in all sections | All sections configured with valid data ready for save | Valid configuration data | Preparation for successful save |
2 | Click "Save Configuration" button | Save operation initiates and completes successfully | Save button click | Successful save operation required |
3 | Verify confirmation message appears immediately after save | Success message displays within 100ms: "Configuration saved successfully" or similar | Message timing verification | Immediate user feedback |
4 | Verify confirmation message content and clarity | Message clearly states successful save with appropriate language: "New Connection Configuration has been saved successfully" | Message content inspection | Clear, unambiguous messaging |
5 | Verify confirmation message styling and visual design | Message appears with success styling: green background or border, checkmark icon, prominent positioning | Success message styling | Positive visual feedback |
6 | Verify confirmation message positioning | Message appears in prominent location: top of page, modal overlay, or dedicated notification area | Message positioning | Visibility and user attention |
7 | Verify confirmation message auto-dismissal timing | Message automatically disappears after 5 seconds without user interaction | Auto-dismissal timing | Automatic cleanup |
8 | Test manual message dismissal | User can manually close message using X button or clicking outside modal | Manual dismissal functionality | User control over notification |
9 | Verify confirmation message accessibility | Message accessible to screen readers with appropriate ARIA labels and roles | Accessibility compliance | Inclusive design |
10 | Test confirmation message with save errors | When save fails, appropriate error message displays instead of success message | Simulate save failure | Error message differentiation |
11 | Verify message stacking with multiple operations | Multiple rapid save operations show appropriate message handling (queue or replace) | Rapid save operations | Multiple message handling |
12 | Test confirmation message responsiveness | Message displays properly on different screen sizes and zoom levels | Various screen resolutions | Responsive design verification |
Verification Points
Primary_Verification: Clear, properly styled confirmation message displays immediately upon successful configuration save with appropriate auto-dismissal behavior
Secondary_Verifications: Message content is clear and specific, visual styling indicates success, message positioning is prominent, accessibility features work correctly
Negative_Verification: No false success messages on save failures, no message display issues or timing problems, no accessibility barriers
Test Case 14: Unsaved Changes Retention
Test Case ID: CIS01US16_TC_014
Title: Verify system retains unsaved changes when navigating between configuration sections without losing user input
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: Functional
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Automated
Tags: Happy-Path, Consumer/Onboarding Services, State-Management, User-Experience, MOD-Settings, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Performance-Metrics, Report-Engineering, Customer-All, Risk-Medium, Business-Should-Have, Revenue-Impact-Low, Integration-State-Persistence, Form-Management
Business Context
Customer_Segment: All
Revenue_Impact: Low
Business_Priority: Should-Have
Customer_Journey: Onboarding
Compliance_Required: No
SLA_Related: No
Quality Metrics
Risk_Level: Medium
Complexity_Level: Medium
Expected_Execution_Time: 3 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: Medium
Coverage Tracking
Feature_Coverage: 100% of unsaved changes retention functionality
Integration_Points: Form State Management, Client-side Storage, UI Navigation System
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, User-Acceptance, Product, Performance-Metrics, Engineering
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium
Requirements Traceability
Related_Requirements: AC14 - Unsaved changes retention during navigation, User Story Section 5 - Configuration state management, Solution Section 4 - Configuration validation and state handling
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_015 (Navigation warning)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: JavaScript state management, Form handling framework, Client-side data retention
Performance_Baseline: State retention with no noticeable delay during section navigation
Data_Requirements: Test data for each configuration section to validate state retention
Prerequisites
Setup_Requirements: New Connection Configuration page loaded with all sections accessible
User_Roles_Permissions: System Administrator access
Test_Data: Test inputs for each section: Response times (36/72/144), Address components (Unit, State, City, Region), Documents (National ID, Address Proof)
Prior_Test_Cases: CIS01US16_TC_001, CIS01US16_TC_002
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Navigate to Response Time Configuration section | Section displays with default values: Acknowledgment: 24, Response: 48, Resolution: 168 | Default response time values | Starting baseline state |
2 | Modify Response Time values without saving | Enter new values: Acknowledgment: 36, Response: 72, Resolution: 144 hours | Modified SLA times: 36/72/144 | Create unsaved changes |
3 | Scroll down to Address Display Configuration section | Response Time section scrolls out of view, Address Display section becomes visible | Navigate to address section | Section navigation without page change |
4 | Add address components without saving | Add components: Unit, State, City, Region in that order | Address components: Unit, State, City, Region | Create unsaved address changes |
5 | Set address display format without saving | Select "Three Lines" format option | Three Lines display format | Additional unsaved change |
6 | Scroll up to verify Response Time values retained | Response Time section shows modified values: 36/72/144 hours (not default values) | Previously modified values should persist | Verify state retention |
7 | Scroll down to Document Types Configuration section | Document section becomes visible, previous sections retain changes | Navigate to document section | Third section navigation |
8 | Add document types without saving | Select and configure: National ID (required), Address Proof (required), Passport (optional) | Document configuration setup | Create unsaved document changes |
9 | Navigate back to Response Time Configuration | Response Time values still show: 36/72/144 hours | Modified response times should persist | Cross-section state retention |
10 | Navigate to Address Display Configuration | Address components and Three Lines format still configured | Previous address setup should persist | Address state retention |
11 | Navigate to Document Types Configuration | Document selections remain: National ID (req), Address Proof (req), Passport (opt) | Document setup should persist | Document state retention |
12 | Test rapid section navigation | Quickly navigate between all sections multiple times, verify all changes retained | All previously modified values | Stress test state management |
13 | Simulate user workflow interruption | Navigate away and back, verify unsaved changes still present | All unsaved modifications | Realistic user behavior testing |
14 | Verify changes lost only on page refresh | Refresh browser page, confirm all unsaved changes are lost (expected behavior) | Page refresh test | Expected state clearing |
Verification Points
Primary_Verification: All unsaved changes are retained when navigating between configuration sections within the same page session
Secondary_Verifications: State management works consistently across all sections, rapid navigation doesn't cause data loss, changes persist during normal user workflow patterns
Negative_Verification: Changes are appropriately lost on page refresh (no unintended persistence), no memory leaks from state retention, no performance degradation
Test Case 15: Navigation Away Warning
Test Case ID: CIS01US16_TC_015
Title: Verify system prompts user confirmation when attempting to navigate away with unsaved changes to prevent accidental data loss
Created By: Hetal
Created Date: August 06, 2025
Version: 1.0
Classification
Module/Feature: New Connection Configuration
Test Type: UI
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Manual
Tags: Happy-Path, Consumer/Onboarding Services, Navigation-Warning, User-Protection, MOD-Settings, P2-High, Phase-Regression, Type-UI, Platform-Web, Report-Product, Report-Quality-Dashboard, Report-User-Acceptance, Report-Cross-Browser-Results, Report-Performance-Metrics, Customer-All, Risk-Medium, Business-Should-Have, Revenue-Impact-Low, Integration-Navigation-Guard, Data-Loss-Prevention
Business Context
Customer_Segment: All
Revenue_Impact: Low
Business_Priority: Should-Have
Customer_Journey: Onboarding
Compliance_Required: No
SLA_Related: No
Quality Metrics
Risk_Level: Medium
Complexity_Level: Medium
Expected_Execution_Time: 4 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: Medium
Coverage Tracking
Feature_Coverage: 100% of navigation warning functionality
Integration_Points: Navigation Guard System, Browser Event Handlers, Modal Dialog System
Code_Module_Mapped: CX-Web
Requirement_Coverage: Complete
Cross_Platform_Support: Web
Stakeholder Reporting
Primary_Stakeholder: Product
Report_Categories: Quality-Dashboard, User-Acceptance, Product, Cross-Browser-Results, Performance-Metrics
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium
Requirements Traceability
Related_Requirements: AC15 - Navigation away warning with user confirmation, User Story Section 5 - Unsaved changes protection, Solution Section 4 - Data loss prevention during navigation
Related_Bugs: N/A
Related_Test_Cases: CIS01US16_TC_014 (Unsaved changes retention)
Test Environment
Environment: Staging
Browser/Version: Chrome 115+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: JavaScript navigation guards, Browser beforeunload events, Modal dialog framework
Performance_Baseline: Warning dialog appears within 100ms of navigation attempt
Data_Requirements: Unsaved configuration changes for triggering navigation warnings
Prerequisites
Setup_Requirements: New Connection Configuration page with unsaved changes present
User_Roles_Permissions: System Administrator access
Test_Data: Unsaved changes: Modified response times (12/24/72), Address components (Unit, State), Document selection (National ID)
Prior_Test_Cases: CIS01US16_TC_014 (Unsaved changes retention)
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
1 | Create unsaved changes in Response Time Configuration | Modify values: Acknowledgment: 12, Response: 24, Resolution: 72 hours without saving | Unsaved SLA changes: 12/24/72 | Establish unsaved state for warning trigger |
2 | Add unsaved address components | Add Unit and State components, select Two Lines format without saving | Unsaved address config: Unit, State (Two Lines) | Additional unsaved changes |
3 | Attempt to navigate to Dashboard via menu | Navigation warning modal appears with message: "You have unsaved changes. Are you sure you want to leave this page?" | Dashboard menu click | Primary navigation warning test |
4 | Verify warning dialog content and options | Modal displays clear warning message with two buttons: "Stay on Page" (or "Cancel") and "Leave Page" (or "Discard Changes") | Warning dialog options | User choice clarity |
5 | Click "Stay on Page" or "Cancel" button | Modal closes, remains on New Connection Configuration page, all unsaved changes retained | Cancel navigation action | User chooses to stay |
6 | Verify unsaved changes still present after canceling navigation | All previously modified values still display: Response times (12/24/72), Address components (Unit, State), format (Two Lines) | Previous unsaved changes intact | Changes preservation after cancel |
7 | Attempt navigation to Consumer Accounts module | Warning modal appears again with same message and options | Consumer Accounts menu click | Consistent warning behavior |
8 | Click "Leave Page" or "Discard Changes" button | Navigation proceeds to Consumer Accounts module, unsaved changes are lost | Confirm leave action | User chooses to discard changes |
9 | Navigate back to New Connection Configuration | Page displays with default/saved values, all unsaved changes lost (expected behavior) | Return to configuration page | Confirm changes discarded |
10 | Create new unsaved changes and test browser back button | Make new changes, click browser back button, warning should appear | New unsaved changes + browser back | Browser navigation integration |
11 | Test warning with browser refresh | Create unsaved changes, attempt browser refresh (Ctrl+R), browser warning should appear | Unsaved changes + browser refresh | Browser refresh warning |
12 | Test warning when closing browser tab | Create unsaved changes, attempt to close tab (Ctrl+W), browser warning should appear | Unsaved changes + tab close | Browser tab close warning |
13 | Test no warning after successful save | Save configuration, then navigate away - no warning should appear | Saved configuration state | No warning when changes saved |
14 | Test warning accessibility and keyboard navigation | Warning modal accessible via keyboard, Tab navigation works, Enter/Escape keys function properly | Keyboard accessibility testing | Accessible dialog interaction |
Verification Points
Primary_Verification: System displays confirmation dialog when user attempts to navigate away from configuration page with unsaved changes, providing options to stay or leave
Secondary_Verifications: Warning integrates with browser navigation events, dialog provides clear messaging and options, unsaved changes are preserved when user chooses to stay
Negative_Verification: No warning appears when no unsaved changes present, warning works consistently across all navigation methods, changes are properly discarded when user chooses to leave
