Skip to main content

Settings (CIS01US07)

Settings (CIS01US07) Test Suite

Test Scenario Summary

High-Level Test Scenarios Overview

A. Functional Test Scenarios

Core Functionality Scenarios:

  1. Service Category Management (Create, Edit, Delete, Hierarchy)
  2. Service Configuration Management (CRUD Operations)
  3. Complaint Category Management (Create, Edit, Delete, Hierarchy)
  4. Complaint Type Configuration (CRUD Operations)
  5. SLA Configuration and Validation
  6. Search and Filter Functionality
  7. Import/Export Capabilities
  8. Navigation and Tab Management

Business Rules Scenarios:

  1. Category Hierarchy Validation (Parent-Child Relationships)
  2. Duplicate Prevention (Categories, Subcategories, Service Codes)
  3. SLA Time Validation (Response ≤ Resolution Time)
  4. Status Management (Active/Inactive Toggle)
  5. Code Format Validation
  6. Required Field Validation

User Journey Scenarios:

  1. Utility Administrator Complete Configuration Setup
  2. CSO Manager Performance Monitoring Workflow
  3. Cross-Platform Configuration Management
  4. Bulk Configuration Management

B. Non-Functional Test Scenarios

Performance Scenarios:

  • Page load times < 3 seconds
  • Search response times < 1 second
  • Concurrent user handling (50+ users)
  • Large dataset handling (1000+ categories)

Security Scenarios:

  • Role-based access control validation
  • Session management testing
  • Data encryption verification
  • Input sanitization testing

Compatibility Scenarios:

  • Cross-browser testing (Chrome, Firefox, Safari, Edge)
  • Cross-device testing (Desktop, Tablet, Mobile)
  • Screen resolution compatibility

Usability Scenarios:

  • Navigation flow testing
  • Error message clarity
  • Form validation feedback
  • User interface consistency

C. Edge Case & Error Scenarios

Boundary Conditions:

  • Maximum character limits for names/descriptions
  • Minimum/Maximum SLA time values
  • Category hierarchy depth limits
  • Concurrent modification handling

Invalid Input Scenarios:

  • Special characters in category names
  • Invalid time formats
  • Malformed service codes
  • SQL injection attempts

System Failure Scenarios:

  • Network interruption during save operations
  • Browser crashes during form submission
  • Session timeout handling
  • Database connection failures




Detailed Test Cases

SMOKE TEST SUITE (P1 Critical)




Test Case CIS01US07_TC_001

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_001
  • Title: Verify successful login and navigation to Service Categories
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

  • Module/Feature: Navigation & Authentication
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Automated

Enhanced Tags: Tags: MOD-Navigation, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Core

Business Context:

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

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: 15%
  • Integration_Points: CX Web, Authentication Service
  • Code_Module_Mapped: Authentication, Navigation
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+, Firefox 110+, Safari 16+, Edge Latest
  • Device/OS: Windows 10/11, macOS 12+
  • Screen_Resolution: 1920x1080
  • Dependencies: Authentication Service, Database
  • Performance_Baseline: < 3 seconds page load
  • Data_Requirements: Valid utility admin credentials

Prerequisites:

  • Setup_Requirements: Test environment deployed and accessible
  • User_Roles_Permissions: Utility Administrator role assigned
  • Test_Data: Username: admin@pacificwater.com, Password: TestPass123!
  • Prior_Test_Cases: Environment validation completed

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to application URL

Login page displays within 3 seconds

https://app.utility-cx.com

Baseline performance check

2

Enter valid admin credentials

Fields accept input without errors

admin@pacificwater.com / TestPass123!

Verify credential validation

3

Click Login button

Successfully redirected to dashboard

N/A

Check authentication flow

4

Click Settings menu item

Settings page loads with 5 main tabs

N/A

Verify main navigation

5

Click Services tab

Services tab activates with 2 sub-tabs visible

N/A

Check tab structure

6

Verify Categories sub-tab

Categories sub-tab is active by default

N/A

Default view validation

7

Verify Service Configuration sub-tab

Sub-tab is visible and clickable

N/A

Navigation option check

Verification Points:

  • Primary_Verification: User successfully reaches Service Categories page
  • Secondary_Verifications: All navigation elements are functional, page loads within performance baseline
  • Negative_Verification: No error messages displayed, no broken UI elements




Test Case CIS01US07_TC_002

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_002
  • Title: Create new water service category successfully
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

Enhanced Tags: Tags: MOD-ServiceCategories, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Dependencies: Database, Authentication Service
  • Performance_Baseline: < 2 seconds save operation
  • Data_Requirements: Clean category dataset

Prerequisites:

  • User_Roles_Permissions: Utility Administrator access
  • Test_Data: Category Name: "Water Connection Services"
  • Prior_Test_Cases: CIS01US07_TC_001 must pass

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Service Categories page

Page loads with category hierarchy view

N/A

Via CIS01US07_TC_001

2

Click "Add New Category" button

Add category form appears

N/A

Form display validation

3

Enter category name

Field accepts input, no validation errors

"Water Connection Services"

Water utility specific data

4

Click "Create Category" button

Category created successfully, form closes

N/A

Save operation timing

5

Verify category in hierarchy

New category appears in list with Active status

N/A

Data persistence check

6

Verify category properties

Shows "0 subcategories", Active toggle enabled

N/A

Default state validation

Verification Points:

  • Primary_Verification: Category "Water Connection Services" is created and visible in hierarchy
  • Secondary_Verifications: Category has correct default status, form closes properly, no duplicate entries
  • Negative_Verification: No error messages, no system crashes




Test Case CIS01US07_TC_003

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_003
  • Title: Create new water connection service with SLA configuration
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

Enhanced Tags: Tags: MOD-ServiceConfig, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, SLA-Critical

Test Environment:

  • Environment: Staging
  • Browser/Version: Chrome 115+
  • Dependencies: Service categories must exist
  • Performance_Baseline: < 3 seconds form submission

Prerequisites:

  • Test_Data: Service: "Residential Water Connection", Code: "RWC-NEW-001", Category: "Water Connection Services"
  • Prior_Test_Cases: CIS01US07_TC_002 must pass

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Service Configuration tab

Service list page loads

N/A

Tab navigation

2

Click "Add New Service" button

Create service modal opens

N/A

Modal display

3

Enter service name

Field accepts input

"Residential Water Connection"

Water utility service

4

Enter service code

Field accepts unique code

"RWC-NEW-001"

Code format validation

5

Select service category

Dropdown shows available categories

"Water Connection Services"

Category dependency

6

Select service subcategory

Dropdown updates based on category

"New Installations"

Dynamic dropdown

7

Set response time

Field accepts numeric value

24

SLA configuration

8

Set resolution time

Field accepts value > response time

72

Business rule validation

9

Configure workflow settings

Toggle field work required ON

Yes

Workflow configuration

10

Click "Create Service" button

Service created successfully

N/A

Complete creation flow

11

Verify in service list

New service appears with correct details

N/A

Data persistence

Verification Points:

  • Primary_Verification: Service "Residential Water Connection" created with SLA parameters
  • Secondary_Verifications: Service code is unique, SLA times are validated, workflow settings saved
  • Negative_Verification: Resolution time validation enforced (must be ≥ response time)




REGRESSION TEST SUITE (P1-P2 Priority)




Test Case CIS01US07_TC_004

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_004
  • Title: Verify service category hierarchy with subcategories creation
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

  • Module/Feature: Service Categories
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Automated

Enhanced Tags: Tags: MOD-ServiceCategories, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Integration-Core

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Create parent category

Category created successfully

"Water Distribution Services"

Parent level

2

Click "+" button next to category

Subcategory form appears

N/A

Hierarchy expansion

3

Add first subcategory

Subcategory created under parent

"Meter Installation"

Child level 1

4

Add second subcategory

Second subcategory created

"Meter Replacement"

Child level 2

5

Verify parent category display

Shows "2 subcategories" count

N/A

Count accuracy

6

Test expand/collapse functionality

Subcategories show/hide correctly

N/A

UI behavior

7

Verify subcategory independence

Each subcategory has own Active toggle

N/A

Individual controls




Test Case CIS01US07_TC_005

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_005
  • Title: Validate SLA time business rules enforcement
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

Enhanced Tags: Tags: MOD-ServiceConfig, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical, SLA-Critical

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Open Create Service form

Form displays with SLA fields

N/A

Form initialization

2

Enter response time

Field accepts valid value

48

Valid response time

3

Enter resolution time less than response

Validation error displayed

24

Invalid: 24 < 48

4

Verify error message

Clear error message shown

"Resolution time must be ≥ Response time"

User guidance

5

Correct resolution time

Error clears, form submittable

72

Valid: 72 > 48

6

Test equal values

Both times equal should be valid

48/48

Boundary condition

7

Test zero values

Validation prevents zero/negative

0/-1

Invalid input handling




Test Case CIS01US07_TC_006

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_006
  • Title: Verify complaint category and type creation workflow
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

Enhanced Tags: Tags: MOD-ComplaintConfig, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-CSM, Customer-Enterprise, Risk-High, Business-Critical

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to Complaints tab

Complaints section loads

N/A

Tab navigation

2

Create complaint category

Category created successfully

"Water Quality Issues"

Complaint category

3

Add subcategory

Subcategory created under parent

"Taste and Odor"

Specific issue type

4

Navigate to Complaint Types

Types configuration page loads

N/A

Sub-tab navigation

5

Create complaint type

Type creation form opens

N/A

Type configuration

6

Configure basic information

Required fields completed

"Water Taste Complaint", "WTC-TASTE-001"

Water utility data

7

Set complaint classification

Category/subcategory selected

"Water Quality Issues"/"Taste and Odor"

Category linkage

8

Configure resolution timeframes

SLA times set appropriately

Ack: 2hrs, Response: 4hrs, Resolution: 24hrs

Complaint SLA

9

Set closure requirements

Customer confirmation required

Yes

Quality control

10

Create complaint type

Type created and appears in list

N/A

End-to-end workflow




FULL TEST SUITE (All Priority Levels)




Test Case CIS01US07_TC_007

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_007
  • Title: Search and filter functionality across service configurations
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

  • Module/Feature: Search & Filter
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Full
  • Automation Status: Automated

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Access Service Configuration page

Services list displays

N/A

Baseline state

2

Enter service name in search

Filtered results display

"Water Connection"

Name-based search

3

Clear search, enter service code

Code-based filtering works

"RWC-NEW"

Partial code match

4

Test case-insensitive search

Search works regardless of case

"water connection"

Case handling

5

Use filters dropdown

Filter options display

N/A

Filter availability

6

Apply status filter

Only active services shown

Active

Status filtering

7

Apply priority filter

Priority-specific results

High

Priority filtering

8

Combine search and filters

Combined filtering works

"Water" + High priority

Multiple criteria

9

Test empty search results

"No results" message displayed

"NonexistentService"

Empty state handling




Test Case CIS01US07_TC_008

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_008
  • Title: Category import functionality validation
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

  • Module/Feature: Data Import
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P3-Medium
  • Execution Phase: Full
  • Automation Status: Manual

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

Click "Import Categories" button

File upload dialog opens

N/A

Import initiation

2

Select valid CSV file

File uploads successfully

categories_water_utility.csv

Water utility categories

3

Verify import preview

Categories preview correctly

See sample data below

Data validation

4

Confirm import

Categories imported to system

N/A

Import completion

5

Verify in category list

Imported categories visible

N/A

Data persistence

6

Test invalid file format

Error message displayed

.txt file

Format validation

7

Test malformed CSV

Validation errors shown

Invalid CSV structure

Error handling

Sample Import Data:

Category Name,Parent Category,Status

Billing Services,,Active

Account Management,Billing Services,Active

Payment Processing,Billing Services,Active

Emergency Services,,Active

Water Main Breaks,Emergency Services,Active





Test Case CIS01US07_TC_009

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_009
  • Title: Concurrent user modification conflict handling
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

  • Module/Feature: Concurrency Control
  • Test Type: Functional
  • Test Level: System
  • Priority: P2-High
  • Execution Phase: Full
  • Automation Status: Manual

Test Procedure:

Step #

Action

Expected Result

Test Data

Comments

1

User A opens service for editing

Edit form loads

"Emergency Repair Service"

First user session

2

User B opens same service

Edit form loads independently

Same service

Second user session

3

User A modifies response time

Change saved successfully

2 hours → 1 hour

First modification

4

User B modifies priority level

Conflict detection occurs

Normal → High

Concurrent modification

5

Verify conflict resolution

Appropriate conflict message

"Service modified by another user"

Conflict handling

6

User B refreshes data

Latest changes loaded

Updated response time visible

Data refresh

7

User B reapplies changes

Changes saved successfully

Priority: High

Conflict resolution




PERFORMANCE TEST SCENARIOS




Test Case CIS01US07_TC_010

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_010
  • Title: Page load performance validation under normal load
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

Enhanced Tags: Tags: MOD-Performance, P2-High, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High

Performance Benchmarks:

  • Service Categories page load: < 3 seconds
  • Service Configuration page load: < 3 seconds
  • Search response time: < 1 second
  • Form submission: < 2 seconds

Test Procedure:

Step #

Action

Expected Result

Performance Target

Comments

1

Load Service Categories page

Page loads completely

< 3 seconds

Cold load performance

2

Navigate between sub-tabs

Tab switching responsive

< 0.5 seconds

UI responsiveness

3

Perform search operation

Results display quickly

< 1 second

Search performance

4

Open service creation form

Modal opens responsively

< 0.5 seconds

Form load time

5

Submit service creation

Save operation completes

< 2 seconds

Transaction performance

6

Load large category list

Page handles 100+ categories

< 3 seconds

Data volume handling




API TEST CASES (Critical Level ≥7)




Test Case CIS01US07_TC_011

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_011
  • Title: Service Category API CRUD operations validation
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

API Endpoints Tested:

  • POST /api/v1/service-categories
  • GET /api/v1/service-categories
  • PUT /api/v1/service-categories/{id}
  • DELETE /api/v1/service-categories/{id}

Test Procedure:

Step #

API Call

Expected Response

Test Data

Validation

1

POST /api/v1/service-categories

201 Created

{"name": "Water Billing Services", "status": "active"}

Category creation

2

GET /api/v1/service-categories

200 OK, category in list

N/A

Retrieve validation

3

PUT /api/v1/service-categories/{id}

200 OK

{"name": "Updated Billing Services"}

Update operation

4

DELETE /api/v1/service-categories/{id}

204 No Content

N/A

Deletion validation

5

GET /api/v1/service-categories/{id}

404 Not Found

N/A

Deletion confirmation




SECURITY TEST SCENARIOS




Test Case CIS01US07_TC_012

Test Case Metadata:

  • Test Case ID: CIS01US07_TC_012
  • Title: Input sanitization and SQL injection prevention
  • Created By: QA Team
  • Created Date: 2025-06-02
  • Version: 1.0

Classification:

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

Test Procedure:

Step #

Action

Expected Result

Malicious Input

Comments

1

Attempt SQL injection in category name

Input sanitized, no DB compromise

"'; DROP TABLE categories; --"

SQL injection test

2

Test XSS in service description

Script tags escaped

"<script>alert('XSS')</script>"

XSS prevention

3

Test oversized input

Validation error returned

1000+ character string

Buffer overflow test

4

Test special characters

Characters properly handled

"Category & <Service> #1"

Character encoding

5

Verify CSRF protection

Token validation enforced

N/A

CSRF prevention




Test Suite Organization

Smoke Test Suite (Execution: Every Build)

  • CIS01US07_TC_001: Basic Navigation
  • CIS01US07_TC_002: Service Category Creation
  • CIS01US07_TC_003: Service Configuration Creation

Execution Time: ~10 minutes Automation Rate: 100%

Regression Test Suite (Execution: Before Release)

  • All Smoke tests +
  • CIS01US07_TC_004: Category Hierarchy
  • CIS01US07_TC_005: SLA Validation
  • CIS01US07_TC_006: Complaint Workflow
  • CIS01US07_TC_009: Concurrent Users

Execution Time: ~45 minutes Automation Rate: 95%

Full Test Suite (Execution: Weekly/Major Release)

  • All Regression tests +
  • CIS01US07_TC_007: Search & Filter
  • CIS01US07_TC_008: Import Functionality
  • CIS01US07_TC_010: Performance Tests
  • CIS01US07_TC_011: API Tests
  • CIS01US07_TC_012: Security Tests

Execution Time: ~2 hours Automation Rate: 85%




Execution Matrix

Test Case

Chrome

Firefox

Safari

Edge

Mobile

Priority

TC_001-003

P1

TC_004-006

-

P1-P2

TC_007-009

-

-

-

P2-P3

TC_010-012

-

-

-

-

P1-P2




Integration Test Dependencies

External Dependencies:

  • Authentication Service (CX Core)
  • Database Service
  • File Upload Service

Test Execution Order:

  1. Prerequisites: Authentication & Environment
  2. Core Features: Categories → Services → Complaints
  3. Advanced Features: Search, Import, Performance
  4. Security & Edge Cases: Final validation

Failure Handling:

  • Skip dependent tests when prerequisites fail
  • Log all dependency failures for analysis
  • Provide alternative test paths where possible




Water Utility Test Data Sets

Service Categories:

Water Connection Services

├── New Installations

├── Reconnections

├── Service Upgrades

└── Disconnections


Water Quality Services

├── Testing & Analysis

├── Treatment Issues

└── Contamination Response


Billing & Payment Services

├── Account Management

├── Payment Processing

└── Dispute Resolution


Sample Services:

Residential Water Connection (RWC-NEW-001)

Commercial Water Installation (CWI-NEW-001)

Emergency Water Shutoff (EWS-EMRG-001)

Water Quality Testing (WQT-TEST-001)

Billing Inquiry Resolution (BIR-SUPP-001)


Complaint Types:

Low Water Pressure (LWP-PRES-001)

Water Quality Issues (WQI-QUAL-001)

Billing Disputes (BD-BILL-001)

Service Interruptions (SI-SERV-001)


This comprehensive test suite covers all functional requirements, business rules, and quality attributes while providing complete support for the 17 BrowserStack test management reports through detailed tagging and classification.