Skip to main content

Service & Support Management (CSS01US08)

Total test cases - 60

Total Acceptance criteria- 60

Total Coverage -100%



Test Case 1: Display Five Service Request Types on Main Portal

Test Case Metadata

  • Test Case ID: CSS01US08_TC_001
  • Title: Verify system displays all five service request types clearly on main portal page
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Customer portal, Service catalog
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Service request types configuration

Prerequisites

  • Setup_Requirements: Customer portal configured with service types
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Customer account: customer@utilitycompany.com
  • Prior_Test_Cases: None

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Service & Support section

Service & Support page loads



2

Count service request cards displayed

Exactly 5 service request cards visible


Count validation

3

Verify Service Request card displayed

Card visible with proper title

Service Request

Card 1

4

Verify Register Complaint card displayed

Card visible with proper title

Register Complaint

Card 2

5

Verify Request Transfer card displayed

Card visible with proper title

Request Transfer

Card 3

6

Verify Request Disconnection card displayed

Card visible with proper title

Request Disconnection

Card 4

7

Verify Request Reconnection card displayed

Card visible with proper title

Request Reconnection

Card 5

Verification Points

  • Primary_Verification: All 5 service request types displayed clearly on main portal
  • Secondary_Verifications: Cards have proper titles and are clearly visible
  • Negative_Verification: No additional or missing service request cards



Test Case 2: Authentication Required Before Request Submission

Test Case Metadata

  • Test Case ID: CSS01US08_TC_002
  • Title: Verify system requires user authentication before allowing request submission
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Security/Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Auth Services, Security, MOD-ServiceSupport, P1-Critical, Phase-Smoke, Type-Security, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Point, Happy path

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: 2% of feature covered
  • Integration_Points: CxServices, API, Auth Services
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Authentication service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Valid user credentials

Prerequisites

  • Setup_Requirements: Authentication service configured
  • User_Roles_Permissions: Unauthenticated user
  • Test_Data: Valid credentials: customer@utilitycompany.com / Test@123
  • Prior_Test_Cases: None

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Access portal without authentication

Redirected to login page


Unauthenticated access

2

Try to access service request directly

Access denied, redirected to login


URL manipulation test

3

Enter valid credentials

Authentication successful

customer@utilitycompany.com / Test@123

Valid login

4

Access Service & Support section

Access granted, page loads


Authenticated access

5

Verify service request cards are accessible

All cards functional


Post-auth functionality

Verification Points

  • Primary_Verification: Authentication required before any request submission
  • Secondary_Verifications: Direct URL access blocked without authentication
  • Negative_Verification: Unauthenticated users cannot access service request functionality



Test Case 3: Generate Unique Tracking IDs for All Requests

Test Case Metadata

  • Test Case ID: CSS01US08_TC_003
  • Title: Verify system generates unique tracking IDs for all submitted requests
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, API, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Integration-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Database, ID generation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Multiple request submissions

Prerequisites

  • Setup_Requirements: ID generation service configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various request types data
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit first service request

Unique tracking ID generated

Service: Water Repair

ID 1

2

Submit second service request

Different unique tracking ID generated

Service: Meter Check

ID 2

3

Submit complaint

Unique complaint reference generated

Category: Billing

ID 3

4

Submit transfer request

Unique transfer ID generated

Type: Account Transfer

ID 4

5

Submit disconnection request

Unique disconnection ID generated

Reason: Moving

ID 5

6

Submit reconnection request

Unique reconnection ID generated

Reason: Service Restoration

ID 6

7

Verify all IDs are unique

No duplicate IDs found


Database verification

Verification Points

  • Primary_Verification: All submitted requests generate unique tracking IDs
  • Secondary_Verifications: IDs are properly stored and retrievable
  • Negative_Verification: No duplicate IDs generated under any circumstances



Test Case 4: Display Exactly 5 Service Request Cards

Test Case Metadata

  • Test Case ID: CSS01US08_TC_004
  • Title: Verify system displays exactly 5 service request cards with specified names
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service catalog configuration
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Service request cards configuration

Prerequisites

  • Setup_Requirements: Service request cards configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Expected card names list
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Service & Support page

Page loads successfully



2

Count total number of service cards

Exactly 5 cards displayed


Count = 5

3

Verify "Service Request" card exists

Card found with exact name

Service Request

Card 1 verification

4

Verify "Register Complaint" card exists

Card found with exact name

Register Complaint

Card 2 verification

5

Verify "Request Transfer" card exists

Card found with exact name

Request Transfer

Card 3 verification

6

Verify "Request Disconnection" card exists

Card found with exact name

Request Disconnection

Card 4 verification

7

Verify "Request Reconnection" card exists

Card found with exact name

Request Reconnection

Card 5 verification

Verification Points

  • Primary_Verification: Exactly 5 service request cards displayed with specified names
  • Secondary_Verifications: Card names match requirements exactly
  • Negative_Verification: No additional cards displayed beyond the required 5



Test Case 5: Authentication Required Before Any Request Submission

Test Case Metadata

  • Test Case ID: CSS01US08_TC_005
  • Title: Verify system requires user authentication before allowing any request submission
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Security/Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Auth Services, Security, MOD-ServiceSupport, P1-Critical, Phase-Smoke, Type-Security, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Point, Happy path

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: 2% of feature covered
  • Integration_Points: CxServices, API, Auth Services
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Authentication service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Valid authentication credentials

Prerequisites

  • Setup_Requirements: Authentication service configured
  • User_Roles_Permissions: Mixed (authenticated and unauthenticated)
  • Test_Data: Valid/invalid credentials
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Try to access service request without auth

Authentication required message


Unauthenticated test

2

Try to access complaint form without auth

Authentication required message


Unauthenticated test

3

Try to access transfer request without auth

Authentication required message


Unauthenticated test

4

Try to access disconnection request without auth

Authentication required message


Unauthenticated test

5

Try to access reconnection request without auth

Authentication required message


Unauthenticated test

6

Login with valid credentials

Authentication successful

customer@utilitycompany.com / Test@123

Valid authentication

7

Verify all request types accessible

All forms accessible post-authentication


Post-auth verification

Verification Points

  • Primary_Verification: Authentication required before any request submission
  • Secondary_Verifications: All request types protected by authentication
  • Negative_Verification: No request type accessible without authentication



Test Case 6: Generate Unique Tracking IDs with Specified Formats

Test Case Metadata

  • Test Case ID: CSS01US08_TC_006
  • Title: Verify system generates unique tracking IDs following specified formats
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, API, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Integration-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: ID generation service, Database
  • Performance_Baseline: < 1 second
  • Data_Requirements: Request submission data

Prerequisites

  • Setup_Requirements: ID generation service with format rules
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various request types
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit service request

ID generated in SR-###### format

Service: Water Repair

Format: SR-000001

2

Verify service request ID format

Matches SR-###### pattern


6-digit verification

3

Submit complaint

Complaint reference number generated

Category: Billing

Unique format

4

Verify complaint ID format

Matches complaint reference format


Format verification

5

Submit transfer request

Transfer ID generated

Type: Account Transfer

Unique format

6

Submit disconnection request

Disconnection ID generated

Reason: Moving

Unique format

7

Submit reconnection request

Reconnection ID generated

Reason: Service Restoration

Unique format

8

Verify all formats are unique and correct

All IDs follow specified formats


Format compliance

Verification Points

  • Primary_Verification: All tracking IDs follow specified formats (SR-###### for service requests)
  • Secondary_Verifications: Complaint reference numbers have unique format
  • Negative_Verification: No IDs generated outside of specified formats



Test Case 7: Enforce Mandatory 4-Step Process Workflow

Test Case Metadata

  • Test Case ID: CSS01US08_TC_007
  • Title: Verify system enforces mandatory 4-step process workflow for all requests
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, Integration, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-End-to-End, Happy path

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: 8 minutes
  • Reproducibility_Score: High
  • Data_Sensitivity: Medium
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, WorkflowEngine
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Workflow engine, Backend services
  • Performance_Baseline: < 2 seconds per step
  • Data_Requirements: Complete request data

Prerequisites

  • Setup_Requirements: Workflow engine configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Service request data
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit service request

Status: Submit (Step 1)

Service: Water Repair

Initial submission

2

Verify request moves to initial review

Status: Initial Review (Step 2)


Workflow progression

3

Complete initial review

Status: Expert Assignment (Step 3)


Step 2 completion

4

Assign to expert

Status: Resolution (Step 4)


Step 3 completion

5

Verify no steps can be skipped

Sequential progression enforced


Skip prevention

6

Test with complaint

Same 4-step process enforced

Category: Billing

Process consistency

7

Test with transfer request

Same 4-step process enforced

Type: Account Transfer

Process consistency

8

Verify workflow completion

All 4 steps completed


End-to-end verification

Verification Points

  • Primary_Verification: Mandatory 4-step workflow enforced for all request types
  • Secondary_Verifications: Steps cannot be skipped, progression is sequential
  • Negative_Verification: No request can bypass any of the 4 mandatory steps



Test Case 8: Provide Save Draft Functionality

Test Case Metadata

  • Test Case ID: CSS01US08_TC_008
  • Title: Verify system provides Save Draft functionality at any stage of all request types
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, UX-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Session management, Database
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Partial form data

Prerequisites

  • Setup_Requirements: Draft functionality enabled
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Partial request data
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Start service request, enter partial data

Data entered successfully

Service: Water Repair

Partial data

2

Click "Save Draft" button

Draft saved successfully


Save functionality

3

Start complaint, enter partial data

Data entered successfully

Category: Billing

Partial data

4

Click "Save Draft" button

Draft saved successfully


Save functionality

5

Start transfer request, enter partial data

Data entered successfully

Type: Account Transfer

Partial data

6

Click "Save Draft" button

Draft saved successfully


Save functionality

7

Start disconnection request, enter partial data

Data entered successfully

Reason: Moving

Partial data

8

Click "Save Draft" button

Draft saved successfully


Save functionality

9

Start reconnection request, enter partial data

Data entered successfully

Reason: Service Restoration

Partial data

10

Click "Save Draft" button

Draft saved successfully


Save functionality

Verification Points

  • Primary_Verification: Save Draft functionality available at any stage of all request types
  • Secondary_Verifications: Drafts are properly saved and retrievable
  • Negative_Verification: No data loss when saving drafts



Test Case 9: Allow Navigation Back to Previous Steps

Test Case Metadata

  • Test Case ID: CSS01US08_TC_009
  • Title: Verify system allows navigation back to previous steps without data loss
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, UX-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Session management
  • Performance_Baseline: < 1 second
  • Data_Requirements: Multi-step form data

Prerequisites

  • Setup_Requirements: Multi-step forms configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete form data
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Start service request, complete step 1

Step 1 completed

Service: Water Repair

Data entry

2

Navigate to step 2, enter data

Step 2 completed

Date: 02/15/2025

Data entry

3

Click "Back" button

Return to step 1 with data intact


Backward navigation

4

Verify step 1 data preserved

All previously entered data visible

Service: Water Repair

Data persistence

5

Navigate forward to step 2

Step 2 displays with preserved data

Date: 02/15/2025

Forward navigation

6

Navigate to step 3, enter data

Step 3 completed

Payment: Online

Data entry

7

Click "Back" button twice

Return to step 1 with all data intact


Multiple back navigation

8

Verify all data preserved

All steps maintain entered data


Data integrity check

Verification Points

  • Primary_Verification: Navigation back to previous steps without data loss
  • Secondary_Verifications: All entered data preserved during navigation
  • Negative_Verification: No data loss when navigating backward



Test Case 10: Persist Form Data When Navigating Between Steps

Test Case Metadata

  • Test Case ID: CSS01US08_TC_010
  • Title: Verify system persists form data when navigating between steps
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, UX-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Session management, Data persistence
  • Performance_Baseline: < 1 second
  • Data_Requirements: Multi-step form data

Prerequisites

  • Setup_Requirements: Data persistence configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete multi-step form data
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Enter data in service request step 1

Data entered and saved

Service: Water Repair, Description: "Low pressure"

Step 1 data

2

Navigate to step 2

Data persists from step 1


Forward navigation

3

Enter data in step 2

Data entered and saved

Date: 02/15/2025, Time: 9:00 AM

Step 2 data

4

Navigate to step 3

Data persists from previous steps


Forward navigation

5

Enter data in step 3

Data entered and saved

Payment: Online Payment

Step 3 data

6

Navigate back to step 1

All data from all steps persists


Backward navigation

7

Verify step 1 data intact

Previously entered data displayed

Service: Water Repair, Description: "Low pressure"

Data verification

8

Navigate through all steps

All data preserved in each step


Complete navigation test

9

Refresh page and verify persistence

Data remains after page refresh


Session persistence

Verification Points

  • Primary_Verification: Form data persists when navigating between steps
  • Secondary_Verifications: Data survives page refreshes and session changes
  • Negative_Verification: No data loss during any navigation action



Test Case 11: Organize Services by Utility Type with Color-Coding

Test Case Metadata

  • Test Case ID: CSS01US08_TC_011
  • Title: Verify system organizes services by utility type with color-coding
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service catalog, UI styling
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Service catalog with utility types

Prerequisites

  • Setup_Requirements: Service catalog configured with utility types
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Services across all utility types
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "Service Request" card

Service selection page loads



2

Verify Water services section

Water services grouped together

Water Pressure Check, Water Quality Test

Category grouping

3

Verify Wastewater services section

Wastewater services grouped together

Sewer Line Inspection, Wastewater Treatment

Category grouping

4

Verify Metering services section

Metering services grouped together

Meter Reading, Meter Replacement

Category grouping

5

Verify Connection services section

Connection services grouped together

New Connection, Service Upgrade

Category grouping

6

Verify Maintenance services section

Maintenance services grouped together

Routine Maintenance, Emergency Repair

Category grouping

7

Verify color-coding for each utility type

Each category has distinct color


Visual verification

8

Verify color consistency within categories

Same color used for all services in category


Color consistency

Verification Points

  • Primary_Verification: Services organized by utility type (Water, Wastewater, Metering, Connection, Maintenance)
  • Secondary_Verifications: Color-coding applied consistently to each utility type
  • Negative_Verification: No services appear in wrong categories



Test Case 12: Display Service Information with Required Fields

Test Case Metadata

  • Test Case ID: CSS01US08_TC_012
  • Title: Verify system displays service name, description, price, and category for each service
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service catalog database
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Complete service information

Prerequisites

  • Setup_Requirements: Service catalog with complete information
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Services with all required fields
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to service selection page

Service selection page loads



2

Verify service name displayed

Service name visible

Water Pressure Check

Field 1

3

Verify service description displayed

Service description visible

"Comprehensive water pressure testing and analysis"

Field 2

4

Verify service price displayed

Service price visible

$75.00

Field 3

5

Verify service category displayed

Service category visible

Water

Field 4

6

Test with different service

All 4 fields visible

Meter Reading - "Monthly meter reading service" - $25.00 - Metering

Different service

7

Verify all services have required fields

All services display 4 required fields


Complete verification

8

Verify field formatting consistency

All fields properly formatted


Formatting check

Verification Points

  • Primary_Verification: All services display name, description, price, and category
  • Secondary_Verifications: Information is properly formatted and readable
  • Negative_Verification: No services missing any of the 4 required fields



Test Case 13: Allow Only Single Service Selection

Test Case Metadata

  • Test Case ID: CSS01US08_TC_013
  • Title: Verify system allows only one service selection at a time with Select button confirmation
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service selection logic
  • Performance_Baseline: < 1 second
  • Data_Requirements: Multiple services available

Prerequisites

  • Setup_Requirements: Service selection functionality enabled
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Multiple services in catalog
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to service selection page

Service selection page loads



2

Select first service

Service highlighted/selected

Water Pressure Check

Selection 1

3

Try to select second service

First service deselected, second service selected

Meter Reading

Single selection

4

Verify only one service selected

Only one service in selected state

Meter Reading

Verification

5

Click "Select" button

Service selection confirmed


Button confirmation

6

Verify selected service confirmed

System acknowledges selection


Confirmation

7

Try to select different service after confirmation

Previous selection maintained


Selection locked

8

Test with multiple rapid selections

Only latest selection maintained


Rapid selection test

Verification Points

  • Primary_Verification: Only one service can be selected at a time
  • Secondary_Verifications: Select button confirmation required
  • Negative_Verification: Cannot select multiple services simultaneously



Test Case 14: Enforce Date Format and Prevent Past Dates

Test Case Metadata

  • Test Case ID: CSS01US08_TC_014
  • Title: Verify system enforces MM/DD/YYYY format and prevents past date selection
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, Validation

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Date validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Date picker functionality

Prerequisites

  • Setup_Requirements: Date validation rules configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various date formats and values
  • Prior_Test_Cases: CSS01US08_TC_013

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to service details step

Service details page loads



2

Click on preferred date field

Date picker opens



3

Enter date in correct format

Date accepted

02/15/2025

MM/DD/YYYY format

4

Try to enter invalid format

Format error displayed

15/02/2025

DD/MM/YYYY format

5

Try to enter another invalid format

Format error displayed

2025-02-15

YYYY-MM-DD format

6

Try to select past date

Past date selection prevented

01/15/2025

Past date

7

Select valid future date

Date accepted successfully

03/15/2025

Future date

8

Verify date format display

Date displays in MM/DD/YYYY format

03/15/2025

Format verification

Verification Points

  • Primary_Verification: MM/DD/YYYY format enforced for preferred date
  • Secondary_Verifications: Past date selection prevented
  • Negative_Verification: Invalid date formats rejected



Test Case 15: Provide Configurable Time Slot Dropdowns

Test Case Metadata

  • Test Case ID: CSS01US08_TC_015
  • Title: Verify system provides configurable time slot dropdowns based on service type and date
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Time slot configuration service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Time slot configuration

Prerequisites

  • Setup_Requirements: Time slots configured for different service types
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Different service types with varying time slots
  • Prior_Test_Cases: CSS01US08_TC_014

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select water service and date

Time slot dropdown enabled

Water Pressure Check, 02/15/2025

Service type 1

2

Click time slot dropdown

Water service time slots displayed

8:00 AM - 10:00 AM, 10:00 AM - 12:00 PM

Service-specific slots

3

Select different service type

Time slot dropdown updates

Meter Reading, 02/15/2025

Service type 2

4

Click time slot dropdown

Meter service time slots displayed

9:00 AM - 11:00 AM, 1:00 PM - 3:00 PM

Different time slots

5

Change date for same service

Time slot dropdown updates

Meter Reading, 02/16/2025

Date-based slots

6

Verify time slots are configurable

Different slots for different configurations


Configuration verification

7

Test with maintenance service

Maintenance-specific time slots displayed

Emergency Repair, 02/15/2025

Service type 3

8

Verify time slot selection

Selected time slot properly saved

8:00 AM - 10:00 AM

Selection verification

Verification Points

  • Primary_Verification: Time slot dropdowns configurable based on service type and date
  • Secondary_Verifications: Different service types have different available time slots
  • Negative_Verification: Time slots properly filtered based on service type and date



Test Case 16: Offer Payment Methods with Mandatory Selection

Test Case Metadata

  • Test Case ID: CSS01US08_TC_016
  • Title: Verify system offers payment methods with mandatory selection requirement
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Point, Happy path

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: High

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Payment method configuration
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Payment method options

Prerequisites

  • Setup_Requirements: Payment methods configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Service with pricing information
  • Prior_Test_Cases: CSS01US08_TC_015

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Payment & Review step

Payment options displayed



2

Verify "Online Payment" option available

Radio button for online payment visible

Online Payment

Option 1

3

Verify "On Service Completion" option available

Radio button for service completion payment visible

On Service Completion

Option 2

4

Try to proceed without selection

Validation error displayed


Mandatory validation

5

Select "Online Payment"

Option selected successfully


Selection 1

6

Verify other option deselected

Only one option selected at a time


Single selection

7

Select "On Service Completion"

Option selected successfully


Selection 2

8

Verify selection is mandatory

Cannot proceed without payment method selection


Mandatory enforcement

Verification Points

  • Primary_Verification: Three payment methods available with mandatory selection
  • Secondary_Verifications: Only one payment method can be selected at a time
  • Negative_Verification: Cannot proceed without payment method selection



Test Case 17: Redirect to Payment Gateway for Online Payment

Test Case Metadata

  • Test Case ID: CSS01US08_TC_017
  • Title: Verify system redirects to payment gateway when online payment is selected
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Integration/Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, Integration, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-External-Dependency, Happy path

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: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, PaymentGateway
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Quality-Dashboard, Integration-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Payment gateway service
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Payment gateway configuration

Prerequisites

  • Setup_Requirements: Payment gateway integrated and configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Service with payment amount: $75.00
  • Prior_Test_Cases: CSS01US08_TC_016

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select "Online Payment" option

Option selected successfully



2

Click "Continue" button

Redirect to payment gateway initiated



3

Verify payment gateway loads

Payment gateway interface displayed


External integration

4

Verify correct amount displayed

Service amount shown correctly

$75.00

Amount verification

5

Verify service details in gateway

Service information passed correctly

Water Pressure Check

Service details

6

Verify customer information passed

Customer details available in gateway

John Doe

Customer info

7

Test payment gateway functionality

Payment interface is functional


Gateway functionality

8

Verify return URL configured

Return path back to portal configured


Return integration

Verification Points

  • Primary_Verification: Online payment selection redirects to payment gateway
  • Secondary_Verifications: Correct amount and service details passed to gateway
  • Negative_Verification: Payment gateway integration works without errors



Test Case 18: Generate Service Request Numbers in SR-###### Format

Test Case Metadata

  • Test Case ID: CSS01US08_TC_018
  • Title: Verify system generates service request numbers in SR-###### format
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, API, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Integration-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: ID generation service, Database
  • Performance_Baseline: < 1 second
  • Data_Requirements: Service request submission

Prerequisites

  • Setup_Requirements: Service request ID generation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete service request data
  • Prior_Test_Cases: CSS01US08_TC_017

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit first service request

Service request submitted successfully

Water Pressure Check

Request 1

2

Verify ID format

ID generated in SR-###### format

SR-000001

Format verification

3

Verify ID is 6 digits

ID contains exactly 6 digits after SR-

000001

Digit count

4

Submit second service request

Service request submitted successfully

Meter Reading

Request 2

5

Verify sequential numbering

ID generated sequentially

SR-000002

Sequential increment

6

Submit third service request

Service request submitted successfully

Pipe Repair

Request 3

7

Verify continued sequence

ID continues sequential pattern

SR-000003

Sequence continuation

8

Verify format consistency

All IDs follow exact SR-###### format

SR-000001, SR-000002, SR-000003

Format consistency

Verification Points

  • Primary_Verification: Service request numbers generated in SR-###### format
  • Secondary_Verifications: Sequential 6-digit numbering maintained
  • Negative_Verification: No IDs generated outside the specified format



Test Case 19: Provide Downloadable/Printable Receipts

Test Case Metadata

  • Test Case ID: CSS01US08_TC_019
  • Title: Verify system provides downloadable/printable receipts with complete service information
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Receipt generation service
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Completed service request

Prerequisites

  • Setup_Requirements: Receipt generation service configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Completed service request: SR-000001
  • Prior_Test_Cases: CSS01US08_TC_018

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Complete service request submission

Service request submitted successfully

Water Pressure Check, SR-000001

Request completion

2

Verify receipt is generated

Receipt displayed on screen


Receipt generation

3

Verify receipt contains service information

Service details displayed

Water Pressure Check, $75.00

Service info

4

Verify receipt contains customer information

Customer details displayed

John Doe, Account: 12345

Customer info

5

Verify receipt contains request ID

Service request number displayed

SR-000001

Request ID

6

Click "Download" button

Receipt downloads as PDF


Download functionality

7

Verify PDF content

Downloaded PDF contains complete information


PDF verification

8

Click "Print" button

Print dialog opens


Print functionality

9

Verify print preview

Print preview shows complete receipt


Print preview

Verification Points

  • Primary_Verification: Receipts are downloadable and printable with complete service information
  • Secondary_Verifications: PDF format maintains all information integrity
  • Negative_Verification: No missing information in downloaded/printed receipts



Test Case 20: Display Next Steps with Specific Timelines

Test Case Metadata

  • Test Case ID: CSS01US08_TC_020
  • Title: Verify system displays next steps with specific timelines
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Timeline configuration
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Timeline information

Prerequisites

  • Setup_Requirements: Timeline information configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Completed service request
  • Prior_Test_Cases: CSS01US08_TC_019

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Complete service request submission

Service request submitted successfully



2

Verify "Next Steps" section displayed

Next steps section visible


Section display

3

Verify email confirmation timeline

"Email confirmation within 24 hours" displayed

24 hours

Timeline 1

4

Verify service rep contact timeline

"Service representative contact within 2-3 business days" displayed

2-3 business days

Timeline 2

5

Verify service completion timeline

"Service completion within 3-5 business days" displayed

3-5 business days

Timeline 3

6

Verify all timelines are specific

All timelines contain specific time frames


Specificity check

7

Verify timelines are for standard requests

Standard request timelines displayed


Standard vs. priority

8

Verify timeline formatting

All timelines properly formatted and readable


Formatting check

Verification Points

  • Primary_Verification: Next steps displayed with specific timelines
  • Secondary_Verifications: Three specific timelines provided (24 hours, 2-3 days, 3-5 days)
  • Negative_Verification: No vague or missing timeline information



Test Case 21: Provide Mandatory Category Dropdown with Dynamic Subcategory Loading

Test Case Metadata

  • Test Case ID: CSS01US08_TC_021
  • Title: Verify system provides mandatory category dropdown with dynamic subcategory loading
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Must-Have
  • Customer_Journey: Support
  • Compliance_Required: Yes
  • SLA_Related: Yes

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: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Complaint category master data
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Category and subcategory data

Prerequisites

  • Setup_Requirements: Complaint categories configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Categories: Billing, Service Quality, Technical Issue
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "Register Complaint" card

Complaint form loads



2

Verify category dropdown is mandatory

Field marked as required


Mandatory field

3

Try to proceed without category

Validation error displayed


Validation check

4

Click category dropdown

Available categories displayed

Billing, Service Quality, Technical Issue

Master data

5

Select "Billing" category

Category selected, subcategory dropdown enabled

Billing

Dynamic loading

6

Verify subcategory dropdown enabled

Subcategory field becomes active


Dynamic behavior

7

Click subcategory dropdown

Billing-related subcategories displayed

Incorrect Charges, Payment Issues, Meter Reading

Filtered data

8

Change to "Service Quality" category

Subcategory dropdown updates with new options

Service Quality

Dynamic update

9

Verify new subcategories loaded

Service Quality subcategories displayed

Water Pressure, Response Time, Service Interruption

Category-specific data

Verification Points

  • Primary_Verification: Category dropdown is mandatory with dynamic subcategory loading
  • Secondary_Verifications: Subcategories filter based on selected category
  • Negative_Verification: Cannot proceed without category selection



Test Case 22: Require Complaint Name Selection Based on Category and Subcategory

Test Case Metadata

  • Test Case ID: CSS01US08_TC_022
  • Title: Verify system requires complaint name selection based on category and subcategory
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Must-Have
  • Customer_Journey: Support
  • Compliance_Required: Yes
  • SLA_Related: Yes

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Complaint master data
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Complaint names by category/subcategory

Prerequisites

  • Setup_Requirements: Complaint names configured by category/subcategory
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complaint names for different category/subcategory combinations
  • Prior_Test_Cases: CSS01US08_TC_021

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select "Billing" category

Category selected successfully

Billing


2

Select "Incorrect Charges" subcategory

Subcategory selected successfully

Incorrect Charges


3

Verify complaint name dropdown enabled

Complaint name field becomes active


Dynamic enabling

4

Click complaint name dropdown

Complaint names for billing/incorrect charges displayed

Overcharged for Usage, Wrong Rate Applied, Duplicate Billing

Filtered complaints

5

Select complaint name

Complaint name selected successfully

Overcharged for Usage

Required selection

6

Change to different subcategory

Complaint name dropdown updates

Payment Issues

Dynamic update

7

Verify new complaint names loaded

Payment-related complaint names displayed

Payment Not Processed, Auto-Pay Failed, Payment Reversal

Updated complaints

8

Try to proceed without complaint name

Validation error displayed


Mandatory validation

9

Verify complaint name is mandatory

Field marked as required


Required field

Verification Points

  • Primary_Verification: Complaint name selection required based on category and subcategory
  • Secondary_Verifications: Complaint names filter dynamically based on selections
  • Negative_Verification: Cannot proceed without complaint name selection



Test Case 23: Prevent Future Dates for Incident Date Field

Test Case Metadata

  • Test Case ID: CSS01US08_TC_023
  • Title: Verify system prevents future dates for incident date field
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, Validation

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Low
  • Business_Priority: Should-Have
  • Customer_Journey: Support
  • 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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Date validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Date picker with validation

Prerequisites

  • Setup_Requirements: Date validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Current date: 01/17/2025
  • Prior_Test_Cases: CSS01US08_TC_022

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to incident date field

Incident date field displayed



2

Try to select future date

Future date selection prevented

01/18/2025

Tomorrow's date

3

Verify validation message

Error message displayed

"Cannot select future date"

Validation message

4

Select today's date

Date accepted successfully

01/17/2025

Today's date

5

Select past date

Date accepted successfully

01/15/2025

Past date

6

Try to manually enter future date

Future date entry rejected

01/20/2025

Manual entry test

7

Verify field is mandatory

Field marked as required


Mandatory field

8

Try to proceed without date

Validation error displayed


Required validation

Verification Points

  • Primary_Verification: Future dates prevented for incident date field
  • Secondary_Verifications: Current and past dates accepted
  • Negative_Verification: Cannot select or enter future dates



Test Case 24: Auto-populate Priority Based on Selected Category

Test Case Metadata

  • Test Case ID: CSS01US08_TC_024
  • Title: Verify system auto-populates priority based on selected category (non-editable)
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, Database, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

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: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Priority configuration master data
  • Performance_Baseline: < 1 second
  • Data_Requirements: Category-priority mapping

Prerequisites

  • Setup_Requirements: Priority rules configured for categories
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Categories with different priority levels
  • Prior_Test_Cases: CSS01US08_TC_023

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select "Billing" category

Category selected successfully

Billing


2

Verify priority auto-populated

Priority field shows "High"

High

Auto-populated

3

Verify priority field is non-editable

Field is read-only/disabled


Non-editable

4

Select "Service Quality" category

Category selected successfully

Service Quality


5

Verify priority updates

Priority field shows "Medium"

Medium

Auto-update

6

Select "Technical Issue" category

Category selected successfully

Technical Issue


7

Verify priority updates

Priority field shows "Low"

Low

Auto-update

8

Try to manually edit priority

Field cannot be edited


Edit prevention

Verification Points

  • Primary_Verification: Priority auto-populates based on selected category
  • Secondary_Verifications: Priority field is non-editable
  • Negative_Verification: Cannot manually modify priority field





Test Case 25: Enforce Description Field with Character Limits

Test Case Metadata

  • Test Case ID: CSS01US08_TC_025
  • Title: Verify system enforces description field with 10-500 character limits
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, Validation

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Low
  • Business_Priority: Should-Have
  • Customer_Journey: Support
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Text validation rules

Prerequisites

  • Setup_Requirements: Character limit validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Text strings of various lengths
  • Prior_Test_Cases: CSS01US08_TC_024

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Enter description with 9 characters

Validation error displayed

"Too short"

Below minimum

2

Enter description with exactly 10 characters

Validation passes

"Valid desc"

Minimum boundary

3

Enter description with 250 characters

Validation passes

[250 character string]

Mid-range

4

Enter description with exactly 500 characters

Validation passes

[500 character string]

Maximum boundary

5

Enter description with 501 characters

Validation error displayed

[501 character string]

Above maximum

6

Verify character counter displays

Character count shown


Counter display

7

Verify field is mandatory

Field marked as required


Required field

8

Try to proceed without description

Validation error displayed


Required validation

Verification Points

  • Primary_Verification: Description field enforces 10-500 character limits
  • Secondary_Verifications: Character counter displays current count
  • Negative_Verification: Cannot proceed with description outside character limits



Test Case 26: Require Expected Resolution Field with Validation

Test Case Metadata

  • Test Case ID: CSS01US08_TC_026
  • Title: Verify system requires expected resolution field with minimum 5 characters and different from description
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, Validation

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Low
  • Business_Priority: Should-Have
  • Customer_Journey: Support
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Text validation rules

Prerequisites

  • Setup_Requirements: Field validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various text strings
  • Prior_Test_Cases: CSS01US08_TC_025

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Enter expected resolution with 4 characters

Validation error displayed

"Fix"

Below minimum

2

Enter expected resolution with 5 characters

Validation passes

"Solve"

Minimum boundary

3

Enter same text as description

Validation error displayed

[Same text as description]

Uniqueness check

4

Enter different text from description

Validation passes

"Provide refund and explanation"

Different text

5

Verify field is mandatory

Field marked as required


Required field

6

Try to proceed without expected resolution

Validation error displayed


Required validation

7

Verify minimum character message

Clear error message displayed

"Minimum 5 characters required"

Error message

8

Verify uniqueness message

Clear error message displayed

"Cannot be same as description"

Error message

Verification Points

  • Primary_Verification: Expected resolution requires minimum 5 characters and must differ from description
  • Secondary_Verifications: Clear validation messages displayed
  • Negative_Verification: Cannot proceed with invalid expected resolution



Test Case 27: Support File Upload with Format Validation

Test Case Metadata

  • Test Case ID: CSS01US08_TC_027
  • Title: Verify system supports drag & drop and browse file upload for PDF, JPG, PNG formats
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, FileUpload

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Low
  • Business_Priority: Should-Have
  • Customer_Journey: Support
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, FileStorage
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: File upload service
  • Performance_Baseline: < 5 seconds per file
  • Data_Requirements: Test files in various formats

Prerequisites

  • Setup_Requirements: File upload functionality enabled
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Files: test.pdf, image.jpg, photo.png, document.docx
  • Prior_Test_Cases: CSS01US08_TC_026

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to evidence upload section

File upload area displayed



2

Drag PDF file to upload area

File uploaded successfully

test.pdf

Drag & drop

3

Click "Choose Files" button

File browser opens


Browse method

4

Select JPG file

File uploaded successfully

image.jpg

JPG format

5

Upload PNG file

File uploaded successfully

photo.png

PNG format

6

Try to upload unsupported format

Validation error displayed

document.docx

Format validation

7

Verify supported formats only

Only PDF, JPG, PNG accepted


Format restriction

8

Verify upload methods work

Both drag & drop and browse functional


Method verification

Verification Points

  • Primary_Verification: File upload supports drag & drop and browse for PDF, JPG, PNG formats
  • Secondary_Verifications: Unsupported file formats are rejected
  • Negative_Verification: Cannot upload files in unsupported formats



Test Case 28: Limit File Uploads to Maximum 5 Files

Test Case Metadata

  • Test Case ID: CSS01US08_TC_028
  • Title: Verify system limits file uploads to maximum 5 files with size validation
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Point, FileUpload

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Low
  • Business_Priority: Should-Have
  • Customer_Journey: Support
  • Compliance_Required: No
  • SLA_Related: No

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, FileStorage
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: File upload service, Storage limits
  • Performance_Baseline: < 5 seconds per file
  • Data_Requirements: 6+ test files

Prerequisites

  • Setup_Requirements: File upload limits configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: 6 valid files: file1.pdf, file2.jpg, file3.png, file4.pdf, file5.jpg, file6.png
  • Prior_Test_Cases: CSS01US08_TC_027

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Upload first file

File uploaded successfully

file1.pdf

File 1/5

2

Upload second file

File uploaded successfully

file2.jpg

File 2/5

3

Upload third file

File uploaded successfully

file3.png

File 3/5

4

Upload fourth file

File uploaded successfully

file4.pdf

File 4/5

5

Upload fifth file

File uploaded successfully

file5.jpg

File 5/5

6

Try to upload sixth file

Upload prevented or warning displayed

file6.png

Limit enforcement

7

Verify file count limit

Maximum 5 files enforced


Limit verification

8

Remove one file and add another

New file uploads successfully


File management

Verification Points

  • Primary_Verification: File upload limited to maximum 5 files
  • Secondary_Verifications: Size validation enforced
  • Negative_Verification: Cannot upload more than 5 files



Test Case 29: Provide Optional Additional Notes Field

Test Case Metadata

  • Test Case ID: CSS01US08_TC_029
  • Title: Verify system provides optional additional notes field (0-500 characters)
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P3-Medium
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P3-Medium, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Low, Revenue-Impact-Low, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Text validation rules

Prerequisites

  • Setup_Requirements: Additional notes field configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various text strings
  • Prior_Test_Cases: CSS01US08_TC_028

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to additional notes field

Field displayed and accessible



2

Verify field is optional

Field not marked as required


Optional field

3

Leave field empty

No validation error


Empty allowed

4

Enter text within 500 characters

Text accepted

"Additional context for this evidence submission"

Valid text

5

Enter exactly 500 characters

Text accepted

[500 character string]

Maximum boundary

6

Try to enter 501 characters

Character limit enforced

[501 character string]

Limit enforcement

7

Verify character counter

Character count displayed


Counter display

8

Proceed without any notes

Form submission successful


Optional verification

Verification Points

  • Primary_Verification: Additional notes field is optional with 0-500 character limit
  • Secondary_Verifications: Character counter displays current count
  • Negative_Verification: Cannot exceed 500 character limit



Test Case 30: Auto-populate Review Section with Entered Data

Test Case Metadata

  • Test Case ID: CSS01US08_TC_030
  • Title: Verify system auto-populates review section with all entered data
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Must-Have
  • Customer_Journey: Support
  • Compliance_Required: Yes
  • SLA_Related: Yes

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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Data binding service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Complete complaint form data

Prerequisites

  • Setup_Requirements: Review section configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete complaint information
  • Prior_Test_Cases: CSS01US08_TC_029

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Complete complaint details form

All fields filled successfully

Category: Billing, Description: "Overcharged on bill"

Data entry

2

Navigate to review section

Review section displays



3

Verify customer information auto-populated

Customer details displayed

John Doe, Account: 12345, john@email.com

Customer data

4

Verify complaint details auto-populated

Complaint information displayed

Category: Billing, Priority: High, Description: "Overcharged on bill"

Complaint data

5

Verify evidence information auto-populated

Evidence details displayed

Files: invoice.pdf, Additional Notes: "Context notes"

Evidence data

6

Verify all fields are read-only

Cannot edit data in review section


Read-only verification

7

Navigate back and change data

Data changes reflected in review

Updated description

Data sync

8

Verify updated data in review

Review section shows updated information


Update verification

Verification Points

  • Primary_Verification: Review section auto-populated with all entered data
  • Secondary_Verifications: Data is read-only in review section
  • Negative_Verification: Cannot edit data directly in review section



Test Case 31: Provide Optional Send Acknowledgment Checkbox

Test Case Metadata

  • Test Case ID: CSS01US08_TC_031
  • Title: Verify system provides optional Send Acknowledgment to Customer checkbox
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P3-Medium
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P3-Medium, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Low, Revenue-Impact-Low, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Low
  • Business_Priority: Could-Have
  • Customer_Journey: Support
  • 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: Low

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Notification service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Checkbox configuration

Prerequisites

  • Setup_Requirements: Acknowledgment checkbox configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Completed complaint form
  • Prior_Test_Cases: CSS01US08_TC_030

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to review section

Review section displayed



2

Verify acknowledgment checkbox present

Checkbox visible

Send Acknowledgment to Customer

Checkbox display

3

Verify checkbox is optional

Checkbox not pre-selected


Optional state

4

Submit without selecting checkbox

Submission successful


Optional verification

5

Return and select checkbox

Checkbox selected


Selection test

6

Submit with checkbox selected

Submission successful


Selected state

7

Verify checkbox state saved

Selection preference maintained


State persistence

8

Verify submission works both ways

Both selected and unselected work


Functionality test

Verification Points

  • Primary_Verification: Send Acknowledgment checkbox is optional
  • Secondary_Verifications: Checkbox state is properly saved
  • Negative_Verification: Submission works regardless of checkbox state



Test Case 32: Generate Complaint Receipt with Unique Reference Number

Test Case Metadata

  • Test Case ID: CSS01US08_TC_032
  • Title: Verify system generates complaint receipt with unique reference number and complete details
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Must-Have
  • Customer_Journey: Support
  • Compliance_Required: Yes
  • SLA_Related: Yes

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Receipt generation service
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Complete complaint submission

Prerequisites

  • Setup_Requirements: Receipt generation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete complaint data
  • Prior_Test_Cases: CSS01US08_TC_031

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit complaint

Complaint submitted successfully

Category: Billing, Description: "Overcharged"

Submission

2

Verify receipt generation

Receipt displayed automatically


Receipt display

3

Verify unique reference number

Reference number generated

COM-2025-001

Unique ID

4

Verify receipt contains complaint details

All complaint information displayed

Category: Billing, Priority: High

Complaint data

5

Verify receipt contains customer details

Customer information displayed

John Doe, Account: 12345

Customer data

6

Verify receipt contains timestamp

Date and time displayed

01/17/2025 10:30 AM

Timestamp

7

Verify receipt is downloadable

Download option available


Download functionality

8

Verify receipt is printable

Print option available


Print functionality

Verification Points

  • Primary_Verification: Complaint receipt generated with unique reference number
  • Secondary_Verifications: Receipt contains complete complaint and customer details
  • Negative_Verification: No duplicate reference numbers generated



Test Case 33: Require Transfer Type Selection from Configurable Master Data

Test Case Metadata

  • Test Case ID: CSS01US08_TC_033
  • Title: Verify system requires transfer type selection from configurable master data
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-High, Revenue-Impact-High, Integration-Point, Happy path

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: Medium
  • Failure_Impact: High

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Transfer settings master data
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Transfer types configuration

Prerequisites

  • Setup_Requirements: Transfer types master data configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Transfer types: Account Transfer, Service Transfer, Billing Transfer
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "Request Transfer" card

Transfer request page loads



2

Verify transfer type dropdown

Dropdown field displayed



3

Click transfer type dropdown

Available options displayed

Account Transfer, Service Transfer, Billing Transfer

Master data

4

Verify field is required

Field marked as mandatory


Required field

5

Try to proceed without selection

Validation error displayed


Validation check

6

Select "Account Transfer"

Selection successful

Account Transfer

Valid selection

7

Verify selection saved

Selected value displayed


Selection persistence

8

Verify options come from settings

Options match configured master data


Configuration verification

Verification Points

  • Primary_Verification: Transfer type selection required from configurable master data
  • Secondary_Verifications: All transfer types come from settings configuration
  • Negative_Verification: Cannot proceed without transfer type selection



Test Case 34: Enforce Future Date Selection for Effective Date

Test Case Metadata

  • Test Case ID: CSS01US08_TC_034
  • Title: Verify system enforces future date selection for effective date with date picker
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-High, Revenue-Impact-High, Integration-Point, Validation

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: High

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Date validation service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Date picker functionality

Prerequisites

  • Setup_Requirements: Date validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Current date: 01/17/2025
  • Prior_Test_Cases: CSS01US08_TC_033

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click effective date field

Date picker opens



2

Try to select today's date

Date selection prevented

01/17/2025

Current date

3

Try to select past date

Date selection prevented

01/15/2025

Past date

4

Select future date

Date accepted successfully

02/15/2025

Future date

5

Verify date picker functionality

Date picker displays properly


UI functionality

6

Verify field is required

Field marked as mandatory


Required field

7

Try to proceed without date

Validation error displayed


Validation check

8

Verify future date requirement

Only future dates selectable


Future date enforcement

Verification Points

  • Primary_Verification: Effective date requires future date selection with date picker
  • Secondary_Verifications: Current and past dates are prevented
  • Negative_Verification: Cannot select current or past dates



Test Case 35: Require New Account Holder Information with Validation

Test Case Metadata

  • Test Case ID: CSS01US08_TC_035
  • Title: Verify system requires new account holder first name, last name, email, and phone number
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-High, Revenue-Impact-High, Integration-Point, Happy path

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: High
  • Failure_Impact: High

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Contact information validation

Prerequisites

  • Setup_Requirements: Form validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Valid contact information
  • Prior_Test_Cases: CSS01US08_TC_034

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to new account holder section

Section displayed



2

Verify first name field is required

Field marked as mandatory


Required field

3

Enter first name

Name accepted

Jane

Text input

4

Verify last name field is required

Field marked as mandatory


Required field

5

Enter last name

Name accepted

Smith

Text input

6

Verify email field is required

Field marked as mandatory


Required field

7

Enter email address

Email accepted

jane.smith@email.com

Email validation

8

Verify phone field is required

Field marked as mandatory


Required field

9

Enter phone number

Phone accepted

(555) 123-4567

Phone validation

10

Try to proceed with empty fields

Validation errors displayed


Required validation

Verification Points

  • Primary_Verification: All four fields (first name, last name, email, phone) are required
  • Secondary_Verifications: Text input accepted for name fields
  • Negative_Verification: Cannot proceed with missing required fields



Test Case 36: Validate Email Format and Phone Number Format

Test Case Metadata

  • Test Case ID: CSS01US08_TC_036
  • Title: Verify system validates email format and phone number format
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Validation

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Should-Have
  • Customer_Journey: Daily-Usage
  • 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: Medium

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Format validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Invalid and valid format examples

Prerequisites

  • Setup_Requirements: Format validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various email and phone formats
  • Prior_Test_Cases: CSS01US08_TC_035

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Enter invalid email format

Validation error displayed

invalidEmail

Invalid format

2

Enter valid email format

Email accepted

jane.smith@email.com

Valid format

3

Enter email without @ symbol

Validation error displayed

jane.smith.email.com

Missing @

4

Enter email without domain

Validation error displayed

jane.smith@

Missing domain

5

Enter invalid phone format

Validation error displayed

12345

Invalid format

6

Enter valid phone format

Phone accepted

(555) 123-4567

Valid format

7

Enter phone with letters

Validation error displayed

(ABC) 123-4567

Invalid characters

8

Verify format validation messages

Clear error messages displayed


Error messaging

Verification Points

  • Primary_Verification: Email format and phone number format validation enforced
  • Secondary_Verifications: Clear validation error messages displayed
  • Negative_Verification: Invalid formats rejected with appropriate error messages



Test Case 37: Provide Relationship Dropdown with Predefined Options

Test Case Metadata

  • Test Case ID: CSS01US08_TC_037
  • Title: Verify system provides relationship dropdown with predefined options
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Should-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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Dropdown configuration
  • Performance_Baseline: < 1 second
  • Data_Requirements: Relationship options

Prerequisites

  • Setup_Requirements: Relationship dropdown configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Predefined relationship options
  • Prior_Test_Cases: CSS01US08_TC_036

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click relationship dropdown

Dropdown options displayed



2

Verify "Spouse" option available

Option visible in dropdown

Spouse

Option 1

3

Verify "Child" option available

Option visible in dropdown

Child

Option 2

4

Verify "Parent" option available

Option visible in dropdown

Parent

Option 3

5

Verify "Sibling" option available

Option visible in dropdown

Sibling

Option 4

6

Verify "Business partner" option available

Option visible in dropdown

Business partner

Option 5

7

Verify "Other" option available

Option visible in dropdown

Other

Option 6

8

Select "Spouse" option

Selection successful

Spouse

Selection test

9

Verify field is required

Field marked as mandatory


Required field

Verification Points

  • Primary_Verification: Relationship dropdown with predefined options (Spouse, Child, Parent, Sibling, Business partner, Other)
  • Secondary_Verifications: All options are selectable
  • Negative_Verification: Cannot proceed without relationship selection



Test Case 38: Offer Billing Address Change Option

Test Case Metadata

  • Test Case ID: CSS01US08_TC_038
  • Title: Verify system offers billing address change option with conditional address fields
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

  • Customer_Segment: All
  • Revenue_Impact: Medium
  • Business_Priority: Should-Have
  • Customer_Journey: Daily-Usage
  • 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: Medium

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Address form configuration
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Address form fields

Prerequisites

  • Setup_Requirements: Billing address options configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Address information
  • Prior_Test_Cases: CSS01US08_TC_037

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to billing address section

Section displayed



2

Verify radio button options

Two options displayed

"Yes, change billing address" / "No, keep existing address"

Radio options

3

Select "No, keep existing address"

Option selected, no additional fields


Default option

4

Select "Yes, change billing address"

Option selected, address fields displayed


Conditional display

5

Verify address fields appear

Address form fields visible

Street, City, State, ZIP

Address fields

6

Verify field is required

One option must be selected


Required selection

7

Test conditional field display

Address fields show/hide based on selection


Conditional logic

8

Verify address fields same as NSC form

Same address fields as new service connection


Field consistency

Verification Points

  • Primary_Verification: Billing address change option with conditional address fields
  • Secondary_Verifications: Address fields match NSC form format
  • Negative_Verification: Cannot proceed without billing address selection



Test Case 39: Provide Financial Responsibility Radio Buttons

Test Case Metadata

  • Test Case ID: CSS01US08_TC_039
  • Title: Verify system provides financial responsibility radio buttons with default selection
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Point, Happy path

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: High

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Financial settings configuration
  • Performance_Baseline: < 1 second
  • Data_Requirements: Financial responsibility options

Prerequisites

  • Setup_Requirements: Financial responsibility options configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Financial responsibility settings
  • Prior_Test_Cases: CSS01US08_TC_038

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to financial responsibility section

Section displayed



2

Verify two radio button options

Two options displayed

"Transfer outstanding balance" / "Clear balance before transfer"

Radio options

3

Verify default selection

"Transfer outstanding balance" pre-selected


Default selection

4

Select "Clear balance before transfer"

Option selected successfully


Alternative option

5

Verify single selection

Only one option selected at a time


Single selection

6

Verify field is required

One option must be selected


Required selection

7

Test selection toggle

Can switch between options


Toggle functionality

8

Verify default behavior

"Transfer outstanding balance" is default


Default verification

Verification Points

  • Primary_Verification: Financial responsibility radio buttons with "Transfer outstanding balance" as default
  • Secondary_Verifications: Only one option can be selected at a time
  • Negative_Verification: Cannot proceed without financial responsibility selection



Test Case 40: Display Multiple Document Types with Optional Upload

Test Case Metadata

  • Test Case ID: CSS01US08_TC_040
  • Title: Verify system displays multiple document types with optional upload for each type
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, FileStorage
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: File upload service, Document configuration
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Document type configuration

Prerequisites

  • Setup_Requirements: Document types configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Document types: ID Proof, Address Proof, Income Proof
  • Prior_Test_Cases: CSS01US08_TC_039

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to documentation section

Documentation section displayed



2

Verify ID Proof document type

Document type visible

ID Proof

Document type 1

3

Verify Address Proof document type

Document type visible

Address Proof

Document type 2

4

Verify Income Proof document type

Document type visible

Income Proof

Document type 3

5

Verify upload is optional

No required field indicators


Optional upload

6

Upload document under ID Proof

Upload successful

drivers_license.pdf

Upload test

7

Proceed without uploading to other types

Process continues successfully


Optional verification

8

Verify all document types are visible

All configured types displayed


Type visibility

Verification Points

  • Primary_Verification: Multiple document types displayed with optional upload
  • Secondary_Verifications: All document types are visible and functional
  • Negative_Verification: Upload is optional, not required for all types



Test Case 41: Allow Multiple Sub-document Uploads Under Each Document Type

Test Case Metadata

  • Test Case ID: CSS01US08_TC_041
  • Title: Verify system allows multiple sub-document uploads under each document type
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, FileStorage
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: File upload service, Storage management
  • Performance_Baseline: < 5 seconds per file
  • Data_Requirements: Multiple document files

Prerequisites

  • Setup_Requirements: Multiple file upload enabled
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Multiple documents: license.pdf, passport.pdf, utility_bill.pdf, lease.pdf
  • Prior_Test_Cases: CSS01US08_TC_040

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Upload first document under ID Proof

Upload successful

drivers_license.pdf

Sub-document 1

2

Upload second document under ID Proof

Upload successful

passport.pdf

Sub-document 2

3

Verify both documents listed

Both documents displayed


Multiple document display

4

Upload first document under Address Proof

Upload successful

utility_bill.pdf

Different type

5

Upload second document under Address Proof

Upload successful

lease_agreement.pdf

Multiple under same type

6

Verify documents organized by type

Documents grouped by document type


Organization verification

7

Test upload limits per type

Multiple uploads allowed per type


Limit testing

8

Verify document management

Can remove and add documents


Document management

Verification Points

  • Primary_Verification: Multiple sub-document uploads allowed under each document type
  • Secondary_Verifications: Documents properly organized by type
  • Negative_Verification: No restriction on multiple uploads per document type



Test Case 42: Display Outstanding Balance Prominently

Test Case Metadata

  • Test Case ID: CSS01US08_TC_042
  • Title: Verify system displays outstanding balance prominently and transfers to new account holder
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Point, Happy path

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: High

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Billing
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Billing system, Balance calculation
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Account with outstanding balance

Prerequisites

  • Setup_Requirements: Billing system integrated
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Account with outstanding balance: $245.78
  • Prior_Test_Cases: CSS01US08_TC_041

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to transfer request review

Review section displayed



2

Verify outstanding balance displayed

Balance shown prominently

$245.78

Prominent display

3

Verify balance amount is correct

Correct amount displayed

$245.78

Amount verification

4

Verify balance transfer indication

Shows transfer to new account holder


Transfer indication

5

Verify balance is highlighted

Balance displayed with emphasis


Visual prominence

6

Verify currency formatting

Balance properly formatted

$245.78

Format verification

7

Test with zero balance

Zero balance displayed correctly

$0.00

Zero balance test

8

Verify balance alert

Alert or warning displayed


Alert verification

Verification Points

  • Primary_Verification: Outstanding balance displayed prominently and transfers to new account holder
  • Secondary_Verifications: Balance amount is correct and properly formatted
  • Negative_Verification: Balance cannot be hidden or missed by user



Test Case 43: Generate Downloadable/Printable Transfer Receipt

Test Case Metadata

  • Test Case ID: CSS01US08_TC_043
  • Title: Verify system generates downloadable/printable transfer receipt with all details
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Receipt generation service
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Completed transfer request

Prerequisites

  • Setup_Requirements: Receipt generation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete transfer request
  • Prior_Test_Cases: CSS01US08_TC_042

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit transfer request

Request submitted successfully



2

Verify receipt generation

Receipt displayed automatically


Receipt display

3

Verify receipt contains transfer details

All transfer information displayed

Transfer type, effective date, new account holder

Transfer data

4

Verify receipt contains customer details

Customer information displayed

Current account holder, account number

Customer data

5

Verify receipt contains financial details

Outstanding balance transfer information

$245.78 transfer

Financial data

6

Click "Download" button

Receipt downloads as PDF


Download functionality

7

Verify PDF content

Downloaded PDF contains complete information


PDF verification

8

Click "Print" button

Print dialog opens


Print functionality

9

Verify receipt can be returned to dashboard

Dashboard navigation available


Navigation option

Verification Points

  • Primary_Verification: Transfer receipt is downloadable and printable with all details
  • Secondary_Verifications: Receipt contains complete transfer, customer, and financial information
  • Negative_Verification: No missing information in receipt



Test Case 44: Provide Disconnection Reason Dropdown from Master Data

Test Case Metadata

  • Test Case ID: CSS01US08_TC_044
  • Title: Verify system provides disconnection reason dropdown from configurable master data
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Disconnection settings master data
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Disconnection reasons configuration

Prerequisites

  • Setup_Requirements: Disconnection reasons configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Reasons: Moving, Temporary Closure, Service Issues, Property Sale
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "Request Disconnection" card

Disconnection request page loads



2

Verify reason dropdown field

Dropdown field displayed



3

Click reason dropdown

Available reasons displayed

Moving, Temporary Closure, Service Issues, Property Sale

Master data

4

Verify field is required

Field marked as mandatory


Required field

5

Select "Moving" reason

Reason selected successfully

Moving

Valid selection

6

Try to proceed without selection

Validation error displayed


Validation check

7

Verify reasons come from settings

Options match configured master data


Configuration verification

8

Test with different reason

Different reason selectable

Temporary Closure

Alternative selection

Verification Points

  • Primary_Verification: Disconnection reason dropdown from configurable master data
  • Secondary_Verifications: Field is required and validates properly
  • Negative_Verification: Cannot proceed without reason selection



Test Case 45: Require Mandatory Date Selection Preventing Past Dates

Test Case Metadata

  • Test Case ID: CSS01US08_TC_045
  • Title: Verify system requires mandatory date selection preventing past dates
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-High, Revenue-Impact-Medium, Integration-Point, Validation

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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Date validation service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Date picker with validation

Prerequisites

  • Setup_Requirements: Date validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Current date: 01/17/2025
  • Prior_Test_Cases: CSS01US08_TC_044

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to preferred schedule section

Schedule section displayed



2

Verify date field is mandatory

Field marked as required


Required field

3

Try to proceed without date

Validation error displayed


Required validation

4

Try to select past date

Date selection prevented

01/15/2025

Past date

5

Try to select today's date

Date selection prevented

01/17/2025

Current date

6

Select future date

Date accepted successfully

02/15/2025

Future date

7

Verify date picker functionality

Date picker opens properly


UI functionality

8

Verify validation message

Clear error message for past dates


Error messaging

Verification Points

  • Primary_Verification: Date selection is mandatory and prevents past dates
  • Secondary_Verifications: Current date also prevented, only future dates allowed
  • Negative_Verification: Cannot select past or current dates



Test Case 46: Offer Configurable Admin-defined Time Slots

Test Case Metadata

  • Test Case ID: CSS01US08_TC_046
  • Title: Verify system offers configurable admin-defined time slots (2-hour blocks)
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Time slot configuration service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Time slot configuration

Prerequisites

  • Setup_Requirements: Time slots configured by admin
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Time slots: 8:00 AM - 10:00 AM, 10:00 AM - 12:00 PM, 1:00 PM - 3:00 PM
  • Prior_Test_Cases: CSS01US08_TC_045

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select valid future date

Date selected successfully

02/15/2025

Date selection

2

Click time slot dropdown

Time slot options displayed



3

Verify 2-hour block format

Time slots in 2-hour blocks

8:00 AM - 10:00 AM, 10:00 AM - 12:00 PM

2-hour blocks

4

Verify time slots are configurable

Admin-defined slots displayed


Configuration verification

5

Select time slot

Time slot selected successfully

8:00 AM - 10:00 AM

Selection test

6

Test with different date

Different time slots may be available

02/16/2025

Date-based slots

7

Verify slot availability

Available slots displayed


Availability check

8

Verify admin configurability

Time slots come from admin settings


Configuration source

Verification Points

  • Primary_Verification: Time slots are configurable by admin in 2-hour blocks
  • Secondary_Verifications: Time slots display properly and are selectable
  • Negative_Verification: Time slots cannot be manually entered, only selected



Test Case 47: Provide Optional Additional Notes Field (250 Characters)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_047
  • Title: Verify system provides optional additional notes field (maximum 250 characters, text only)
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P3-Medium
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P3-Medium, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Low, Revenue-Impact-Low, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Text validation rules

Prerequisites

  • Setup_Requirements: Additional notes field configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various text strings
  • Prior_Test_Cases: CSS01US08_TC_046

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to additional notes field

Field displayed



2

Verify field is optional

Field not marked as required


Optional field

3

Leave field empty

No validation error


Empty allowed

4

Enter text within 250 characters

Text accepted

"Priority disconnection needed due to moving date"

Valid text

5

Enter exactly 250 characters

Text accepted

[250 character string]

Maximum boundary

6

Try to enter 251 characters

Character limit enforced

[251 character string]

Limit enforcement

7

Try to enter special characters

Special characters rejected

!@#$%^&*()

Text only validation

8

Verify character counter

Character count displayed


Counter display

9

Proceed without any notes

Form submission successful


Optional verification

Verification Points

  • Primary_Verification: Additional notes field is optional with 250 character limit, text only
  • Secondary_Verifications: Character counter displays, special characters handled appropriately
  • Negative_Verification: Cannot exceed 250 character limit



Test Case 48: Display Read-only Customer Information Summary

Test Case Metadata

  • Test Case ID: CSS01US08_TC_048
  • Title: Verify system displays read-only customer information summary
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Customer data service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Customer account information

Prerequisites

  • Setup_Requirements: Customer data integration configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Customer: John Doe, Account: 12345, Email: john@email.com
  • Prior_Test_Cases: CSS01US08_TC_047

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Review & Submit section

Review section displayed



2

Verify customer name displayed

Name shown as read-only

John Doe

Customer name

3

Verify account number displayed

Account number shown as read-only

12345

Account number

4

Verify customer type displayed

Customer type shown as read-only

Residential

Customer type

5

Verify service address displayed

Service address shown as read-only

123 Main St, Springfield

Service address

6

Verify email displayed

Email shown as read-only

john@email.com

Email

7

Verify phone displayed

Phone shown as read-only

(555) 123-4567

Phone

8

Try to edit customer information

Fields are not editable


Read-only verification

9

Verify all fields match verified customer

Information matches logged-in customer


Customer verification

Verification Points

  • Primary_Verification: Customer information summary displayed as read-only
  • Secondary_Verifications: All customer fields are present and match logged-in customer
  • Negative_Verification: Cannot edit customer information in review section



Test Case 49: Validate Required Fields Before Enabling Submit

Test Case Metadata

  • Test Case ID: CSS01US08_TC_049
  • Title: Verify system validates all required fields before enabling submit button
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-High, Revenue-Impact-High, Integration-Point, Validation

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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service catalog configuration
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Service request cards configuration

Prerequisites

  • Setup_Requirements: Service request cards configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Expected card names list
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Service & Support page

Page loads successfully



2

Count total number of service cards

Exactly 5 cards displayed


Count = 5

3

Verify "Service Request" card exists

Card found with exact name

Service Request

Card 1 verification

4

Verify "Register Complaint" card exists

Card found with exact name

Register Complaint

Card 2 verification

5

Verify "Request Transfer" card exists

Card found with exact name

Request Transfer

Card 3 verification

6

Verify "Request Disconnection" card exists

Card found with exact name

Request Disconnection

Card 4 verification

7

Verify "Request Reconnection" card exists

Card found with exact name

Request Reconnection

Card 5 verification

Verification Points

  • Primary_Verification: Exactly 5 service request cards displayed with specified names
  • Secondary_Verifications: Card names match requirements exactly
  • Negative_Verification: No additional cards displayed beyond the required 5



Test Case 50: Generate Downloadable/Printable Disconnection Receipt

Test Case Metadata

  • Test Case ID: CSS01US08_TC_050
  • Title: Verify system generates downloadable/printable disconnection receipt
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Receipt generation service
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Completed disconnection request

Prerequisites

  • Setup_Requirements: Receipt generation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete disconnection request
  • Prior_Test_Cases: CSS01US08_TC_049

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit disconnection request

Request submitted successfully

Reason: Moving, Date: 02/15/2025

Submission

2

Verify receipt generation

Receipt displayed automatically


Receipt display

3

Verify receipt contains request details

All disconnection information displayed

Request Type: Disconnection, Reason: Moving

Request data

4

Verify receipt contains customer details

Customer information displayed

John Doe, Account: 12345

Customer data

5

Verify receipt contains schedule details

Schedule information displayed

02/15/2025, 8:00 AM - 10:00 AM

Schedule data

6

Click "Download" button

Receipt downloads as PDF


Download functionality

7

Verify PDF content

Downloaded PDF contains complete information


PDF verification

8

Click "Print" button

Print dialog opens


Print functionality

9

Verify print preview

Print preview shows complete receipt


Print preview

Verification Points

  • Primary_Verification: Disconnection receipt is downloadable and printable
  • Secondary_Verifications: Receipt contains complete disconnection and customer details
  • Negative_Verification: No missing information in receipt



Test Case 51: Update Audit Trail Upon Successful Submission

Test Case Metadata

  • Test Case ID: CSS01US08_TC_051
  • Title: Verify system updates audit trail upon successful submission
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, API, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Happy path

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: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database, AuditService
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Integration-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Audit service, Database
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Audit trail configuration

Prerequisites

  • Setup_Requirements: Audit service configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete disconnection request
  • Prior_Test_Cases: CSS01US08_TC_050

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit disconnection request

Request submitted successfully

Reason: Moving, Date: 02/15/2025

Submission

2

Verify audit trail entry created

Audit record created


Audit creation

3

Verify audit contains user information

User ID recorded in audit

Customer ID: 12345

User tracking

4

Verify audit contains request details

Request information logged

Request Type: Disconnection

Request logging

5

Verify audit contains timestamp

Submission timestamp recorded

01/17/2025 10:30 AM

Timestamp logging

6

Verify audit contains status

Initial status recorded

Status: Submitted

Status logging

7

Verify audit trail is complete

All required audit fields populated


Complete audit

8

Test audit trail accessibility

Audit trail can be queried


Audit accessibility

Verification Points

  • Primary_Verification: Audit trail updated upon successful submission
  • Secondary_Verifications: Audit contains complete user, request, and timestamp information
  • Negative_Verification: No audit trail created for failed submissions



Test Case 52: Provide Reconnection Reason Dropdown from Master Data

Test Case Metadata

  • Test Case ID: CSS01US08_TC_052
  • Title: Verify system provides reconnection reason dropdown from configurable master data
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Reconnection settings master data
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Reconnection reasons configuration

Prerequisites

  • Setup_Requirements: Reconnection reasons configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Reasons: Service Restoration, New Tenant, Service Upgrade, Maintenance Complete
  • Prior_Test_Cases: CSS01US08_TC_002

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click "Request Reconnection" card

Reconnection request page loads



2

Verify reason dropdown field

Dropdown field displayed



3

Click reason dropdown

Available reasons displayed

Service Restoration, New Tenant, Service Upgrade, Maintenance Complete

Master data

4

Verify field is required

Field marked as mandatory


Required field

5

Select "Service Restoration" reason

Reason selected successfully

Service Restoration

Valid selection

6

Try to proceed without selection

Validation error displayed


Validation check

7

Verify reasons come from settings

Options match configured master data


Configuration verification

8

Test with different reason

Different reason selectable

New Tenant

Alternative selection

Verification Points

  • Primary_Verification: Reconnection reason dropdown from configurable master data
  • Secondary_Verifications: Field is required and validates properly
  • Negative_Verification: Cannot proceed without reason selection



Test Case 53: Require Mandatory Date Selection Preventing Past Dates (Reconnection)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_053
  • Title: Verify system requires mandatory date selection preventing past dates for reconnection
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-High, Revenue-Impact-Medium, Integration-Point, Validation

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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Date validation service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Date picker with validation

Prerequisites

  • Setup_Requirements: Date validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Current date: 01/17/2025
  • Prior_Test_Cases: CSS01US08_TC_052

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to preferred schedule section

Schedule section displayed



2

Verify date field is mandatory

Field marked as required


Required field

3

Try to proceed without date

Validation error displayed


Required validation

4

Try to select past date

Date selection prevented

01/15/2025

Past date

5

Try to select today's date

Date selection prevented

01/17/2025

Current date

6

Select future date

Date accepted successfully

02/20/2025

Future date

7

Verify date picker functionality

Date picker opens properly


UI functionality

8

Verify validation message

Clear error message for past dates


Error messaging

Verification Points

  • Primary_Verification: Date selection is mandatory and prevents past dates for reconnection
  • Secondary_Verifications: Current date also prevented, only future dates allowed
  • Negative_Verification: Cannot select past or current dates



Test Case 54: Offer Configurable Admin-defined Time Slots (Reconnection)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_054
  • Title: Verify system offers configurable admin-defined time slots for reconnection (2-hour blocks)
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Time slot configuration service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Time slot configuration

Prerequisites

  • Setup_Requirements: Time slots configured by admin
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Time slots: 10:00 AM - 12:00 PM, 1:00 PM - 3:00 PM, 3:00 PM - 5:00 PM
  • Prior_Test_Cases: CSS01US08_TC_053

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select valid future date

Date selected successfully

02/20/2025

Date selection

2

Click time slot dropdown

Time slot options displayed



3

Verify 2-hour block format

Time slots in 2-hour blocks

10:00 AM - 12:00 PM, 1:00 PM - 3:00 PM

2-hour blocks

4

Verify time slots are configurable

Admin-defined slots displayed


Configuration verification

5

Select time slot

Time slot selected successfully

10:00 AM - 12:00 PM

Selection test

6

Test with different date

Different time slots may be available

02/21/2025

Date-based slots

7

Verify slot availability

Available slots displayed


Availability check

8

Verify admin configurability

Time slots come from admin settings


Configuration source

Verification Points

  • Primary_Verification: Time slots are configurable by admin in 2-hour blocks for reconnection
  • Secondary_Verifications: Time slots display properly and are selectable
  • Negative_Verification: Time slots cannot be manually entered, only selected



Test Case 55: Provide Optional Additional Notes Field (Reconnection)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_055
  • Title: Verify system provides optional additional notes field for reconnection (maximum 250 characters, text only)
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P3-Medium
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P3-Medium, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Low, Revenue-Impact-Low, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 1 second
  • Data_Requirements: Text validation rules

Prerequisites

  • Setup_Requirements: Additional notes field configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Various text strings
  • Prior_Test_Cases: CSS01US08_TC_054

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to additional notes field

Field displayed



2

Verify field is optional

Field not marked as required


Optional field

3

Leave field empty

No validation error


Empty allowed

4

Enter text within 250 characters

Text accepted

"Priority reconnection needed for business operations"

Valid text

5

Enter exactly 250 characters

Text accepted

[250 character string]

Maximum boundary

6

Try to enter 251 characters

Character limit enforced

[251 character string]

Limit enforcement

7

Try to enter special characters

Special characters rejected

!@#$%^&*()

Text only validation

8

Verify character counter

Character count displayed


Counter display

9

Proceed without any notes

Form submission successful


Optional verification

Verification Points

  • Primary_Verification: Additional notes field is optional with 250 character limit, text only
  • Secondary_Verifications: Character counter displays, special characters handled appropriately
  • Negative_Verification: Cannot exceed 250 character limit



Test Case 56: Display Read-only Customer Information Summary (Reconnection)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_056
  • Title: Verify system displays read-only customer information summary for reconnection
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Customer data service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Customer account information

Prerequisites

  • Setup_Requirements: Customer data integration configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Customer: John Doe, Account: 12345, Email: john@email.com
  • Prior_Test_Cases: CSS01US08_TC_055

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Review & Submit section

Review section displayed



2

Verify customer name displayed

Name shown as read-only

John Doe

Customer name

3

Verify account number displayed

Account number shown as read-only

12345

Account number

4

Verify customer type displayed

Customer type shown as read-only

Residential

Customer type

5

Verify service address displayed

Service address shown as read-only

123 Main St, Springfield

Service address

6

Verify email displayed

Email shown as read-only

john@email.com

Email

7

Verify phone displayed

Phone shown as read-only

(555) 123-4567

Phone

8

Try to edit customer information

Fields are not editable


Read-only verification

9

Verify all fields match verified customer

Information matches logged-in customer


Customer verification

Verification Points

  • Primary_Verification: Customer information summary displayed as read-only for reconnection
  • Secondary_Verifications: All customer fields are present and match logged-in customer
  • Negative_Verification: Cannot edit customer information in review section



Test Case 57: Validate Required Fields Before Enabling Submit (Reconnection)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_057
  • Title: Verify system validates all required fields before enabling submit button for reconnection
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support

  • Tags: Negative, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-High, Business-High, Revenue-Impact-High, Integration-Point, Validation

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: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Quality-Dashboard, Validation-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form validation service
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Required field validation rules

Prerequisites

  • Setup_Requirements: Form validation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Partial and complete reconnection request data
  • Prior_Test_Cases: CSS01US08_TC_056

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Review & Submit section

Review section displayed



2

Verify submit button state with missing fields

Submit button disabled


Missing required fields

3

Fill verified customer information

Customer information populated

John Doe, Account: 12345

Customer data

4

Verify submit button still disabled

Submit button remains disabled


Still missing fields

5

Fill request type

Request type populated

Reconnection

Request type

6

Fill reconnection reason

Reason populated

Service Restoration

Reason field

7

Fill preferred schedule

Schedule populated

02/20/2025, 10:00 AM - 12:00 PM

Schedule data

8

Verify all required fields complete

All required fields filled


Complete validation

9

Verify submit button enabled

Submit button becomes enabled


Validation passes

10

Test submit functionality

Request submits successfully


Submission test

Verification Points

  • Primary_Verification: Submit button enabled only when all required fields are validated for reconnection
  • Secondary_Verifications: Submit button state changes dynamically based on field completion
  • Negative_Verification: Cannot submit with missing required fields



Test Case 58: Provide Add Another Reconnection Request Option

Test Case Metadata

  • Test Case ID: CSS01US08_TC_058
  • Title: Verify system provides Add another Reconnection request option after successful submission
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Point, Happy path

Business Context

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

Quality Metrics

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Form reset functionality
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Successful reconnection request

Prerequisites

  • Setup_Requirements: Add another request functionality configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete reconnection request
  • Prior_Test_Cases: CSS01US08_TC_057

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit reconnection request

Request submitted successfully

Reason: Service Restoration

Submission

2

Verify success message displayed

Success confirmation shown


Success confirmation

3

Verify "Add another Reconnection request" option

Option displayed prominently


Option display

4

Click "Add another Reconnection request"

New request form displays


New form

5

Verify form is reset

Clean form with no previous data


Form reset

6

Verify customer information retained

Customer data still pre-populated

John Doe, Account: 12345

Customer retention

7

Fill out new reconnection request

Second request can be submitted

Reason: New Tenant

Second request

8

Submit second request

Second request submitted successfully


Multiple submissions

9

Verify both requests are separate

Two distinct requests created


Request separation

Verification Points

  • Primary_Verification: "Add another Reconnection request" option available after successful submission
  • Secondary_Verifications: New form resets properly while retaining customer information
  • Negative_Verification: Previous request data does not carry over to new request




Test Case 59: Generate Downloadable/Printable Reconnection Receipt

Test Case Metadata

  • Test Case ID: CSS01US08_TC_059
  • Title: Verify system generates downloadable/printable reconnection receipt
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

  • Module/Feature: Service & Support Management
  • Test Type: Functional/UI
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, UI, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Happy path

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

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Happy path
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

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

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Receipt generation service
  • Performance_Baseline: < 3 seconds
  • Data_Requirements: Completed reconnection request

Prerequisites

  • Setup_Requirements: Receipt generation configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete reconnection request
  • Prior_Test_Cases: CSS01US08_TC_058

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit reconnection request

Request submitted successfully

Reason: Service Restoration, Date: 02/20/2025

Submission

2

Verify receipt generation

Receipt displayed automatically


Receipt display

3

Verify receipt contains request details

All reconnection information displayed

Request Type: Reconnection, Reason: Service Restoration

Request data

4

Verify receipt contains customer details

Customer information displayed

John Doe, Account: 12345

Customer data

5

Verify receipt contains schedule details

Schedule information displayed

02/20/2025, 10:00 AM - 12:00 PM

Schedule data

6

Verify receipt contains notes

Additional notes displayed if provided

"Priority reconnection needed"

Notes data

7

Click "Download" button

Receipt downloads as PDF


Download functionality

8

Verify PDF content

Downloaded PDF contains complete information


PDF verification

9

Click "Print" button

Print dialog opens


Print functionality

10

Verify print preview

Print preview shows complete receipt


Print preview

Verification Points

  • Primary_Verification: Reconnection receipt is downloadable and printable
  • Secondary_Verifications: Receipt contains complete reconnection and customer details
  • Negative_Verification: No missing information in receipt



Test Case 60: Update Audit Trail Upon Successful Submission (Reconnection)

Test Case Metadata

  • Test Case ID: CSS01US08_TC_060
  • Title: Verify system updates audit trail upon successful reconnection request submission
  • Created By: Hetal
  • Created Date: 2025-01-17
  • Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support

  • Tags: Happy-Path, Consumer Services, API, Database, MOD-ServiceSupport, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Happy path

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: High
  • Failure_Impact: Critical

Coverage Tracking

  • Feature_Coverage: 2% of feature covered
  • Integration_Points: CxServices, API, Database, AuditService
  • Code_Module_Mapped: CX-Web
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Quality-Dashboard, Integration-Testing
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: High

Requirements Traceability

Test Environment

  • Environment: Dev/Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Audit service, Database
  • Performance_Baseline: < 2 seconds
  • Data_Requirements: Audit trail configuration

Prerequisites

  • Setup_Requirements: Audit service configured
  • User_Roles_Permissions: Valid authenticated customer
  • Test_Data: Complete reconnection request
  • Prior_Test_Cases: CSS01US08_TC_059

Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Submit reconnection request

Request submitted successfully

Reason: Service Restoration, Date: 02/20/2025

Submission

2

Verify audit trail entry created

Audit record created


Audit creation

3

Verify audit contains user information

User ID recorded in audit

Customer ID: 12345

User tracking

4

Verify audit contains request details

Request information logged

Request Type: Reconnection

Request logging

5

Verify audit contains timestamp

Submission timestamp recorded

01/17/2025 10:45 AM

Timestamp logging

6

Verify audit contains status

Initial status recorded

Status: Submitted

Status logging

7

Verify audit contains reason

Reconnection reason logged

Reason: Service Restoration

Reason logging

8

Verify audit trail is complete

All required audit fields populated


Complete audit

9

Test audit trail accessibility

Audit trail can be queried


Audit accessibility

Verification Points

  • Primary_Verification: Audit trail updated upon successful reconnection request submission
  • Secondary_Verifications: Audit contains complete user, request, and timestamp information
  • Negative_Verification: No audit trail created for failed submissions


Back to top