Skip to main content

New Service Connection Application Form (CIS01US03)

Total Test Cases: 27
Total Acceptance criteria :14
Total Coverage : 100%




TC_ Single-page application form with clear section divisions

Test Case: CIS01US03_TC_001

Title: Verify single-page application form displays with clear section divisions and proper layout

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_001
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC1
  • Requirements Traceability: CIS01US03-AC-01

Classification:

  • Module/Feature: New Service Connection Application Form 
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support:MOD-CX Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-None, UI-Layout, Coverage-AC1, Browser-All, Device-All, AC1-SinglePage ,HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC1
  • Integration_Points: Service-CX, API 
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC1
  • Cross_Platform_Support: Web

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: WaterUtil Authentication Service
  • Performance_Baseline: Page load < 2 seconds

Prerequisites:

  • Valid Customer Executive credentials
  • Clean test environment
  • WaterUtil Authentication Service available
  • Consumer Onboarding module accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Consumer Onboarding dashboard

Dashboard loads successfully with "New Application" button visible

N/A

Verify dashboard accessibility

2

Click "New Application" button

Single-page form loads with all sections visible
AI - powered upload & Enter Manually

section
AI - powered upload & Enter Manually are visible

Form should display all sections

3

Verify section divisions are clearly marked

Six distinct sections visible: 1) Application Method, 2) Consumer Details, 3) Address Details, 4) Document Upload, 5) Plan Selection, 6) Review & Payment

N/A

Each section clearly separated

4

Verify section headings are prominent

Each section has clear, readable heading with appropriate font size and contrast

N/A

Visual hierarchy validation

5

Verify section boundaries

Visual separation between sections using borders, spacing, or background colors

N/A

Clear section demarcation

6

Verify Test scrolling behavior

Smooth scrolling through all sections on single page

N/A

Verify single-page functionality

7

Test responsive layout

Form adapts to different screen sizes while maintaining section clarity

Various screen resolutions

Responsive design validation

Verification Points:

  • Primary_Verification: Single-page application form displays with six clearly divided sections in logical order
  • Secondary_Verifications: Section headings are prominent and readable, Visual separation is clear between sections, Form maintains single-page layout without reloads, Responsive design works across devices
  • Negative_Verification: No section overlapping, No broken layout elements, No missing section divisions, No page reloads during navigation




Test Case: CIS01US03_TC_002

Title: Verify section navigation and progress indication within single-page form

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_002
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC1, AC20
  • Requirements Traceability: CIS01US03-AC-01, CIS01US03-AC-20

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Navigation-Within-Form, Progress-Indicator, Coverage-AC1-AC20 ,HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC1 navigation aspects
  • Integration_Points: Service-CX, API
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC1 + AC20
  • Cross_Platform_Support: Web

Requirements Traceability

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Form State Management Service

Prerequisites:

  • Single-page form loaded successfully
  • All form sections visible
  • Progress indicator component functional


    Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Application Method Selection

Two method options should be displayed: "AI-Powered Upload" and "Enter Manually"

N/A

Confirm both options are visible

2

Begin with Step 1: Consumer Details

Step 1 is highlighted; Steps 2–6 are inactive

Valid consumer input

Verify "Change Method" and "Next" buttons

3

Click Next

Navigates to Step 2: Address Details; Step 1 shows completed (✔); Step 2 is highlighted

Valid address input

"Save Draft", "Save and Continue", and "Previous" buttons visible

4

Click Save and Continue

Navigates to Step 3: Document Upload; Steps 1–2 are checkmarked; Step 3 is highlighted

Upload required docs

"Next" button remains disabled until uploads are completed

5

Complete Step 3 and click Save and Continue

Navigates to Step 4: Plan Selection; Steps 1–3 completed; Step 4 is highlighted

Select valid plan

"Next" enabled only after selecting a plan

6

Click Save and Continue

Navigates to Step 5: Review; Steps 1–4 completed; Step 5 is highlighted

Valid review inputs

"Submit Application" visible only when validations pass

7

Click Submit Application

Proceeds to Step 6: Payment; Steps 1–5 are checkmarked; Step 6 is highlighted

N/A

Final submission step

8

Use Previous button at each step

Navigates to the immediate prior step with all data preserved

N/A

Backward navigation validation

9

Test section jumping

Can navigate to previously completed sections directly within single page

N/A

Validate jump navigation works correctly

10

Click Save Draft

Saves all current progress without advancing step

N/A

Verify state saved correctly

11

Scroll manually between sections

Layout stays intact with smooth scroll and no visual shifts

N/A

User experience validation


Verification Points:

  • Primary Verifications: Step-by-step navigation flows sequentially from Step 1 to Step 6. Progress indicator updates correctly: current step is highlighted; completed steps show checkmarks. All transitions occur within a single-page layout—no page reloads.
  • Secondary Verifications: Navigation buttons like Next and Submit Application are only enabled after step validation is met. Save Draft preserves data at any step. Previous and Progress Tracker allow smooth navigation to already completed steps. Section data remains persistent across navigation.Scrolling between sections is smooth and consistent with UI expectations.
  • Negative Verifications: No uncompleted step becomes active before the current one is finished.No false progress (e.g., showing a step as completed when it’s not).No loss of form data on navigation.No API delays beyond thresholds (if applicable, <500ms).No broken layouts or reloads during scroll or navigation




TC_ Auto-populate customer information when existing customer found

Test Case: CIS01US03_TC_003

Title: Verify auto-population of customer information for existing customers

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_003
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC2
  • Requirements Traceability: CIS01US03-AC-02

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High,Integration-CustomerDB, Auto-Population, Coverage-AC2,HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC2
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC2

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Customer Database, Address Validation Service
  • Performance_Baseline: Lookup response < 2 seconds

Prerequisites:

  • Customer database contains existing customer records
  • Customer lookup service functional
  • Valid existing customer data available for testing

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Consumer Details section

Consumer Details form displays with empty fields

N/A

Starting point for customer lookup

2

Enter existing customer phone number

Phone field accepts input and triggers validation

"+1-555-0123"

Existing customer identifier

3

Click "Verify" button

System performs customer lookup in database

N/A

Customer search initiation

4

Verify customer found notification

System displays "Existing customer found" message with option to auto-populate

Found customer data

Customer recognition confirmation

5

Accept auto-population option

System auto-populates First Name, Last Name, Email, and previous address information

Expected customer data

Auto-population execution

6

Verify populated field accuracy

All auto-populated fields contain correct customer information

Expected customer data

Data accuracy validation

7

Verify field editability

Auto-populated fields remain editable for updates

N/A

Field modification capability

8

Test with multiple customer records

System correctly identifies and populates data for different existing customers

Multiple customer phone numbers

Multi-customer validation

Verification Points:

  • Primary Verification: System successfully identifies existing customers and auto-populates their information accurately
  • Secondary Verification: Customer lookup completes within performance benchmarks, Auto-populated fields remain editable, System handles multiple customer records correctly
  • Negative Verification: No data corruption during auto-population, No unauthorized access to customer data, Auto-population doesn't override user edits




Test Case: CIS01US03_TC_004

Title: Verify customer lookup failure handling and new customer flow

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_004
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC2
  • Requirements Traceability: CIS01US03-AC-02

Classification:

  • Module/Feature:New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web,  Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,  Error-Handling, New-Customer-Flow, Coverage-AC2, Negative

Business Context:

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

Quality Metrics:

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

Requirements Traceability:

Coverage Tracking:

  • Feature_Coverage: 100% of AC2 error scenarios
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC2 negative cases

Test Environment:

  • Environment: Staging
  • Dependencies: Customer Database Service

Prerequisites:

  • Customer lookup service functional
  • Test phone numbers not in customer database

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Enter new customer phone number

Phone field accepts input

"+1-555-9999"

Non-existing customer

2

Click "Verify" button

System performs lookup and finds no existing customer

N/A

Customer search for new customer

3

Verify new customer handling

System displays "New customer" message and keeps fields empty for manual entry

N/A

New customer flow initiation

4

Test invalid phone format

System validates phone format and shows appropriate error message

"invalid-phone"

Phone validation

5

Verify manual entry capability

All fields remain fully editable for new customer information

N/A

Manual entry validation

Verification Points:

  • Primary Verification: System handles customer lookup failures gracefully and provides clear guidance for new customers
  • Secondary Verification: Error messages are clear and actionable, Manual entry remains functional, Invalid data is properly rejected
  • Negative Verification: No system crashes on lookup failures, No false positive customer matches, Database errors don't expose sensitive information




TC_: Validate phone numbers and email addresses in real-time

Test Case: CIS01US03_TC_005

Title: Verify real-time phone number validation with multiple formats

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_005
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC3
  • Requirements Traceability: CIS01US03-AC-03

Classification:

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

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Phone-Validation, Real-Time, Coverage-AC3, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC3 phone validation
  • Integration_Points: Service-CX, API , Database , Happy path
  • Code_Module_Mapped:CX-Backoffice
  • Requirement_Coverage: Complete AC3 phone aspects

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Phone Validation Service
  • Performance_Baseline: Validation response < 300ms

Prerequisites:

  • Phone validation service functional
  • Real-time validation enabled
  • Consumer Details form accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to phone number field

Phone number field is active and ready for input

N/A

Field accessibility

2

Enter valid phone number format 1

Real-time validation shows checkmark within 300ms

"+1-555-0123"

Standard format validation

3

Clear field and enter valid format 2

Validation immediately updates to show valid status

"(555) 123-4567"

Alternative format validation

4

Enter invalid phone number

Real-time validation shows red error indicator with descriptive message

"123"

Invalid format detection

5

Test multiple invalid formats

Each invalid format triggers immediate error feedback with specific guidance

All invalid formats

Comprehensive error detection

8

Verify validation timing

Validation response occurs within 300ms of last keystroke

Various inputs

Performance validation

Verification Points:

  • Primary Verification: Phone number validation occurs in real-time with immediate visual feedback for both valid and invalid formats
  • Secondary Verification: Multiple phone formats are supported, Validation response time meets performance requirements, Error messages provide clear guidance
  • Negative Verification: Invalid formats are immediately rejected, No false positives for invalid numbers, Validation doesn't interfere with typing




Test Case: CIS01US03_TC_006

Title: Verify real-time email address validation with comprehensive format checking

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_006
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC3
  • Requirements Traceability: CIS01US03-AC-03

Classification:

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

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Email-Validation, Real-Time, Coverage-AC3, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC3 email validation
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC3 email aspects

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Email Validation Service
  • Performance_Baseline: Validation response < 300ms

Prerequisites:

  • Email validation service functional
  • Real-time validation enabled
  • Consumer Details form accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to email address field

Email field is active and ready for input

N/A

Field accessibility

2

Enter valid email address

The system validates the input in real-time 

"user@example.com"

Standard email validation

3

Test complex valid email format

Validation immediately shows valid status for complex formats

"test.email@domain.co.uk"

Complex format support

4

Test email with plus sign

System correctly validates emails with plus addressing

"user+tag@example.org"

Advanced format support

5

Enter incomplete email

Real-time validation shows pending or warning status

"user@"

Partial email handling

6

Enter invalid email format

Immediate error feedback with descriptive message

"invalid-email"

Invalid format detection

7

Test various invalid formats

Each invalid format triggers specific error guidance

All invalid formats

Comprehensive error detection

8

Test domain validation

System validates common domain formats and TLDs

Various domain formats

Domain-specific validation

Verification Points:

  • Primary Verification: Email address validation occurs in real-time with immediate visual feedback for valid and invalid formats
  • Secondary Verification: Complex email formats are supported, Domain validation is accurate, Validation response time meets performance requirements
  • Negative Verification: Invalid email formats are immediately rejected, No false positives for invalid addresses, Validation provides helpful error messages




TC_ Address auto-complete functionality with dropdown suggestions

Test Case: CIS01US03_TC_007

Title: Verify address auto-complete functionality with dynamic dropdown suggestions

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_007
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC4
  • Requirements Traceability: CIS01US03-AC-04

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support:  MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-AddressService, Auto-Complete, Hierarchical-Dependencies, Coverage-AC4,HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC4
  • Integration_Points: Service-CX, API , Happy pat
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC4

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Address Validation Service, Geographic Database
  • Performance_Baseline: Suggestion response < 500ms

Prerequisites:

  • Address validation service functional
  • Geographic database populated
  • Address Details form accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Address Details section

Address form displays with auto-complete enabled fields

N/A

Form accessibility

2

Start typing in street address field

Dropdown suggestions appear after 3 characters

"123 Main"

Auto-complete activation

3

Verify suggestion accuracy

Dropdown shows relevant address suggestions based on input

Expected suggestions

Suggestion relevance

4

Select suggestion from dropdown

Selected address populates the field and closes dropdown

Selected suggestion

Selection functionality

5

Test city field auto-complete

City field shows dropdown suggestions based on partial input

"Bos"

City suggestion system

6

Verify dependent field updates

Selecting city updates area/district dropdown options

Selected city

Dependent field behavior

7

Test area/district auto-complete

Area field shows location-specific suggestions

Partial area input

Hierarchical suggestions

8

Verify suggestion filtering

Suggestions update dynamically as more characters are typed

Extended input

Dynamic filtering

9

Test keyboard navigation

Can navigate suggestions using arrow keys and select with Enter

Keyboard inputs

Accessibility support

10

Verify mobile touch interaction

Dropdown suggestions work correctly on touch devices

Touch interactions

Mobile compatibility

Verification Points:

  • Primary Verification: Address auto-complete provides accurate dropdown suggestions for street, city, and area fields with proper selection functionality
  • Secondary Verification: Suggestions appear within performance benchmarks, Dependent fields update correctly, Keyboard and touch navigation work properly
  • Negative Verification: Invalid addresses don't appear in suggestions, Auto-complete doesn't interfere with manual typing, No performance issues with large suggestion lists




TC_ Document upload through drag-and-drop interface

Test Case: CIS01US03_TC_008

Title: Verify drag-and-drop document upload functionality

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_013
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC7
  • Requirements Traceability: CIS01US03-AC-07

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web,Report-Product, Customer-All, Risk-High,Business-Critical,Revenue-Impact-High,Drag-Drop-Interface, File-Upload, Coverage-AC7,HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC7
  • Integration_Points: Service-CX, API, Database , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC7

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: File Upload Service, Document Storage Service
  • Performance_Baseline: Upload progress feedback < 1 second

Prerequisites:

  • Document upload section accessible
  • Drag-and-drop functionality enabled
  • File upload service operational

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to Document Upload section

Upload interface displays with clear drag-and-drop zone and instructions

N/A

Interface accessibility

2

Verify drag-and-drop zone appearance

Drop zone clearly marked with "Drag and drop files here or click to browse" message

N/A

Visual design validation

3

Drag single file over drop zone

Drop zone highlights with blue border to indicate valid drop target

drivers_license.jpg

Drag feedback validation

4

Drop single file in drop zone

File upload initiates with progress bar showing upload percentage

drivers_license.jpg

Single file upload

5

Verify upload progress tracking

Progress bar shows percentage and estimated time remaining

N/A

Progress indication

6

Confirm successful upload

File appears in uploaded documents list with green checkmark and file details

N/A

Upload completion

7

Test multiple file drag-and-drop

Multiple files can be dragged and dropped simultaneously

3 documents


Verification Points:

  • Primary Verification: Drag-and-drop interface allows successful document upload with clear visual feedback and progress indication
  • Secondary Verification: Multiple files can be uploaded simultaneously, Interface works across different browsers, Mobile devices have appropriate alternatives
  • Negative Verification: Invalid drop areas don't accept files, Drag-and-drop doesn't interfere with other page interactions, Upload failures are handled gracefully




Test Case: CIS01US03_TC_009

Title: Verify drag-and-drop interface validation and error handling

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_014
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC7
  • Requirements Traceability: CIS01US03-AC-07

Classification:

  • Module/Feature:New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web,Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,Drag-Drop-Validation, Error-Handling, Coverage-AC7,Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC7 error scenarios
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC7 validation aspects

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: File Validation Service

Prerequisites:

  • Drag-and-drop interface functional
  • File validation rules configured

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Drag invalid file type to drop zone

Drop zone indicates rejection with appropriate error message

"document.txt"

File type validation

2

Drop oversized file

System rejects file with size limit error message

Oversized file

Size validation

3

Attempt to drop corrupted file

System detects corruption and provides error feedback

Corrupted file

File integrity check

4

Test security-restricted file types

Executable and potentially harmful files are rejected

"executable.exe"

Security validation

5

Verify error message clarity

All error messages provide clear guidance on acceptable file types and sizes

Various invalid files

Error messaging quality

6

Test drag-and-drop outside valid zones

Files dropped outside designated areas don't trigger unwanted actions

Outside drop zone

Boundary validation

Verification Points:

  • Primary Verification: Drag-and-drop interface properly validates file types, sizes, and integrity with clear error messaging
  • Secondary Verification: Security restrictions prevent upload of potentially harmful files, Error messages provide actionable guidance, Interface handles edge cases gracefully
  • Negative Verification: Invalid files don't get uploaded, No security vulnerabilities through file upload, Drag operations don't cause system instability




TC_ Automatically categorize uploaded documents by type

Test Case: CIS01US03_TC_010

Title: Verify automatic document categorization based on file content and metadata

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_015
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC8
  • Requirements Traceability: CIS01US03-AC-08

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Integration, Platform-Web,Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-DocumentAI, Auto-Categorization, Coverage-AC8,HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC8
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC8

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Document AI Service, Classification Engine
  • Performance_Baseline: Categorization completion < 3 seconds

Prerequisites:

  • Document upload functionality working
  • Document AI service operational
  • Classification rules configured

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Upload driver's license document

System automatically categorizes as "ID Proof" with confidence score

"drivers_license.jpg"

ID document recognition

3

Upload utility bill document

System categorizes as "Address Proof" based on utility company letterhead

"utility_bill.pdf"

Address proof recognition

4

Upload property deed

System recognizes legal document format and categorizes as "Property Ownership"

"property_deed.pdf"

Property document recognition

5

Upload income verification

System categorizes as "Income Verification" based on employment content

"pay_stub.pdf"

Income document recognition

6

Upload bank statement

System categorizes as "Financial Document" based on banking content

"bank_statement.pdf"

Financial document recognition

7

Verify categorization speed

All categorizations complete within 3 seconds of upload

N/A

Performance validation

8

Test how the system handles unclear or confusing documents.

System handles documents that could fit multiple categories appropriately

unclear or confusing documents

Edge case handling

Verification Points:

  • Primary Verification: System automatically categorizes uploaded documents with high accuracy based on content analysis and metadata
  • Secondary Verification: Categorization completes within performance benchmarks, Confidence scores are displayed transparently, Manual override capability exists for corrections
  • Negative Verification: Incorrect categorizations don't prevent form submission, Ambiguous documents are handled gracefully, Categorization failures don't break the upload process




Test Case: CIS01US03_TC_011

Title: Verify document categorization error handling

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_016
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC8
  • Requirements Traceability: CIS01US03-AC-08

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web,Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Negative

Manual-Classification, Error-Handling, Coverage-AC8

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC8 error scenarios
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC8 error handling

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Document AI Service

Prerequisites:

  • Document categorization system functional
  • Manual classification interface available

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Upload unclear/blurry document

If the system isn’t sure about the result, it should show low confidence 

"blurry_document.jpg"

Low quality handling

2

Upload non-English document

System handles foreign language gracefully

"foreign_language_doc.pdf"

Language limitation handling

3

Test manual categorization interface

User can easily select correct category from dropdown menu

N/A

Manual interface usability

Verification Points:

  • Primary Verification: The system gracefully handles documents it cannot categorize.
  • Secondary Verification: Manual categorization interface is user-friendly, Service failures don't prevent document upload
  • Negative Verification: Categorization failures don't cause system errors,

TC_ Calculate fees automatically as form sections completed

Test Case: CIS01US03_TC_012

Title: Verify automatic fee calculation as form sections are completed

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_017
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC9
  • Requirements Traceability: CIS01US03-AC-09

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Integration, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Critical, BxServices, HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC9
  • Integration_Points: Service-CX, API ,Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC9

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Billing Engine, Fee Calculation Service
  • Performance_Baseline: Fee calculation < 1 second

Prerequisites:

  • Fee calculation service operational
  • Billing engine configured with current rates
  • Form sections accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Complete Consumer Details section

Base application fee appears in fee summary

N/A

Initial fee calculation

2

Verify initial fee calculation

Application processing fee ($25.00) displayed

Basic application data

Base fee validation

3

Complete Address Details section

Service connection fee added based on property type

Residential property

Property-based fee addition

4

Complete Document Upload section

No additional fees for standard document processing

Standard documents

Document processing validation

5

Complete Plan Selection section

Plan-specific fees and meter size costs added

Standard plan selection

Plan-based calculation

6

Verify cumulative fee calculation

Total shows: Application ($25) + Connection ($75) + Deposit ($150) = $250

N/A

Cumulative calculation

7

Test commercial property calculation

Commercial rates applied: Application ($50) + Connection ($200) + Deposit ($500) = $750

Commercial data

Commercial rate validation

8

Verify real-time updates

Fee summary updates immediately when form sections change

Section modifications

Real-time calculation

9

Test plan change impact

Changing plan updates fees automatically

Plan modification

Dynamic fee adjustment

10

Verify calculation accuracy

All fees match current rate schedule and business rules

Various configurations

Accuracy validation

Verification Points:

  • Primary Verification: Fees are calculated automatically as each form section is completed with accurate amounts based on selections
  • Secondary Verification: Calculations update in real-time when form data changes, Different property types and plans produce correct fee variations, Fee calculations complete within performance benchmarks
  • Negative Verification: Fee calculations don't include inappropriate charges, Calculation errors don't prevent form progression, Invalid selections don't produce nonsensical fees




Test Case: CIS01US03_TC_013

Title: Verify fee calculation accuracy and business rule compliance

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_018
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC9
  • Requirements Traceability: CIS01US03-AC-09

Classification:

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

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Critical, Business-Rules, Calculation-Accuracy, Coverage-AC9, HappyPath, BxServices

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC9 business rules
  • Integration_Points:Service-CX, API , Happy path
  • Code_Module_Mapped:CX-Backoffice
  • Requirement_Coverage: Complete AC9 business scenarios

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Business Rules Engine, Rate Management System

Prerequisites:

  • Fee calculation system functional
  • Business rules configured
  • Rate schedules current

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Apply senior citizen discount

Fee calculation reduces total by 10% with discount line item

Senior citizen data

Discount application

2

Verify discount calculation accuracy

Discount amount correctly calculated and displayed separately

N/A

Discount accuracy

3

Test military discount override

Military discount (15%) replaces senior discount when applicable

Military status

Discount hierarchy

4

Apply rush service surcharge

Additional $100 rush service fee added to total

Rush service request

Surcharge application

5

Test multiple fee modifiers

System correctly applies multiple discounts and surcharges

Complex scenario

Multiple modifier handling

6

Verify tax calculation

Applicable taxes calculated on taxable portions of fees

Tax jurisdiction data

Tax calculation

7

Test fee rounding rules

All monetary amounts rounded to appropriate decimal places

Various calculations

Rounding validation

8

Verify business rule precedence

Conflicting rules resolved according to defined precedence

Conflicting scenarios

Rule precedence

Verification Points:

  • Primary Verification: Fee calculations accurately apply all relevant business rules including discounts, surcharges, and taxes
  • Secondary Verification: Business rule precedence is correctly implemented, Fee rounding follows standard practices, Complex scenarios with multiple modifiers calculated correctly
  • Negative Verification: Inappropriate discounts aren't applied, Conflicting rules don't cause calculation errors, Fee calculations remain within reasonable bounds




TC_ Display real-time fee breakdown with explanations

Test Case: CIS01US03_TC_014

Title: Verify real-time fee breakdown display with detailed explanations

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_019
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC10
  • Requirements Traceability: CIS01US03-AC-10

Classification:

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

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, +Real-Time-Display, Fee-Transparency, Coverage-AC10, BxServices, HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC10
  • Integration_Points: Service-CX
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC10

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Fee Display Service, Help Content System
  • Performance_Baseline: Display update < 500ms

Prerequisites:

  • Fee calculation system working
  • Fee breakdown component functional
  • Help content configured

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Navigate to fee summary section

Fee breakdown displays with all calculated fees

N/A

Breakdown visibility

2

Verify line item detail

Each fee shows: name, amount, and explanation icon/link

Standard breakdown

Detail completeness

3

Click application fee explanation

Detailed explanation appears: "Covers administrative processing and application review"

Application fee

Explanation accuracy

4

Test connection fee explanation

Clear explanation: "One-time fee for physical service connection and meter installation"

Connection fee

Connection fee clarity

5

Verify deposit explanation

Explanation shows: "Refundable security deposit based on credit evaluation and usage estimate"

Deposit fee

Deposit explanation

6

Test real-time updates

Fee breakdown updates immediately when form selections change

Form modifications

Real-time functionality

7

Verify total calculation display

Running total prominently displayed with clear labeling

N/A

Total visibility

8

Test tax breakdown detail

If applicable, taxes shown separately with tax rate information

Tax scenarios

Tax transparency

9

Verify discount display

Discounts shown as negative line items with clear explanations

Discount scenarios

Discount clarity

Verification Points:

  • Primary Verification: Fee breakdown displays in real-time with detailed explanations for each fee component
  • Secondary Verification: All fees have clear, accurate explanations, Display updates immediately with form changes, Mobile devices show readable breakdown
  • Negative Verification: No unexplained fees appear in breakdown, Explanations don't contain errors or confusion, Display doesn't break with complex fee structures




Test Case: CIS01US03_TC_015

Title: Verify fee breakdown transparency and customer education features

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_020
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC10
  • Requirements Traceability: CIS01US03-AC-10

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Customer-Education, Transparency, Coverage-AC10, BxServices, HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC10 education aspects
  • Integration_Points: Service-CX
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC10 transparency aspects

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Help Content System

Prerequisites:

  • Fee breakdown display functional
  • Help content system available
  • Customer education content configured

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Access fee comparison feature

System shows how fees compare to industry standards

N/A

Industry comparison

2

Verify payment option explanations

Clear explanations for each payment timing option (Pay Now, Pay Later, etc.)

Payment options

Payment clarity

3

Test refund policy information

Detailed explanation of deposit refund conditions and timeline

Deposit information

Refund transparency

4

Verify fee schedule access

Link to complete current fee schedule for reference

N/A

Full schedule access

5

Test cost-saving tips

System provides relevant tips for reducing fees where applicable

Cost scenarios

Customer assistance

6

Verify regulatory information

Appropriate regulatory disclosures and rate approval information

Regulatory data

Compliance transparency

Verification Points:

  • Primary Verification: Fee breakdown includes educational content and transparency features to help customers understand charges
  • Secondary Verification: Comparison information helps customers understand value, Payment options are clearly explained, Regulatory compliance information is available
  • Negative Verification: Educational content doesn't contradict fee calculations, Information remains current and accurate, Help features don't interfere with form completion




TC_ Validate all required fields before allowing submission

Test Case: CIS01US03_TC_016

Title: Verify comprehensive required field validation before form submission

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_021
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC11
  • Requirements Traceability: CIS01US03-AC-11

Classification:

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

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Required-Field-Validation, Submission-Prevention, Coverage-AC11 , HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC11
  • Integration_Points: Service-CX,
  • Code_Module_Mapped:CX-Backoffice
  • Requirement_Coverage: Complete AC11

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Validation Service, Form State Management
  • Performance_Baseline: Validation completion < 1 second

Prerequisites:

  • All form sections accessible
  • Required field rules configured
  • Validation service operational

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Attempt submission with empty Consumer Details

Submission prevented with clear indication of missing required fields

Empty form

Consumer validation

2

Complete Consumer Details, leave Address Details empty

Submission blocked with address field requirements highlighted

Partial completion

Address validation

3

Complete Consumer and Address, skip Document Upload

Submission prevented with document requirements shown

Missing documents

Document validation

4

Complete all sections except Plan Selection

Submission blocked until plan is selected

No plan selected

Plan validation

5

Complete all sections with invalid email format

Submission prevented with format validation error

Invalid email

Format validation

6

Test individual required field validation

Each required field properly marked and validated independently

Various field combinations

Individual field validation

7

Verify conditional required fields

Fields required based on property type are properly validated

Conditional scenarios

Conditional validation

8

Test validation message clarity

All validation messages clearly indicate what needs to be corrected

Various error states

Message clarity

9

Verify validation performance

Complete form validation completes within 1 second

Full form

Performance validation

10

Test successful submission after correction

Form submits successfully when all required fields are properly completed

Complete valid form

Successful submission

Verification Points:

  • Primary Verification: Form submission is prevented when any required fields are missing or invalid, with clear indication of what needs correction
  • Secondary Verification: Validation covers all form sections comprehensively, Conditional required fields are properly validated, Validation messages provide clear guidance
  • Negative Verification: Form cannot be submitted with incomplete data, Validation doesn't block submission when all requirements are met, No validation bypasses are possible




Test Case: CIS01US03_TC_017

Title: Verify required field validation across different form states and scenarios

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_022
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC11
  • Requirements Traceability: CIS01US03-AC-11

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,  Validation-States, Edgecases, Coverage-AC11, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC11 edge cases
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC11 edge scenarios

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Validation Service

Prerequisites:

  • Form validation system functional
  • Various form states achievable

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Add secondary consumer and test validation

Secondary consumer fields become required and are validated

Secondary consumer scenario

Dynamic requirement validation

2

Test validation after browser refresh

Form state and validation requirements persist after page refresh

Browser refresh

State persistence

3

Test validation with session timeout

System handles expired sessions gracefully during validation

Session timeout

Session handling

4

Verify validation with auto-populated fields

Auto-populated fields are still subject to validation requirements

Auto-populated data

Auto-population validation

5

Test validation with draft save/restore

Restored draft maintains proper validation requirements

Draft scenario

Draft validation

6

Verify validation order precedence

Critical validations take precedence over minor format issues

Multiple validation errors

Validation prioritization

Verification Points:

  • Primary Verification: Required field validation works correctly across all form states and edge cases
  • Secondary Verification: Dynamic requirements are properly updated, Session handling doesn't bypass validation, Draft restoration maintains validation integrity
  • Negative Verification: No validation bypass through edge cases, System remains secure during validation failures, Form state corruption doesn't disable validation




TC_ Highlight incomplete or invalid fields with clear error messages

Test Case: CIS01US03_TC_018

Title: Verify clear highlighting and error messaging for incomplete/invalid fields

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_023
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC12
  • Requirements Traceability: CIS01US03-AC-12

Classification:

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

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web,Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High,Error-Highlighting, User-Experience, Coverage-AC12, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC12
  • Integration_Points: Service-CX
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC12

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Error Display Service, Accessibility Framework
  • Performance_Baseline: Error display < 200ms

Prerequisites:

  • Form validation system functional
  • Error display components configured
  • Accessibility features enabled

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Leave required field empty and trigger validation

Field highlighted with red border and clear error message

Empty required field

Required field highlighting

2

Verify error message clarity

Message clearly states "This field is required" or similar clear language

N/A

Message clarity validation

3

Enter invalid email format

Email field highlighted with specific format error message

"invalid-email"

Format error highlighting

4

Test phone number format errors

Phone field shows specific guidance: "Please enter a valid phone number (e.g., +1-555-123-4567)"

"123"

Phone format guidance

5

Verify visual highlighting consistency

All error states use consistent color scheme and visual indicators

Various errors

Visual consistency

6

Test error message positioning

Error messages appear close to relevant fields without obscuring other content

N/A

Message positioning

7

Verify accessibility compliance

Error messages are accessible to screen readers 

Screen reader test

Accessibility validation

8

Test multiple simultaneous errors

Multiple field errors displayed clearly without overlap or confusion

Multiple invalid fields

Multiple error handling

9

Verify error clearing behavior

Error highlighting and messages clear when field is corrected

Correct invalid fields

Error resolution

Verification Points:

  • Primary Verification: Incomplete and invalid fields are clearly highlighted with specific, actionable error messages
  • Secondary Verification: Visual highlighting is consistent and accessible, Error messages provide specific guidance for correction, Multiple errors are handled clearly
  • Negative Verification: Error messages don't obscure important content, Highlighting doesn't interfere with form usability, Error states don't persist after correction




Test Case: CIS01US03_TC_019

Title: Verify error message specificity and user guidance quality

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_024
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC12
  • Requirements Traceability: CIS01US03-AC-12

Classification:

  • Module/Feature:New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web,Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,Message-Quality, User-Guidance, Coverage-AC12, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC12 message quality aspects
  • Integration_Points:Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC12 guidance aspects

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Message Content System

Prerequisites:

  • Error messaging system functional
  • Message content configured
  • User guidance rules defined

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Upload oversized file

Specific message: "File size (7MB) exceeds the 5MB limit. Please select a smaller file."

Oversized file

Specific file error

2

Upload unsupported file type

Clear guidance: "Only JPG, PNG, and PDF files are supported. Please select a different file type."

.txt file

File type guidance

3

Enter out-of-territory address

Helpful message: "This address appears to be outside our service area. Please verify the address or contact customer service."

Out-of-area address

Territory guidance

4

Enter duplicate phone number

Clear conflict message: "This phone number is already associated with an existing account. Please use a different number or contact support."

Duplicate phone

Conflict resolution guidance

Verification Points:

  • Primary Verification: Error messages provide specific, actionable guidance that helps users correct issues effectively
  • Secondary Verification: Messages are polite and professional
  • Negative Verification: Messages don't blame users for errors,Messages don't create additional confusion




TC_ Prevent duplicate customer entries based on phone number

Test Case: CIS01US03_TC_020

Title: Verify duplicate customer prevention using phone number validation

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_029
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC15
  • Requirements Traceability: CIS01US03-AC-15

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Integration, Platform-Web,Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High,Integration-CustomerDB, Phone-Validation, Coverage-AC15, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC15
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC15

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Customer Database, Duplicate Detection Service
  • Performance_Baseline: Duplicate check < 2 seconds

Prerequisites:

  • Customer database populated with existing records
  • Duplicate detection service operational
  • Phone validation system working

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Enter phone number of existing customer

System detects duplicate during phone verification

"+1-555-0123"

Duplicate detection

2

Verify duplicate prevention message

Clear message: "This phone number is already associated with an existing account"

N/A

Duplicate notification

3

Test duplicate detection with different phone formats

System recognizes same number in different formats as duplicate

Alternative formats

Format normalization

4

Verify existing customer information display

System shows existing customer name and provides options

Existing customer data

Customer identification

5

Test "Use Existing Customer" 

Provides option to auto-populate from existing customer record

N/A

Existing customer flow

6

Verify new phone number acceptance

Unique phone numbers proceed without duplicate warnings

"+1-555-9999"

New customer validation

7

Test duplicate check performance

Duplicate detection completes within 2 seconds

N/A

Performance validation

Verification Points:

  • Primary Verification: System successfully prevents duplicate customer entries by detecting existing phone numbers with clear user guidance
  • Secondary Verification: Different phone number formats are normalized for duplicate detection, Performance meets requirements, Resolution options are provided
  • Negative Verification:False positives don't occur with similar numbers, System handles edge cases without errors




Test Case: CIS01US03_TC_021

Title: Verify duplicate resolution workflows and data integrity

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_030
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC15
  • Requirements Traceability: CIS01US03-AC-15

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support:MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,  Duplicate-Resolution, Data-Integrity, Coverage-AC15, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC15 resolution scenarios
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC15 resolution aspects

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Customer Support Integration

Prerequisites:

  • Duplicate detection system working
  • Customer support workflows configured
  • Resolution processes defined

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Trigger duplicate detection and select "Contact Support"

Support ticket or contact form initiated with duplicate context

Duplicate scenario

Support integration

2

Verify duplicate context preservation

Support request includes relevant duplicate information

Duplicate data

Context transfer

3

Test legitimate phone number transfer scenario

System provides workflow for transferring phone from old to new account

Transfer scenario

Transfer workflow

4

Verify data integrity during resolution

Original customer data remains protected during resolution process

N/A

Data protection

5

Test false positive correction

System allows correction when duplicate detection is wrong

False positive case

Error correction

6

Verify audit trail creation

All duplicate-related actions are logged for compliance

N/A

Audit logging

Verification Points:

  • Primary Verification: Duplicate resolution workflows maintain data integrity and provide clear paths for legitimate cases
  • Secondary Verification: Support integration works smoothly, Audit trails are properly maintained, False positives can be corrected appropriately
  • Negative Verification: Resolution doesn't compromise existing customer data, Unauthorized changes aren't possible, System maintains security during resolution




TC_Generate unique application ID upon successful submission

Test Case: CIS01US03_TC_022

Title: Verify unique application ID generation upon successful form submission

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_033
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC17
  • Requirements Traceability: CIS01US03-AC-17

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Integration, Platform-Web,Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-IDService, Unique-Generation, Coverage-AC17, Happy path, API

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC17
  • Integration_Points: Service-CX, Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC17

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: ID Generation Service, Application Database
  • Performance_Baseline: ID generation < 1 second

Prerequisites:

  • ID generation service operational
  • Application database accessible
  • Form submission working

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Complete all form sections with valid data

Form ready for submission

Complete application data

Pre-submission validation

2

Submit completed application

Application submits successfully

N/A

Submission success

3

Verify application ID generation

Unique application ID generated and displayed on confirmation page

N/A

ID generation validation

4

Verify ID format compliance

Generated ID follows defined format (e.g., APP-20250603-0001)

Expected format

Format validation

5

Record generated ID for uniqueness testing

Note the generated application ID

Generated ID

ID recording

6

Submit second identical application

New unique ID generated (different from first)

Same application data

Uniqueness validation

7

Test ID generation performance

ID generation completes within 1 second

N/A

Performance validation

8

Verify ID persistence

Generated ID remains consistent across system

Application ID

Persistence validation

9

Test concurrent submission ID uniqueness

Multiple simultaneous submissions generate unique IDs

Concurrent submissions

Concurrency validation

Verification Points:

  • Primary Verification: System generates unique application IDs upon successful submission with proper format and immediate availability
  • Secondary Verification: IDs remain unique across multiple submissions, Format compliance is maintained, Performance meets requirements
  • Negative Verification: No duplicate IDs are generated, Submission failures don't consume ID sequence, Concurrent submissions don't create conflicts




Test Case: CIS01US03_TC_023

Title: Verify application ID integration with tracking and reference systems

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_034
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC17
  • Requirements Traceability: CIS01US03-AC-17

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Integration
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Integration, Platform-Web,Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,ID-Integration, Tracking-Systems, Coverage-AC17, HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC9
  • Integration_Points:Service-CX, API , Happy path
  • Code_Module_Mapped:CX-Backoffice
  • Requirement_Coverage: Complete AC9

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Billing Engine, Fee Calculation Service
  • Performance_Baseline: Fee calculation < 1 second

Prerequisites:

  • Fee calculation service operational
  • Billing engine configured with current rates
  • Form sections accessible

Test Procedure:

Step

What To Do

What Should Happen

Why This Fee Amount

Step

1

Complete Consumer Details section

Application fee shows up ($25)

Every application pays processing fee

1

2

Check the fee amount

$25.00 displayed for application fee

Base fee from rate schedule

2

3

Complete Address Details section

Connection fee gets added ($75 for residential)

Physical connection cost varies by property type

3

4

Complete Document Upload section

No new fees added

Document processing is included in application fee

4

5

Complete Plan Selection section

Meter cost and plan fees get added

Different meter sizes cost different amounts

5

6

Check total calculation

Total shows $250 ($25 + $75 + $150)

All residential fees added together

6

7

Test with commercial property

Fees change to $750 ($50 + $200 + $500)

Commercial rates are higher than residential

7

8

Change something in the form

Fees update immediately

System recalculates in real-time

8

9

Change the service plan

Plan fees update automatically

Different plans have different costs

9

10

Verify all calculations are correct

All fees match the official rate schedule

Must follow utility company's approved rates

10

Verification Points:

  • Primary Verification: Fees are calculated automatically as each form section is completed with accurate amounts based on selections
  • Secondary Verification: Calculations update in real-time when form data changes, Different property types and plans produce correct fee variations, Fee calculations complete within performance benchmarks
  • Negative Verification: Fee calculations don't include inappropriate charges, Calculation errors don't prevent form progression, Invalid selections don't produce nonsensical fees




TC_Display confirmation page with application details after submission

Test Case: CIS01US03_TC_024

Title: Verify comprehensive confirmation page display after successful application submission

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_035
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC18
  • Requirements Traceability: CIS01US03-AC-18

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web,Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High,Confirmation-Display, Application-Summary, Coverage-AC18. Database ,HappyPath, BxServices

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC18
  • Integration_Points: Service-CX, API ,Happy path
  • Code_Module_Mapped: CX-Backoffice
  • Requirement_Coverage: Complete AC18

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Application Data Service, Email Service
  • Performance_Baseline: Page load < 2 seconds

Prerequisites:

  • Application submission successful
  • Confirmation page components functional
  • Application data accessible

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Complete and submit application successfully

Confirmation page loads immediately after submission

Complete application

Page navigation

2

Verify success message with icon

"Application Successfully Submitted" with green checkmark icon displayed

N/A

Success indication

3

Check Consumer ID display

Consumer ID shown (e.g., CID-2025060001)

Generated Consumer ID

ID visibility

4

Verify Application Fee Summary section

Section shows "Application Fee Summary:" as header

N/A

Fee summary header

5

Check Application Processing Fee

Application Processing Fee: $25.00 displayed

$25.00

Processing fee

6

Check Service Connection Fee

Service Connection Fee: $75.00 displayed

$75.00

Connection fee

7

Check Security Deposit

Security Deposit: $150.00 displayed

$150.00

Deposit amount

8

Verify Total Due amount

Total Due: $250.00 displayed prominently

$250.00

Total calculation

9

Check payment completion message

"Payment Completed Successfully!" with green checkmark icon

N/A

Payment confirmation

10

Verify change to return

amount to be returned back to consumer

Change amount

Cash payment handling

11

Check "Add Another Consumer" button

Button visible and clickable

N/A

Add consumer button

12

Test "Add Another Consumer" functionality

Clicking button takes to Step 1 (Consumer Details) for new application

N/A

New consumer flow

13

Check "Return to Dashboard" button

Button visible and clickable

N/A

Dashboard button

14

Test "Return to Dashboard" functionality

Clicking button returns to Consumer Onboarding dashboard

N/A

Dashboard navigation

Verification Points :
Primary Verification:

  • Confirmation page displays "Application Successfully Submitted" with green checkmark
  • Consumer ID is generated and shown
  • Complete fee breakdown with correct amounts
  • "Payment Completed Successfully!" with green checkmark
  • Both navigation buttons work correctly

Secondary Verification:

  • All fee amounts are accurate ($25 + $75 + $150 = $250)
  • Change amount displayed correctly for cash payments
  • Button navigation takes to correct destinations
  • Page layout is clear and professional

Negative Verification:

  • No incorrect fee calculations shown
  • No broken navigation buttons
  • Payment status always shows as completed
  • Consumer ID is never missing or duplicate




Test Case: CIS01US03_TC_025

Title: Verify confirmation page functionality and user guidance features

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_036
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC18
  • Requirements Traceability: CIS01US03-AC-18

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,  User-Guidance, Confirmation-Features, Coverage-AC18, HappyPath

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC18 functionality aspects
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped: CX-Backofficer
  • Requirement_Coverage: Complete AC18 user features

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Email Service, Document Generation Service

Prerequisites:

  • Confirmation page accessible
  • Supporting services operational

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Verify processing timeline display

Clear timeline showing application review (2-3 business days)

Timeline information

Timeline accuracy

2

Check email confirmation mention

Confirmation states email copy will be sent to provide address

Customer email

Email notification

3

Test "Return to Dashboard" functionality

Button successfully navigates back to main dashboard

N/A

Navigation functionality

4

Verify "Submit Another Application" option

Option available to start new application process

N/A

Workflow continuation

5

Check FAQ or help section access

Links to relevant help content for post-submission questions

Help content

Support resources

6

Test mobile responsiveness

Confirmation page displays properly on mobile devices

Mobile view

Mobile compatibility

7

Verify social sharing options (if applicable)

Options to share confirmation or refer others

Social features

Sharing functionality

Verification Points:

  • Primary Verification: Confirmation page provides comprehensive user guidance and functional options for next steps
  • Secondary Verification: Timeline information is accurate, Email confirmation process works, Navigation options function properly
  • Negative Verification: No broken links or functionality, Mobile experience remains complete, Support resources are current and helpful




TC_ Maintain form data integrity during validation and error correction

Test Case: CIS01US03_TC_026

Title: Verify form data integrity during validation processes and error correction

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_037
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC19
  • Requirements Traceability: CIS01US03-AC-19

Classification:

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

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P1-Critical, Phase-Regression, Type-Functional, Platform-Web,Report-Product, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High,Data-Preservation, Validation-Integrity, Coverage-AC19, Negative

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC19
  • Integration_Points: Service-CX
  • Code_Module_Mapped:CX-Backoffice
  • Requirement_Coverage: Complete AC19

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Dependencies: Data Storage Service, Validation Engine
  • Performance_Baseline: Data preservation < 500ms

Prerequisites:

  • Form validation system functional
  • Data storage mechanisms working
  • Error correction workflows available

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Fill form with mix of valid and invalid data

Form accepts all input without data loss

Mixed valid/invalid data

Data acceptance

2

Trigger form validation

Validation identifies errors while preserving all entered data

N/A

Validation execution

3

Verify data preservation during validation

All valid data remains intact in form fields

Valid data portions

Data retention

4

Correct invalid email field

Email correction preserves all other field data

Invalid to valid email

Field correction

5

Verify cross-section data integrity

Correcting error in one section doesn't affect other sections

Multi-section scenario

Cross-section integrity

6

Test error correction workflow

Step-by-step error correction maintains form state

Error correction process

Workflow integrity

7

Verify file upload preservation

Uploaded files remain attached 

Uploaded documents

File attachment integrity

8

Test session interruption recovery

Data stays safe and unchanged even if the session gets interrupted or disconnected.

Session interruption

Session recovery integrity

Verification Points:

  • Primary Verification: Form data integrity is maintained throughout all validation processes and error correction workflows
  • Secondary Verification: Cross-section data preservation works correctly, File attachments remain intact, Session interruptions don't cause data loss
  • Negative Verification: No data corruption during validation, Error corrections don't affect unrelated fields, Validation failures don't result in data loss




Test Case: CIS01US03_TC_027

Title: Verify data integrity under stress conditions and edge cases

Test Case Metadata:

  • Test Case ID: CIS01US03_TC_038
  • Created By: Hetal
  • Created Date: 2025-06-03
  • Version: 1.0
  • Acceptance Criteria: AC19
  • Requirements Traceability: CIS01US03-AC-19

Classification:

  • Module/Feature: New Service Connection Application Form
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

Enhanced Tags for 17 Reports Support: MOD-CX-Backoffice, P2-High, Phase-Regression, Type-Functional, Platform-Web,Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium,Stress-Testing, Edge-Cases, Coverage-AC19,EdgeCase

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

  • Feature_Coverage: 100% of AC19 stress scenarios
  • Integration_Points: Service-CX, API , Happy path
  • Code_Module_Mapped:CX-Backoffice
  • Requirement_Coverage: Complete AC19 edge cases

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Dependencies: Data Storage Service

Prerequisites:

  • Data integrity system functional
  • Stress testing tools available

Test Procedure:

Step

Action

Expected Result

Test Data

Comments

1

Perform rapid sequential field changes

Data integrity maintained during rapid input

Rapid input sequence

High-frequency changes

2

Test large form data handling

System handles maximum data volumes without corruption

Large data set

Volume stress testing

3

Simulate network interruptions during validation

Data preserved despite network issues

Network interruption

Network resilience

4

Test recovery from validation service failures

Data stays correct and is not lost even if the validation service stops working.

Service failure

Service resilience

Verification Points:

  • Primary Verification: Data integrity is maintained under stress conditions and edge cases
  • Secondary Verification: System handles resource limitations gracefully, Service failures don't corrupt data, Concurrent operations remain stable
  • Negative Verification: Stress conditions don't cause data loss, Edge cases don't break validation integrity, System remains stable under adverse conditions