Skip to main content

New Connection Application Detail View (CIS01US04)

Total Test Cases - 18
Total Acceptance Criteria - 17
Total Coverage = 100%

Test Scenario Summary

This test suite covers the complete workflow for New Connection Application processing in a B2B utility SaaS environment, supporting both Customer Executive and Utility Administrator user roles across six workflow stages: Application Review, Site Inspection, Approval, Installation, Activation, and Follow-up.

Functional Test Scenarios Overview:

  • Application Review Workflow: Document verification, requirements validation, application decision making
  • Site Inspection Management: Scheduling, location verification, inspection results processing
  • Approval Process: Requirements validation, inspection results review, final approval decisions
  • Installation Management: New meter installation scheduling and existing meter assignment
  • Service Activation: Meter configuration, communication setup, service enablement
  • Cross-Stage Navigation: Workflow progress tracking and stage transition validation

Non-Functional Test Scenarios:

  • Performance Testing: Page load times, document processing, concurrent user handling
  • Security Testing: Role-based access, data protection, audit trails
  • Compatibility Testing: Chrome 115+ browser support, cross-device responsiveness
  • Integration Testing: WX Dispatcher integration, meter management systems

Test Suite Organization

Smoke Test Suite (P1 Priority - Critical Business Functions)

  • Application Review: Document verification and acceptance workflow
  • Site Inspection: Basic scheduling and completion flow
  • Approval: Final approval decision process
  • Installation: Meter assignment or scheduling capability
  • Activation: Service enablement with basic requirements

Regression Test Suite (P1-P2 Priority - Core Features & Integration)

  • Complete end-to-end workflow execution
  • Document management and verification accuracy
  • Work order integration with WX Dispatcher
  • Application status tracking and updates
  • User role-based functionality validation


Test Case 1: Application Review Workflow Test Cases

Test Case Metadata

Test Case ID: CIS01US04_TC_001
Title: Verify Application Review Tab displays all required information panels with countdown timer
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/UI
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Information-Panels, Countdown-Timer, HappyPath, API

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: Medium
Failure_Impact: Critical

Coverage Tracking

Feature_Coverage: Information Panels, Countdown Timer, Consumer Number Display
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
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+
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Active user session, application database, countdown service
Performance_Baseline: Page load < 3 seconds
Data_Requirements: Valid application with customer data

Prerequisites

Setup_Requirements: User logged in as Customer Executive
User_Roles_Permissions: Customer Executive role with application review access
Test_Data: Application ID: APP-20230615-001, Customer: Alex Johnson
Prior_Test_Cases: User authentication successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Service Connection Workflow with user information card,Workflow Progress ,required documents

Card ,application review card , applications note card

User information card displays (Contact Information with email id , phone no ,service address & billing address)Application Review tab is active and displayed with workflow progress indicator sho

wing 5 stages: (Application Review (active), Site Inspection, Approval, Installation, Activation) Required Documents card (with list of documents to verify and reject)Application Review card with (Requirement checklist , Payment Details and buttons “Accept application”, “Reject information”, “Reject application”)Application notes to add notes.

Test all elements present

Default tab with complete workflow visibility

2

Verify workflow progress indicator

Progress indicator shows 5 distinct stages with Application Review highlighted as active and remaining stages visible but inactive

Workflow stages data

Complete workflow visibility requirement

3

Verify countdown timer display

Timer displays "5 days remaining" with visual countdown indicator showing accurate remaining time

Countdown data based on submission date

Processing deadline tracking functionality

4

Verify Contact Information panel

Panel displays Email: alex.johnson@example.com, Phone: (555) 123-4567, Service Address: 123 Main Street, Anytown, AT 12345, Billing Address: 456 Billing St, Finance City, FC 56789

Alex Johnson contact data

Complete contact information display

5

Verify service vs billing address separation

Service Address and Billing Address are clearly labeled as separate sections with distinct formatting

Address separation data

Address distinction requirement

6

Verify Account Information panel

Panel displays Consumer Number: APP-20230615-001, Category: Residential, Sub Category: Single Family Home, Connection Date: 2023-06-15, Plan: Standard Residential Connection

Account data for APP-20230615-001

Consumer number format validation

7

Verify Consumer Number format

Consumer Number follows exact pattern APP-YYYYMMDD-XXX (APP-20230615-001)

Generated consumer number

Format compliance requirement

8

Verify Application Details panel

Panel displays Application ID: APP-20230615-001, Created On: 2023-06-15, Created By: John Smith, Updated On: May 22, 2023, Last Updated By: Jane Doe

Application metadata

Complete audit information

9

Verify countdown timer accuracy

Timer calculation shows accurate remaining days based on application submission date and current date

Timer calculation data

Deadline calculation verification

Verification Points

Primary_Verification: All three information panels (Contact, Account, Application Details) displayed with correct data, workflow progress indicator shows all 6 stages, countdown timer functional and accurate

Secondary_Verifications: Consumer number follows required APP-YYYYMMDD-XXX format, service and billing addresses displayed separately with clear labels, complete audit information shown with user attribution

Negative_Verification: No error messages displayed, no missing data fields, workflow stages properly restricted with future stages disabled, countdown timer never shows negative values


Test Case 2: Required Documents Display and Management

Test Case Metadata

Test Case ID: CIS01US04_TC_002
Title: Verify Required Documents section displays all 4 core documents with verification status
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/UI
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Document-Management, HappyPath, API

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: Required Documents Display and Management
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Application with uploaded documents, document management service
Performance_Baseline: Document list load < 2 seconds
Data_Requirements: Application with 4 uploaded core documents

Prerequisites

Setup_Requirements: Application with 4 required documents uploaded
User_Roles_Permissions: Customer Executive with document verification access
Test_Data: Identity Proof, Property Ownership Document, Previous Utility Bill, Service Application Form uploaded on 2023-06-15
Prior_Test_Cases: Application created with documents uploaded

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Required Documents section within Application Review tab

Section displays "Required Documents" header with verification summary showing document counts

Document list interface

Header shows real-time status counts

2

Verify document list displays exactly 4 documents

List shows exactly these 4 documents: Identity Proof, Property Ownership Document, Previous Utility Bill, Service Application Form all visible in order

Core document types list

Exactly 4 required documents as specified

3

Verify each document shows upload date

All 4 documents display "Uploaded on 2023-06-15" with consistent date formatting

Upload timestamp: 2023-06-15

Consistent upload date display

4

Verify each document has verification status

All documents show "Pending Verification" status with orange indicator icon

Initial verification status

Initial pending state for all documents

5

Verify action buttons for each document

Each document row has three action buttons: "Verify", "Reject", and "View" buttons clearly visible and enabled

Action control buttons

Individual document action capabilities

6

Verify verification summary displays

Summary section shows "0 verified", "0 rejected", "4 pending" with accurate counts

Status count summary

Real-time status tracking display

7

Verify bulk actions available

"Upload" and "Download All" buttons present and enabled at section level

Bulk operation controls

Document management tools availability

8

Verify document ordering

Documents displayed in logical order: Identity Proof, Property Ownership Document, Previous Utility Bill, Service Application Form

Document sequence

Consistent document presentation

Verification Points

Primary_Verification: Exactly 4 core documents displayed with correct names (Identity Proof, Property Ownership Document, Previous Utility Bill, Service Application Form) and pending verification status

Secondary_Verifications: Upload dates shown consistently, action buttons present for each document, verification summary displays accurate counts, bulk actions available

Negative_Verification: No duplicate documents shown, no missing action buttons, no extra documents beyond the 4 required, no incorrect status indicators


Test Case 3: Document Verification Workflow

Test Case Metadata

Test Case ID: CIS01US04_TC_003
Title: Verify document verification workflow - Mark document as Verified
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Workflow
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Document-Verification, HappyPath , API

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

Coverage Tracking

Feature_Coverage: Document Verification Actions and Status Updates
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
 

Stakeholder Reporting

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

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Document viewer service, audit logging system
Performance_Baseline: Document view load < 2 seconds, verification action < 1 second
Data_Requirements: Identity Proof document available for verification

Prerequisites

Setup_Requirements: Application with Identity Proof document uploaded and pending verification
User_Roles_Permissions: Customer Executive with document verification permissions
Test_Data: Identity Proof document in pending verification status
Prior_Test_Cases: NSC_TC_002 - Required Documents Display successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "View" button for Identity Proof document

Document viewer opens displaying the Identity Proof document with zoom and navigation controls

Identity Proof document

Document preview functionality verification

2

Click "Verify" button for Identity Proof document

Document status immediately changes from "Pending Verification" to "Verified" with green checkmark icon

Identity Proof verification action

Status update must be immediate

3

Verify status summary updates automatically

Summary section updates to show "1 verified", "0 rejected", "3 pending" with accurate real-time counts

Updated count display

Real-time counter update verification

4

Verify Requirements Checklist updates

"All documents verified" remains unchecked (orange) since only 1 of 4 documents verified

Requirements checklist logic

Partial completion tracking accuracy

5

Verify document action buttons update

Verified document no longer shows "Verify" button, only displays "View" and "Reject" buttons

Button state management

Contextual action button behavior

6

Verify audit trail logging

Verification action logged with user ID, timestamp, and document details in audit system

Audit logging verification

User action tracking requirement

7

Verify other documents remain unchanged

Remaining 3 documents still show "Pending Verification" status without being affected

Other document status

Isolated action impact verification

Verification Points

Primary_Verification: Document status successfully changes from "Pending Verification" to "Verified" with green checkmark, and summary counts update correctly showing "1 verified", "0 rejected", "3 pending"

Secondary_Verifications: Requirements checklist reflects partial completion appropriately, action buttons update to show only "View" and "Reject" for verified document, audit trail captures verification action with user attribution

Negative_Verification: Other documents remain unaffected by this verification, no system errors occur, verified document cannot be verified again, requirements checklist does not show complete until all documents verified


Test Case 4: Document Rejection Workflow

Test Case Metadata

Test Case ID: CIS01US04_TC_004
Title: Verify document rejection workflow with reason capture
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Workflow
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Document-Rejection,Negative

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: Document Rejection Process and Reason Capture
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
 

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Quality-Dashboard, Rejection-Tracking
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Document management system, audit logging service
Performance_Baseline: Rejection dialog load < 1 second, rejection processing < 2 seconds
Data_Requirements: Property Ownership Document in pending verification status

Prerequisites

Setup_Requirements: Application with Property Ownership Document uploaded and pending verification
User_Roles_Permissions: Customer Executive with document rejection permissions
Test_Data: Property Ownership Document available for rejection testing
Prior_Test_Cases: NSC_TC_002 - Document display successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "Reject" button for Property Ownership Document

Rejection dialog box opens with text field for rejection reason and confirmation buttons

Property Ownership Document

Rejection process initiation

2

Attempt to confirm “Reject button”

System displays validation error message 

Document rejected
Service application form has being rejected

Mandatory reason validation

3

Click "Confirm Rejection" button

Document status changes from "Pending Verification" to "Rejected" with red icon

Rejection confirmation

Status update with reason storage

4

Verify status summary updates

Summary section updates to show "0 verified", "1 rejected", "3 pending" with accurate counts

Updated count display

Multiple status tracking verification

Verification Points

Primary_Verification: Document successfully rejected, status changes to "Rejected" with red indicator, and summary counts update correctly to show "0 verified", "1 rejected", "3 pending"

Secondary_Verifications:Validation message for document rejection Negative_Verification: rejection doesn't affect other documents


Test Case 5: Requirements Checklist Validation

Test Case Metadata

Test Case ID: CIS01US04_TC_005
Title: Verify Requirements Checklist validation for application acceptance
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Business Logic
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Critical, Requirements-Validation, HappyPath, BxServices

Business Context

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

Coverage Tracking

Feature_Coverage: Complete Requirements Validation and Application Acceptance
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice,
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Quality-Dashboard, Business-Logic-Coverage
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Document verification system, payment processing system, business rules engine
Performance_Baseline: Requirements validation < 1 second, application acceptance < 3 seconds
Data_Requirements: All 4 documents available for verification, payment details configured

Prerequisites

Setup_Requirements: Application with all 4 required documents uploaded
User_Roles_Permissions: Customer Executive with application acceptance permissions
Test_Data: Identity Proof, Property Document, Utility Bill, Application Form all available for verification
Prior_Test_Cases: NSC_TC_002 - Document display successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Verify all 4 documents as valid by clicking "Verify" for each

Mark Identity Proof, Property Document, Utility Bill, Application Form as "Verified" with green checkmarks

All 4 core documents

Complete document verification process

2

Check Requirements Checklist status after all documents verified

"All documents verified" shows orange icon, "No rejected documents" shows red cross mark”, "Service location verified" shows green checkmark

Requirements checklist completion

All requirements properly met indication

3

Verify Payment Details section display

Section shows Amount: $150.00, Payment Option: Pay Later, Payment Mode: Credit Card, Payment Status: Pending with clear formatting

Payment information display

Financial validation information

4

Verify application action buttons availability

"Accept Application" button enabled and highlighted in green "Reject Application" available

Action button states

Business rule enforcement for acceptance

5

Test "Accept Application" button when requirements incomplete

Button disabled (grayed out) when any requirement not met

Incomplete requirements state

Button state responds to requirements

6

Click "Accept Application" with all requirements met

Application status changes to "Accepted", workflow progresses to next stage (Site Inspection)

Application acceptance processing

Successful workflow progression

7

Verify workflow progression indicator

Application Review shows completed (green checkmark), Site Inspection becomes active and accessible

Workflow progression display

Visual workflow advancement

Verification Points

Primary_Verification: All requirements checklist items show as completed (green checkmarks) when documents are verified: "All documents verified", "No rejected documents", "Service location verified", and "Accept Application" button becomes enabled only when all criteria met

Secondary_Verifications: Payment details displayed correctly with Amount ($150.00), Payment Option (Pay Later), Payment Mode (Credit Card), Payment Status (Pending), workflow progression occurs properly after acceptance

Negative_Verification: "Accept Application" button disabled when requirements incomplete, cannot proceed to next workflow stage without meeting all requirements, rejected documents prevent application acceptance, incomplete payment information blocks acceptance

Test Case 6: Consumer Number Auto-Generation

Test Case Metadata

Test Case ID: CIS01US04_TC_006
Title: Verify Consumer Number auto-generation follows APP-YYYYMMDD-XXX format
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Business Logic
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Automated

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Auto-Generation,HappyPath,

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: Low
Expected_Execution_Time: 3 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: Critical

Coverage Tracking

Feature_Coverage: Consumer Number Auto-Generation and Format Validation
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: Engineering
Report_Categories: Business-Logic-Coverage, Number-Generation
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Application creation system, number generation service
Performance_Baseline: Number generation < 500ms
Data_Requirements: Customer information for new application creation

Prerequisites

Setup_Requirements: System configured for new application creation
User_Roles_Permissions: Customer Executive with application creation access
Test_Data: Customer information: Sarah Johnson, service address, contact details
Prior_Test_Cases: User authentication successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Create new application on June 15, 2023

Consumer number auto-generated following APP-20230615-001 pattern

New application creation on 2023-06-15

Number generation trigger verification

2

Verify consumer number format compliance

Generated number exactly matches APP-YYYYMMDD-XXX pattern (APP-20230615-001)

Generated number: APP-20230615-001

Format validation against requirement

3

Create second application same day

Consumer number increments sequentially to APP-20230615-002

Second application same date

Sequential numbering validation

4

Create application on different date (June 16, 2023)

Consumer number resets daily sequence: APP-20230616-001

Different date: 2023-06-16

Date-based sequence reset verification

5

Verify number appears in Account Information panel

Consumer Number field displays generated number prominently

Account Information panel display

Number visibility in UI

6

Verify number uniqueness across multiple applications

Each application has unique consumer number, no duplicates generated

Multiple application creation

Uniqueness guarantee verification

7

Verify number persistence after creation

Consumer number remains unchanged after initial generation

Application save and reload

Data integrity validation

8

Create multiple applications rapidly (stress test)

Sequential numbering maintained without gaps or conflicts

Concurrent application creation

System reliability under load

Verification Points

Primary_Verification: Consumer numbers auto-generated following exact APP-YYYYMMDD-XXX format (e.g., APP-20230615-001) with proper date encoding and sequential numbering

Secondary_Verifications: Sequential numbering increments properly within same day, daily sequence resets appropriately, uniqueness guaranteed across all applications, number persists unchanged after creation

Negative_Verification: No duplicate numbers generated under any circumstances, format never violated even under high load, numbers never change after initial assignment,


Test Case 7: Service and Billing Address Separation

Test Case Metadata

Test Case ID: CIS01US04_TC_007
Title: Verify Service Address displayed separately from Billing Address
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Data Display
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Address-Separation,HappyPath, BxServices

Business Context

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

Quality Metrics

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

Coverage Tracking

Feature_Coverage: Address Separation Display and Consistency
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Data-Display-Coverage, Address-Management
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Address management system, contact information service
Performance_Baseline: Address display load < 1 second
Data_Requirements: Application with distinct service and billing addresses

Prerequisites

Setup_Requirements: Application with different service and billing addresses configured
User_Roles_Permissions: Customer Executive with address viewing access
Test_Data: Service Address: 123 Main Street, Anytown, AT 12345; Billing Address: 456 Billing St, Finance City, FC 56789
Prior_Test_Cases: NSC_TC_001 - Information panels display successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Contact Information panel in Application Review tab

Panel displays with clearly separated address sections

Contact Information panel access

Address panel visibility verification

2

Verify Service Address section display

Shows labeled "Service Address: 123 Main Street, Anytown, AT 12345" with distinct formatting

Service address: 123 Main Street, Anytown, AT 12345

Service address proper labeling

3

Verify Billing Address section display

Shows labeled "Billing Address: 456 Billing St, Finance City, FC 56789" with distinct formatting

Billing address: 456 Billing St, Finance City, FC 56789

Billing address proper labeling

4

Verify address separation and distinction

Service and billing addresses clearly distinguished with separate labels and visual separation

Address distinction verification

Clear visual separation requirement

5

Verify complete address format display

Each address includes street, city, state, ZIP code in proper format

Complete address formatting

Full address information display

6

Test with identical service and billing addresses

Both sections show same address but remain visually separate with distinct labels

Identical addresses: 123 Main Street, Anytown, AT 12345

Same address handling verification

7

Verify address consistency in Site Inspection

Service address correctly used for inspection location display

Site inspection address consistency

Address usage across workflows

8

Verify address consistency in Installation

Service address used for meter installation location

Installation address consistency

Service address propagation

Verification Points

Primary_Verification: Service and billing addresses displayed as separate, clearly labeled sections with complete address information (street, city, state, ZIP code)

Secondary_Verifications: Visual separation maintained between address types, service address consistently used across Site Inspection and Installation workflows, proper formatting for both identical and different addresses

Negative_Verification: Addresses not confused or merged inappropriately,labels always present and accurate


Test Case 8: Workflow Progress Indicator and Stage Restrictions

Test Case Metadata

Test Case ID: CIS01US04_TC_008
Title: Verify workflow progress indicator and stage access restrictions
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Business Logic
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Workflow-Management, HappyPath

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

Coverage Tracking

Feature_Coverage: Workflow Progress Tracking and Stage Access Control
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Workflow-Coverage, Access-Control
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Workflow management system, access control service
Performance_Baseline: Workflow state check < 500ms
Data_Requirements: New application in initial pending state

Prerequisites

Setup_Requirements: New application created in initial workflow state
User_Roles_Permissions: Customer Executive with workflow navigation permissions
Test_Data: New application APP-20230616-001 in initial state
Prior_Test_Cases: Application creation successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to new application in pending state

Workflow progress indicator shows Application Review as active (highlighted), other 4 stages (Site Inspection, Approval, Installation, Activation, )grayed out and inactive

Test progress indicator shows Application Review as active (highlighted), other 4 stages (Site Inspection, Approval, Installation, Activation, )grayed out 

Initial workflow state validation

2

Attempt to click Site Inspection tab

Tab is disabled/non-clickable 

Stage access restriction test

Business rule enforcement verification

3

Complete Application Review process by accepting application

Accept application after verifying all documents and meeting requirements

Application acceptance workflow

Stage completion process

4

Verify workflow progression after acceptance

Application Review shows completed (green checkmark), Site Inspection becomes active and clickable

Workflow progression validation

Visual progress advancement

5

Navigate between accessible stages

Can navigate between completed Application Review and current Site Inspection stage only

Navigation control testing

Access management verification

6

Test stage completion visual indicators

Completed stages show green checkmarks, current stage highlighted, future stages remain grayed

Visual indicator accuracy

Status representation verification

7

Verify stage restriction persistence after page refresh

Even after refreshing the page, the system still follows all stage rules — like which steps are allowed or locked 

Page refresh testing

State persistence validation

Verification Points

Primary_Verification: Users cannot access future workflow stages (Site Inspection, Approval, Installation, Activation)until current stage (Application Review) requirements are satisfied, with proper visual indicators showing accessible vs restricted stages

Secondary_Verifications: Visual indicators accurately reflect stage completion status with green checkmarks for completed stages, current stage highlighted, navigation allowed only between completed and current stages

Negative_Verification: future stages never become accidentally accessible



Test Case 09: Site Inspection Scheduling Functionality

Test Case Metadata

Test Case ID: CIS01US04_TC_009
Title: Verify Site Inspection scheduling with WX Dispatcher integration
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Integration
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Integration, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, WX-Integration, WxServices, HappyPath,

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: High
Expected_Execution_Time: 6 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: High

Coverage Tracking

Feature_Coverage: Site Inspection Scheduling and WX Integration
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
 

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Integration-Coverage, External-System-Testing
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: WX Dispatcher system, service order templates, mapping service
Performance_Baseline: WX integration call < 3 seconds
Data_Requirements: Accepted application ready for site inspection

Prerequisites

Setup_Requirements: Application accepted and progressed to Site Inspection stage
User_Roles_Permissions: Customer Executive with site inspection scheduling permissions
Test_Data: Accepted application with service address: 123 Main Street, Anytown, AT 12345
Prior_Test_Cases: NSC_TC_005 - Application acceptance successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Site Inspection tab after application acceptance

Site Inspection Scheduling section displays with service order selection interface

Site Inspection tab access

Second workflow stage accessibility

2

Click "Select service order" dropdown

Dropdown opens showing available service order templates from WX system with searchable interface

WX service order templates

WX Dispatcher integration verification

3

Select service order from dropdown

Service order selected and displayed: "Residential Service Order #RS-2023-1234"

Service order: RS-2023-1234

Template selection functionality

4

Select inspection date using date picker

Date picker opens allowing future date selection with calendar interface

Inspection date: June 20, 2023

Future date validation and selection

5

Enter special instructions in text area

Text area accepts special instructions with character limit display

"Customer prefers morning appointment, dog on property"

Additional inspection notes capability

6

Verify Service Location card display

Card shows map placeholder, Address: 123 Main Street, Anytown, AT 12345, Location Type: Residential, GPS: 40.7128° N, 74.0060° W

Service location details

Address and location verification

7

Click "Schedule Inspection" button

Inspection successfully scheduled in WX Dispatcher, work order created, confirmation message displayed

Inspection scheduling action

External system integration success

8

Verify work order creation in WX system

Work order appears in WX Dispatcher with correct customer and location details

WX work order verification

End-to-end integration validation

9

Verify workflow progression after scheduling

Site Inspection stage shows as in-progress, next stage becomes accessible

Workflow status update

Stage progression verification

Verification Points

Primary_Verification: Site inspection successfully scheduled with selected service order and date, work order created in WX Dispatcher system with correct customer and location information

Secondary_Verifications: Service location details displayed accurately with map and GPS coordinates, special instructions captured and transmitted to WX system, workflow progresses appropriately after scheduling

Negative_Verification: Cannot schedule inspection without required fields (service order, date), invalid dates rejected, WX integration failures handled gracefully with error messages, duplicate scheduling prevented


Test Case 10: Application Notes and Team Communication

Test Case Metadata

Test Case ID: CIS01US04_TC_010
Title: Verify Application Notes functionality for team communication
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Communication
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Team-Communication, HappyPath

Business Context

Customer_Segment: All
Revenue_Impact: Medium
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: Medium
Failure_Impact: High

Coverage Tracking

Feature_Coverage: Application Notes and Team Communication
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Communication-Coverage, Audit-Trail
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: User management system, audit logging service
Performance_Baseline: Note creation < 2 seconds
Data_Requirements: Active application with user session

Prerequisites

Setup_Requirements: User logged in as Customer Executive with active application
User_Roles_Permissions: Customer Executive with note creation and viewing permissions
Test_Data: Application APP-20230615-001, User: Chris Scott - Customer Service Engineer
Prior_Test_Cases: Application access successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Application Review tab and locate Application Notes section

Application Notes section visible at bottom of tab with "Add Note" button

APP-20230615-001 notes section

Notes panel display verification

2

Verify notes section header and interface

Shows "Application Notes" header with add note button and notes history area

Notes section interface

Team communication area setup

3

Click "Add Note" button

Note creation dialog or inline editor opens with text area and save/cancel options

Add note action

Note creation interface access

4

Enter note content in text area

Text area accepts input with character count and formatting options

"Customer requested morning inspection due to work schedule"

Note content entry capability

5

Click "Save" or "Add" to submit note

Note appears in chronological list with user attribution and timestamp

Note submission process

Note persistence verification

6

Verify note display format and attribution

Shows: "Chris Scott - Customer Service Engineer" with timestamp and note content

Note display: user attribution + timestamp

User identification display

7

Add second note with different user context

Second note added with different user attribution if multiple users available

Switch user or simulate different user

Multi-user notes capability

8

Verify chronological ordering of notes

Latest note appears at top of list in reverse chronological order (newest first)

Note ordering verification

Timeline functionality validation

9

Verify note history preservation across workflow stages

Navigate to different tabs and return - all notes remain visible

Note persistence testing

Historical tracking verification

10

Test note character limits and validation

System handles long notes appropriately, validates empty notes

Long note content testing

Input validation verification

Verification Points

Primary_Verification: Application notes successfully created with proper user attribution showing "Chris Scott - Customer Service Engineer" format, timestamps accurate, and chronological ordering maintained

Secondary_Verifications: Notes persist across workflow stages and page refreshes, multi-user support functional with distinct user attribution, note creation interface intuitive and responsive

Negative_Verification: Cannot create empty notes, character limits enforced appropriately, notes never lose attribution or timestamps, note history never corrupted or lost


Test Case 11: Timeline Chronological Progression Display

Test Case Metadata

Test Case ID: CIS01US04_TC_011
Title: Verify Timeline displays chronological progression of application workflow
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Workflow
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Timeline-Tracking, HappyPath

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

Coverage Tracking

Feature_Coverage: Timeline Progression Tracking and Workflow History
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
Cross_Platform_Support: Web

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Workflow-Coverage, Timeline-Tracking
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Workflow tracking system, audit system
Performance_Baseline: Timeline load < 2 seconds
Data_Requirements: Application with multiple completed workflow stages

Prerequisites

Setup_Requirements: Application with document verification and site inspection completed
User_Roles_Permissions: Customer Executive with timeline viewing access
Test_Data: Application with completed stages: submission, document verification, site inspection
Prior_Test_Cases: Document verification and site inspection completed

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Application Overview/Timeline section

Timeline panel displays prominently showing application progress history

Timeline section access

Timeline visibility verification

2

Verify timeline header and layout

Shows "Timeline" header with clear visual timeline layout and progress indicators

Timeline header display

Section identification and layout

3

Verify completed timeline entries display

Shows historical entries: "Application submitted - Jun 15, 2023 2:30 PM", "Document verification - Jun 16, 2023 10:15 AM", "Site inspection - Jun 20, 2023 9:00 AM"

Historical timeline data

Completed steps accurate display

4

Verify pending timeline entries

Shows future entries: "Final approval (Pending)" with estimated date or status indicator

Pending timeline items

Future steps visibility

5

Verify timeline entry format consistency

Each entry shows icon, action description, date/time stamp, and status indicator with consistent formatting

Timeline entry formatting

Consistent display standards

6

Perform new workflow action (approve application)

Timeline immediately updates with new entry showing approval action and timestamp

Approval action execution

Real-time timeline updates

7

Verify chronological ordering accuracy

Entries displayed in reverse chronological order with newest entries at top

Timeline ordering verification

Logical sequence maintenance

8

Verify status indicators accuracy

Completed entries show green checkmark icons, pending show orange clock icons, current shows highlighted indicator

Status indicator verification

Visual status representation

9

Verify timeline persistence after page refresh

Timeline entries remain consistent and accurate after browser refresh

Timeline persistence testing

Data reliability verification

10

Test timeline with multiple rapid actions

Add multiple notes or actions quickly - timeline updates accurately

Rapid action testing

Real-time update reliability

Verification Points

Primary_Verification: Timeline accurately reflects complete chronological progression of application workflow stages with proper timestamps: "Application submitted - Jun 15, 2023 2:30 PM", "Document verification - Jun 16, 2023 10:15 AM", "Site inspection - Jun 20, 2023 9:00 AM"

Secondary_Verifications: Real-time updates occur when new actions performed, chronological ordering maintained in reverse order (newest first), status indicators accurate with green checkmarks for completed and orange clocks for pending

Negative_Verification: No duplicate timeline entries created, no missing workflow steps in timeline, timeline never shows incorrect timestamps, status indicators never misrepresent actual status



Test Case 12: Payment Details Display and Validation

Test Case Metadata

Test Case ID: CIS01US04_TC_012
Title: Verify Payment Details section display and validation for application acceptance
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Business Logic
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Planned-for-Automation

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Critical, Payment-Validation, BxServices , Negative

Business Context

Customer_Segment: All
Revenue_Impact: Critical
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: Payment Details Display and Financial Validation
Integration_Points:Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Financial-Validation-Coverage, Payment-Processing
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Payment processing system, financial validation service
Performance_Baseline: Payment validation < 1 second
Data_Requirements: Application with payment details configured

Prerequisites

Setup_Requirements: Application with payment information configured
User_Roles_Permissions: Customer Executive with payment viewing and validation access
Test_Data: Payment Amount: $150.00, Payment Option: Pay Later, Payment Mode: Credit Card, Payment Status: Pending
Prior_Test_Cases: Application Review tab accessible

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Application Review tab Payment Details section

Payment Details section displays with complete payment information layout

Payment Details section access

Financial information panel visibility

2

Verify payment amount display

Shows "Amount: $150.00" with proper currency formatting and clear labeling

Payment amount: $150.00

Amount accuracy and formatting verification

3

Verify payment option display

Shows "Payment Option: Pay Later" clearly labeled with proper formatting

Payment option: Pay Later

Payment timing selection display

4

Verify payment mode display

Shows "Payment Mode: Credit Card" when payment option is configured

Payment mode: Credit Card

Payment method information visibility

5

Verify payment status display

Shows "Payment Status: Pending" with appropriate status indicator color

Payment status: Pending

Current payment processing state

6

Test payment information completeness validation

System validates all required payment fields present before enabling application acceptance

Payment validation check

Financial requirement verification

7

Verify payment details impact on Requirements Checklist

Payment information completeness affects "Accept Application" button enablement state

Requirements integration

Payment validation business rules

8

Test with "Pay Now" payment scenario

Change to "Pay Now" and verify payment mode field becomes mandatory and visible

Pay Now scenario

Payment option handling variation

9

Test with "Pay Later" payment scenario

Verify "Pay Later" shows mode as optional or conditional

Pay Later scenario

Alternative payment handling

10

Verify payment amount formatting for various amounts

Test different amounts: $1,250.50, $50.00, $10,000.00 with proper comma and decimal formatting

Various payment amounts

Currency formatting consistency

11

Test payment validation error handling

Enter invalid payment amounts and verify proper error messages displayed

Invalid amounts: $0, negative values

Error handling validation

Verification Points

Primary_Verification: Payment Details section displays complete information with Amount ($150.00), Payment Option (Pay Later), Payment Mode (Credit Card), Payment Status (Pending) all properly formatted and clearly labeled

Secondary_Verifications: Payment information completeness validation works correctly before application acceptance, different payment scenarios (Pay Now vs Pay Later) handled appropriately, currency formatting consistent for various amounts with proper comma and decimal placement

Negative_Verification: Incomplete payment information prevents application acceptance, payment validation errors display appropriate messages, payment status never misrepresented, amount formatting never shows incorrect values, invalid payment amounts properly rejected


Test Case 13: Comprehensive Audit Trail Management

Test Case Metadata

Test Case ID: CIS01US04_TC_013
Title: Verify comprehensive audit information tracking for all user actions
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Audit
Test Level: System
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Audit, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Audit-Trail, HappyPath

Business Context

Customer_Segment: All
Revenue_Impact: High
Business_Priority: Must-Have
Customer_Journey: Compliance-Critical
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: Complete Audit Information Tracking and User Attribution
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
 

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Audit-Coverage, Compliance-Tracking
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Audit logging system, user management service
Performance_Baseline: Audit log retrieval < 2 seconds
Data_Requirements: Multi-user application workflow with various actions

Prerequisites

Setup_Requirements: Application with multiple user interactions and workflow actions
User_Roles_Permissions: Multiple users with different roles for comprehensive testing
Test_Data: Application created by John Smith, updated by Jane Doe, actions by Chris Scott
Prior_Test_Cases: Multi-user workflow actions completed

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Site Inspection tab

Site Inspection Scheduling section displays with skip option available

Site Inspection stage access

Second workflow stage accessibility

2

Locate and click "Skip Inspection" button

Skip Inspection button clearly visible and clickable

Skip inspection option

Alternative workflow path access

3

Confirm skip inspection action

Confirmation dialog appears asking to confirm skipping inspection

Skip confirmation dialog

User confirmation requirement

4

Confirm skip action in dialog

Workflow progresses directly to Approval stage bypassing inspection scheduling

Skip confirmation

Alternative workflow execution

5

Verify workflow progress indicator update

Site Inspection shows as completed (green checkmark) and Approval stage becomes active

Workflow status display

Visual progress tracking

Verification Points

Primary_Verification: Skip inspection successfully progresses workflow directly from Site Inspection to Approval stage, Site Inspection shows as completed with green checkmark

Secondary_Verifications: Workflow progress indicator updates correctly,

Negative_Verification:


Test Case 14: Service Activation Requirements and Communication Setup

Test Case Metadata

Test Case ID: CIS01US04_TC_014
Title: Verify Service Activation requirements and communication preferences configuration
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Workflow
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Service-Activation, MxServices , HappyPath, CommServices

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: 5 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: High

Coverage Tracking

Feature_Coverage: Service Activation Requirements and Communication Setup
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Activation-Coverage, Communication-Setup
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Communication system, meter management service
Performance_Baseline: Activation page load < 2 seconds
Data_Requirements: Application with completed installation ready for activation

Prerequisites

Setup_Requirements: Application with meter installation completed successfully
User_Roles_Permissions: Customer Executive with service activation permissions
Test_Data: Meter Serial: WM-2023-001, Device No: DEV-W-1234, Installation Date: May 15, 2023
Prior_Test_Cases: Meter installation completion

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Activation tab after installation completion

Service Activation section displays with meter installation completion message

Activation tab access

Final workflow stage availability

2

Verify meter installation completion message

Shows "Meter installation has been completed successfully. The service is ready to be activated."

Installation status confirmation

Prerequisites verification message

3

Verify Water Utility meter information display

Shows "Smart Water Meter (Serial: WM-2023-001), Device No: DEV-W-1234, Status: Active ✓ Connected"

Meter details: WM-2023-001, DEV-W-1234

Installation verification data

4

Check Initial Reading section display

Shows "Reading: 0 gal, Last updated: May 25, 2023" with proper formatting

Initial reading: 0 gal, date: May 25, 2023

Initial meter state information

5

Verify Installation Date information

Shows "May 15, 2023, Installed by: John Smith" with installer attribution

Installation: May 15, 2023, John Smith

Installation audit information

6

Check Activation Requirements checklist

Shows "Communication Method: ☐ (unchecked), Meter Configuration: ☐ (unchecked)" as initial state

Requirements status display

Activation prerequisite tracking

7

Verify Activation Status display

Shows "Pending Requirements" when activation requirements not completed

Activation status: Pending Requirements

Overall activation readiness

8

Check Communication Preferences options

Shows checkboxes for Email, SMS, Phone Call, E-bill, Paper-bill all available for selection

Communication options availability

Customer preference configuration

9

Select communication preferences

Check Email and SMS for service communications, verify selection persistence

Email and SMS selection

Communication method setup

10

Select billing preference

Check E-bill for electronic billing, verify billing method selection

E-bill selection

Billing delivery preference

11

Verify communication method requirement validation

System enforces selection of at least one communication method before activation

Communication validation

Mandatory communication setup

Verification Points

Primary_Verification: Activation requirements displayed with proper validation status showing unchecked Communication Method and Meter Configuration, meter information accurate (WM-2023-001, DEV-W-1234, Active ✓ Connected)

Secondary_Verifications: Communication preferences available (Email, SMS, Phone Call, E-bill, Paper-bill), installation audit information complete (May 15, 2023, John Smith), initial reading properly displayed (0 gal, May 25, 2023)

Negative_Verification: Cannot activate service without selecting required communication preferences, activation status remains "Pending Requirements" until all criteria met, meter configuration cannot be bypassed


Test Case 15: Final Service Activation Completion

Test Case Metadata

Test Case ID: CIS01US04_TC_015
Title: Verify Service Activation completion workflow and final status update
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Workflow
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Critical, Service-Completion, HappyPath, CommServices ,API

Business Context

Customer_Segment: All
Revenue_Impact: Critical
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: Medium
Failure_Impact: Critical

Coverage Tracking

Feature_Coverage: Final Service Activation and Workflow Completion
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice 

Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Completion-Coverage, Revenue-Recognition
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: Critical

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Service management system, communication service, workflow engine
Performance_Baseline: Service activation < 3 seconds
Data_Requirements: Application ready for final activation with all prerequisites met

Prerequisites

Setup_Requirements: Application with all activation requirements configured
User_Roles_Permissions: Customer Executive with service activation completion permissions
Test_Data: Communication preferences selected, meter configuration completed
Prior_Test_Cases: NSC_TC_015 - Activation requirements setup successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Check Communication Method activation requirement

Check "Communication Method" checkbox to mark requirement as completed

Communication Method requirement

Activation prerequisite completion

2

Check Meter Configuration activation requirement

Check "Meter Configuration" checkbox to mark technical requirement as completed

Meter Configuration requirement

Technical requirement fulfillment

3

Verify activation status update after requirements completion

Activation Status changes from "Pending Requirements" to "Completed" or "Ready for Activation"

Status progression display

Requirements satisfaction indication

4

Verify communication preference selection enforcement

System validates that at least one communication method (Email, SMS, Phone) is selected

Communication selection validation

Mandatory communication setup

5

Verify warning message for missing communication preferences

Shows "You must select at least one communication method to proceed with activation" if none selected

Validation warning message

User guidance for requirements

6

Select required communication preferences

Select Email communication and verify system accepts the selection

Email communication selection

Communication method validation

7

Click "Activate Service" button

Service successfully activated, application status changes from current state to "Activated"

Service activation execution

Final completion action

8

Verify workflow completion indicators

All workflow stages show as completed with green checkmarks: Application Review ✓, Site Inspection ✓, Approval ✓, Installation ✓, Activation ✓

Complete workflow status

End-to-end workflow success

9

Verify final application status update

Application header and status displays show "Activated" as final status

Final status: Activated

Revenue recognition trigger

Verification Points

Primary_Verification: Service successfully activated when all requirements met (Communication Method ✓, Meter Configuration ✓, communication preferences selected), application status changes to "Activated"

Secondary_Verifications: All workflow stages show completed with green checkmarks, activation audit trail captures final completion with user attribution, communication preferences properly enforced and validated

Negative_Verification: Cannot activate service without required communication method selected, activation status validation prevents premature completion, workflow completion only occurs after all stages properly finished


Test Case 16: Meter Installation - Schedule New Installation

Test Case Metadata

Test Case ID: CIS01US04_TC_016
Title: Verify Schedule New Installation workflow with WX Dispatcher integration
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Integration
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Integration, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Meter-Installation, MxServices , HappyPath, WxServices , API

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: High
Expected_Execution_Time: 6 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: High

Coverage Tracking

Feature_Coverage: New Meter Installation Scheduling
Integration_Points:Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
 

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Installation-Coverage, WX-Integration
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: WX Dispatcher system, meter management system
Performance_Baseline: WX integration < 3 seconds
Data_Requirements: Approved application ready for installation

Prerequisites

Setup_Requirements: Application approved and progressed to Installation stage
User_Roles_Permissions: Customer Executive with meter installation scheduling permissions
Test_Data: Approved application for installation scheduling
Prior_Test_Cases: Application approval successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Installation tab after application approval

Meter Installation section displays with "Schedule New Installation" selected by default

Installation tab access

Fourth workflow stage accessibility

2

Click "Select service order" dropdown

Dropdown opens showing available installation service order templates from WX system

WX service order templates

Installation order selection

3

Select installation service order

Service order selected and displayed: "Meter Installation Order #MI-2023-5678"

Installation order: MI-2023-5678

Installation template selection

4

Select installation date using date picker

Date picker opens allowing future date selection with calendar interface

Installation date: June 25, 2023

Future date validation

5

Enter special instructions in text area

Text area accepts installation-specific notes with character validation

"Standard water meter installation, access via side gate"

Installation specific notes

6

Enter latest meter reading value

Numeric field accepts initial reading value with decimal support

Initial reading: "0"

Initial meter reading setup

7

Select reading date using date picker

Date picker for reading date accepts selected date

Reading date: June 25, 2023

Reading timestamp capture

8

Click "Schedule Installation" button

Installation work order created in WX Dispatcher, confirmation message displayed

Installation scheduling action

External system integration

9

Verify Installation Schedule summary display

Shows scheduled installation details in right panel with complete information

Installation confirmation summary

Installation summary verification

10

Verify work order creation in WX Dispatcher

Work order appears in WX system with correct installation details

WX work order verification

End-to-end integration validation

Verification Points

Primary_Verification: New installation successfully scheduled with work order creation in WX Dispatcher, service order "MI-2023-5678" selected, installation date June 25, 2023

Secondary_Verifications: Latest reading (0) and reading date (June 25, 2023) captured correctly, installation summary displayed in right panel, special instructions transmitted to WX system

Negative_Verification: Cannot schedule without required fields (service order, date, reading), invalid dates rejected, WX integration failures handled with error messages, duplicate installations prevented

Test Case 17 : Meter Installation - Assign Existing Meter

Test Case Metadata

Test Case ID: CIS01US04_TC_017
Title: Verify Assign Existing Meter workflow with meter search and selection
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Integration
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Integration, Platform-Web, Report-QA, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Meter-Assignment, MxServices, HappyPath, API

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: High
Expected_Execution_Time: 7 minutes
Reproducibility_Score: High
Data_Sensitivity: Medium
Failure_Impact: High

Coverage Tracking

Feature_Coverage: Existing Meter Assignment and Multi-Utility Support
Integration_Points: Service-CX, API , Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete
 

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Meter-Management-Coverage, Multi-Utility-Support
Trend_Tracking: Yes
Executive_Visibility: Yes
Customer_Impact_Level: High

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Meter management system, utility service databases
Performance_Baseline: Meter search < 2 seconds, assignment < 3 seconds
Data_Requirements: Available meters in inventory for assignment

Prerequisites

Setup_Requirements: Application approved with available meters in inventory
User_Roles_Permissions: Customer Executive with meter assignment permissions
Test_Data: Available meters: WM-2023-001, WM-2023-002 with device numbers
Prior_Test_Cases: Application approval successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select "Assign Existing Meter" radio button

Interface switches to meter assignment view with utility tabs displayed

Meter assignment option

Alternative installation method

2

Verify utility service tabs display

Water Utility and Electric Utility tabs displayed and functional

Multi-utility tabs

Multi-utility service support

3

Click Water Utility tab

Water meter search and selection interface displayed with search functionality

Water utility service

Utility-specific meter interface

4

Use search bar to search for available meters

Search by meter number functionality works with partial matching

Search term: "WM-2023"

Meter search capability

5

Verify available meters list display

List shows available meters: Meter No: WM-2023-001, Device No: DEV-W-1234, Installed On: May 15, 2023, Status: Active, Action: Select

Available meter inventory

Meter availability display

6

Select meter WM-2023-002 from list

Meter details populate in "Selected Water Meter Details" section

Selected meter: WM-2023-002

Specific meter selection

7

Verify selected meter details display

Meter Number: WM-2023-002, Device Number: DEV-W-2345 displayed correctly

Meter details confirmation

Selection confirmation display

8

Enter latest meter reading

Reading field accepts numeric value with decimal precision

Current reading: "150.5"

Current meter reading capture

9

Select reading date using date picker

Date picker for current reading date accepts selection

Reading date: June 25, 2023

Reading timestamp capture

10

Click "Assign Meter" button

Meter successfully assigned to customer account with confirmation message

Meter assignment action

Account linking completion

11

Verify meter assignment confirmation

System confirms meter WM-2023-002 assigned to application with reading data

Assignment confirmation

Assignment success verification

Verification Points

Primary_Verification: Existing meter WM-2023-002 successfully assigned to customer account with reading data (150.5, June 25, 2023), meter search functions correctly by meter number

Secondary_Verifications: Selected meter details (WM-2023-002, DEV-W-2345) displayed accurately, multi-utility tabs functional, meter inventory shows available meters with correct status

Negative_Verification: Cannot assign meter without reading and date, already assigned meters not available for selection, invalid reading values rejected, meter assignment prevents double assignment


Test Case 18: Site Inspection 

Test Case Metadata

Test Case ID: CIS01US04_TC_018
Title: Verify Skip Inspection functionality and workflow progression
Created By: Hetal
Created Date: 2025-06-09
Version: 1.0

Classification

Module/Feature: New Connection Application Detail View
Test Type: Functional/Workflow
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Manual

Enhanced Tags

Tags: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Workflow-Skip, HappyPath, API

Business Context

Customer_Segment: All
Revenue_Impact: Medium
Business_Priority: Should-Have
Customer_Journey: Alternative-Workflow
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: Skip Inspection Alternative Workflow Path
Integration_Points: Service-CX, API ,Happy path
Code_Module_Mapped: CX-Backoffice
Requirement_Coverage: Complete

Stakeholder Reporting

Primary_Stakeholder: QA
Report_Categories: Alternative-Workflow-Coverage, Business-Logic
Trend_Tracking: Yes
Executive_Visibility: No
Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

Environment: Staging
Browser/Version: Chrome 115+,
Device/OS: Windows 10/11,
Screen_Resolution: Desktop-1920x1080, Tablet-1024x768
Dependencies: Workflow management system, business rules engine
Performance_Baseline: Workflow skip operation < 1 second
Data_Requirements: Accepted application ready for site inspection stage

Prerequisites

Setup_Requirements: Application accepted and progressed to Site Inspection stage
User_Roles_Permissions: Customer Executive with inspection skip permissions
Test_Data: Accepted application APP-20230617-001 in Site Inspection stage
Prior_Test_Cases: NSC_TC_005 - Application acceptance successful

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Site Inspection tab from accepted application

Site Inspection Scheduling section displays with both scheduling options and skip option available

Site Inspection stage access

Second workflow stage accessibility verification

2

Locate "Skip Inspection" button on the interface

Skip Inspection button clearly visible, properly labeled, and clickable

Skip inspection button

Alternative workflow path access point

3

Click "Skip Inspection" button

Confirmation dialog box appears asking "Are you sure you want to skip the site inspection? This action cannot be undone."

Skip confirmation dialog

User confirmation requirement for irreversible action

4

Click "Cancel" in confirmation dialog

Dialog closes and remains on Site Inspection stage without any changes

Cancel action

Confirmation dialog cancel functionality

5

Click "Skip Inspection" button again

Confirmation dialog appears again with same warning message

Skip confirmation repeat

Consistent confirmation behavior

6

Click "Confirm" or "Yes" to skip inspection

Workflow immediately progresses to Approval stage, bypassing inspection scheduling completely

Skip confirmation execution

Alternative workflow path execution

7

Verify workflow progress indicator visual update

Site Inspection stage shows as completed with green checkmark and Approval stage becomes active/highlighted

Workflow status display update

Visual progress tracking accuracy

8

Navigate to Approval tab to verify accessibility

Approval section displays without any inspection results or inspection-related requirements

Approval stage without inspection

Conditional approval process functionality

9

Verify Approval tab shows skipped inspection status

Approval requirements section shows "Site inspection: Skipped" or similar indicator

Skipped inspection indicator

Skip status visibility in approval

10

Verify approval functionality works despite skipped inspection

Approval decision options (Approve/Reject) available and functional

Approval functionality validation

Skip doesn't block subsequent approval

11

Navigate back to Site Inspection tab

Site Inspection tab shows "Inspection Skipped" status and no longer allows scheduling

Site Inspection final state

Irreversible skip confirmation

12

Test workflow stage navigation restrictions

Can navigate between completed Application Review, skipped Site Inspection, and current Approval stages only

Stage navigation verification

Proper stage access control maintained

Verification Points

Primary_Verification: Skip inspection functionality successfully progresses workflow directly from Site Inspection to Approval stage, Site Inspection shows as completed with green checkmark, and Approval stage becomes accessible without inspection data

Secondary_Verifications: Workflow progress indicator updates correctly showing skipped status, Approval section displays and functions properly without inspection results, confirmation dialog prevents accidental skipping, stage navigation works correctly with skipped stage

Negative_Verification: Skipped inspection doesn't block subsequent approval process, workflow integrity maintained despite skipped stage, skip action is irreversible once confirmed, no required inspection data causes approval failures, cannot schedule inspection after skipping

No Comments
Back to top