Bill Cycle Setup (BX03US02)

Coverage Summary

• Total Coverage: 100%
• Total Test Cases: 18(13 Functional + 2 Performance/Integration + 1 Security)
• Total Acceptance Criteria: 20 Coverage Percentage: (20/20) × 100 = 100%
• Priority Distribution: 9 P1-Critical (56%) + 7 P2-High (44%)

Test Scenario Analysis

A. Functional Test Scenarios

Core Functionality Scenarios

1. Dashboard Metrics Display - Real-time display of consumer coverage, active cycles, and performance indicators
2. Bill Cycle Creation - Complete cycle creation workflow with validation
3. Premise Selection - Area-based filtering and premise selection with consumer count updates
4. Consumer Management - Individual consumer selection and category breakdown
5. Cycle Monitoring - Performance tracking and billing summary analysis
6. Historical Analysis - Trend analysis and run history tracking
7. Search and Filter Operations - Advanced search across cycles and consumers
8. Export Functionality - Data export capabilities across different views

Business Rules Scenarios (Weighted by Importance)

1. Cycle Uniqueness Validation (Weight: 10) - Prevent duplicate cycle names
2. Consumer Eligibility Rules (Weight: 9) - Only Active and Temp Disconnected consumers
3. Billing Duration Constraints (Weight: 8) - Valid duration ranges and restrictions
4. Premise Assignment Logic (Weight: 8) - Prevent overlapping cycle assignments
5. Real-time Count Updates (Weight: 7) - Dynamic consumer count calculations
6. Status-based Operations (Weight: 7) - Active/Inactive cycle management
7. Permission-based Access (Weight: 6) - Role-specific functionality access

User Journey Scenarios

1. Billing Manager Complete Workflow - Dashboard → Create Cycle → Monitor Performance → Analyze Trends
2. Billing Specialist Execution Flow - View Cycles → Execute Billing → Track Progress → Handle Exceptions
3. Monthly Cycle Management - Create → Configure → Execute → Monitor → Report
4. Exception Handling Journey - Identify Issues → Investigate → Resolve → Document

B. Non-Functional Test Scenarios

Performance Scenarios

• Dashboard load time < 1 second
• Cycle creation response < 1 second
• Consumer count updates in real-time
• Large dataset handling (>10,000 consumers)
• Concurrent user operations

Security Scenarios

• Authentication validation
• Role-based authorization
• Data access controls
• Input validation and sanitization
• Session management

Compatibility Scenarios

• Chrome latest version compatibility
• Responsive design validation
• Cross-resolution support (1920x1080, 1024x768, 375x667)

Usability Scenarios

• Intuitive navigation flow
• Error message clarity
• Loading state indicators
• Data validation feedback

C. Edge Case & Error Scenarios

Boundary Conditions

• Maximum consumer count per cycle
• Minimum billing duration (1 day)
• Maximum billing duration limits
• Empty premise selections
• Zero consumer scenarios

Invalid Input Scenarios

• Duplicate cycle names
• Invalid billing durations
• Malformed search queries

System Failure Scenarios

• Meter data service unavailability
• Database connection issues
• Large dataset timeout scenarios
• Export operation failures

---

BX03US02_TC_001:-Verify Dashboard Metrics Display. 

Title: Verify Dashboard Metrics Display. 

Created By: Sarvesh

Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Dashboard Overview
• Test Type: Functional/UI
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Not-Automated

Enhanced Tags: Happy-Path, Consumer Services, API

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of dashboard metrics
• Integration_Points: Billing Services, Consumer database
• Code_Module_Mapped: - (BX03US02) - dashboard metrics
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: Acceptance Criteria #1
• Related_Bugs: N/A
• Related_Test_Cases: Consumer Creation, Cycle Creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites:

• Setup_Requirements: Test data with active billing cycles
• User_Roles_Permissions: Billing Manager access
• Test_Data: 24 total cycles, 18 active cycles, consumer coverage data
• Prior_Test_Cases: Login, Navigate to BX by bento menu, Bill Cycle Creation, Consumer creation

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Navigate to Billing module	Dashboard loads successfully	Valid credentials	Page loads < 1 sec
2	Verify Consumer Coverage metric	Consumer Coverage metric displays accurately eg:- 84% (+2% from last month) according to the farmulae mention (Consumer Coverage (%) = (Consumers Assigned to Billing Cycles / Total Active Consumers) × 100 )	Live consumer data	Green indicator for positive trend and Red for negative trend
3	Verify Active Cycles count	Active Cycles count displays accurately for eg:- 18 (75% of total 24 cycles) according to the farmulae mention (Active Cycle % = (Active Billing Cycles / Total Billing Cycles) × 100 )	Active cycle data	Correct calculation displayed
4	Verify Average Run Count	Shows accurate average runs count for eg:- 4.3 per cycle (Average Run Count = Total Number of Billing Runs / Number of Billing Cycles )	Historical run data	Accurate average calculation
5	Verify Total Billing Cycles	Shows eg:- 24 (+2 this month) (Total Billing Cycles = All Created Billing Cycles (Active + Inactive) )	Total cycle count	Growth indicator present according to new billing cycles were added this month. Green for positive and red for negative

Verification Points:

• Primary_Verification: All four metrics display correct values with accrurate indictor with color as per mention formulas
• Secondary_Verifications: Trend indicators, percentage calculations, tooltips
• Negative_Verification: No error messages or loading failures, wrong data in KPI, inaccurate indicator and count in Kpi

---

BX03US02_TC_002 : Search and Filter Functionality 

Title: Verify Search and Filter Functionality 

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags: Database, Happy-Path

MOD-BX, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Low

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Search and Filter
• Integration_Points: Billing system, Database
• Code_Module_Mapped: -  (BX03US02) - Search and Filter
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Business rule#2
• Related_Bugs: N/A
• Related_Test_Cases: N/A

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Summary:

• Setup_Requirements: billing cycles with valid names, statuses (Active/Inactive), and Last Run Dates
• User_Roles_Permissions: Billing Manager
• Test_Data: Cycle names with mixed cases, partial keywords (e.g., “Monthly”), and valid status/date entries
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Enter cycle name in search box	Cycle names should display	Search results filter correctly	Case-insensitive search
2	Apply Status filter by Active/Inactive	Only active cycles displayed for active cycle filter aimilarly for inactive filter	Active/Inactive status filter	Correct filtering logic
3	Apply date range filter (Last Run Date)	Cycles within range shown	Last 30 days	Date validation working
4	Clear all filters	All cycles displayed again	Reset functionality	Filters reset properly
5	Test partial search match	"Monthly"	Shows all monthly cycles	Partial matching works

Verification Points:

• Primary_Verification: All Search and Filter metrics display correctly
• Secondary_Verifications: "No Data Available" validation massage for page without data
• Negative_Verification: partial search, copy paste scenario, edit and view after search, data after search without backend IDs, pagination should work after search for partial search

---

BX03US02_TC_003:-Verify New Bill Cycle Creation - HappyPath 

Title: Verify New Bill Cycle Creation - HappyPath 

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags: HappyPath, Consumer Services, Auth Services, Onbarding Services,
MOD-BX, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

• Customer_Segment: All
• Revenue_Impact: HIgh
• Business_Priority: Must-Have
• Customer_Journey: Billing
• Compliance_Required: No
• SLA_Related: Yes

Quality Metrics:

• Risk_Level: HIgh
• Complexity_Level: High
• Expected_Execution_Time: >1 minutes
• Reproducibility_Score: High
• Data_Sensitivity: High
• Failure_Impact: High

Coverage Tracking:

• Feature_Coverage: 100% of Bill Cycle Creation
• Integration_Points: Billing system, Consumer/Auth/Onb database,
• Code_Module_Mapped: (BX03US02) - Bill Cycle Creation
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Acceptance Criteria #2
• Related_Bugs: N/A
• Related_Test_Cases: Login, Utility Setup, Consumer Creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Onboarding data must be pre-configured with Categories, Subcategories, Consumer data, and linked Premises
  • At least 1 premises with attached consumers from multiple categories (e.g., Residential, Commercial)
• User_Roles_Permissions:
  • Billing Manager role
• Test_Data:
  • Cycle Name: “Monthly-West-2025”
  • Category: “Residential”
  • Billing Duration: 30 days
  • Premises: Central Plaza, North Heights
  • Consumers: At least 1400 Residential and 117 Commercial in selected premises
• Prior_Test_Cases: N/A

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Click "Create New Bill Cycle" button	Creation form opens	N/A	Form loads correctly
2	Enter unique cycle name	Name accepted	"Monthly-West-2025"	Validation passes
3	Select consumer category	Category selected based on set Category in onb	"Residential"	Dropdown works
4	Set billing duration	Duration accepted by selecting in calender	30 days	Valid range accepted
5	Navigate to Premise Selection	Premise list loads upon click on dropdown based on set Premise in onboarding	Available premises	Consumer counts update
6	Select premises	Consumer count updates according to selected premise attached to consumer	Central Plaza, North Heights	Real-time calculation
7	Review category breakdown	Percentages calculated for selected categories as per (Catehory of Consumers / Total Consumers in premise) × 100 = (1400 / 1517) × 100 ≈ 92.29% ≈ 92%	92% Residential, 8% Commercial	Accurate distribution
8	Save cycle configuration	Cycle created successfully	Complete configuration	Success message shown

Verification Points:

• Primary_Verification: Cycle should created with all data mention in steps, entry on list view with valid data (bill cycle name, consumer count, premise count, last rundate, days, run count, created by, status, action)
• Secondary_Verifications: Consumer data, premise and the category data should display accurately, tool tip,
• Negative_Verification: cycle created successfully but unable to display on list view needs to refresh, cycle created with incomplete data or data with backednd IDs on list view

---

BX03US02_TC_004 :- Verify Bill Cycle Name Uniqueness Validation 

Title: Verify Bill Cycle Name Uniqueness Validation 

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Cycle Creation Validation
• Test Type: Functional/Negative
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: Negative, Consumer Services
MOD-BX, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Bill Cycle Creation
• Integration_Points: Billing system, Consumer services, database
• Code_Module_Mapped: - (BX03US02) - Bill Cycle Creation
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Acceptance Criteria#2
• Related_Bugs: N/A
• Related_Test_Cases: Login, Utility Setup, Consumer Creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • At least one existing cycle created Eg:- name “Monthly-Central”
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Existing Cycle Name: “Monthly-Central”
  • New Unique Cycle Name: “Monthly-Central-New”
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Open cycle creation form	Form displays	N/A	Ready for input
2	Enter existing cycle name	Validation error shown	"Monthly-Central"	Duplicate name detected
3	Verify error message	Clear error displayed	"Cycle name already exists"	User-friendly message
4	Change to unique name	Validation passes	"Monthly-Central-New"	Name accepted
5	Complete cycle creation	Cycle created successfully	Valid configuration	No validation errors

Verification Points:

• Primary_Verification: Cycle name should be unique
• Secondary_Verifications: Consumer data, premise and the category data should display accurately, tool tip,
• Negative_Verification: Create duplicate cycle name, use upper case/ lower case letter for creating duplicate name of bill cycle check wether cycle create or gives validations, upon edit try to create the duplicate bill cycle name, Duplicate bill cycles (same name or same premise + frequency combination) must be prevented.

---

BX03US02_TC_005 :- Verify Billing Duration Validation Rules 

Title: Verify Billing Duration Validation Rules 

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Duration Validation
• Test Type: Functional/Boundary
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: Negative, Consumer Services, Calender

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Billing Duration
• Integration_Points: Billing system, Calender
• Code_Module_Mapped: - (BX03US02) - Billing Duration
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Business Rule #1
• Related_Bugs: N/A
• Related_Test_Cases: Login, Utility Setup, Consumer Creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Bill Cycle creation form must be accessible
  • System should have validation rules defined for billing duration (min: 1 day, max: 365 days)
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Valid: 1, 365
  • Invalid: 0, -5, "abc", 400
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Enter minimum duration	Value accepted	1 day	Boundary value valid
2	Enter zero duration	Validation error	0 days	Invalid value rejected
3	Enter negative duration	Validation error	-5 days	Negative value rejected
4	Enter non-numeric value	Validation error	"abc"	Non-numeric rejected
5	Enter maximum duration	Value accepted	365 days	Upper boundary valid
6	Enter exceed maximum	Validation error	400 days	Exceeds limit rejected

Verification Points:

• Primary_Verification: billing duration should according to mention critria in steps
• Secondary_Verifications: Input integer field, Must be a positive integer (min 1 day),
• Negative_Verification: input Character in integer field, check negative period, over exceed period, except filling period

---

BX03US02_TC_006 :- Verify Premise Selection with Area Filtering 

Title: Verify Premise Selection with Area Filtering 

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags: HappyPath, Auth Services, Onboarding Services, Consumer Services

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Premise Selection
• Integration_Points: Billing system, Database, Onboarding Services
• Code_Module_Mapped: - (BX03US02) - Premise Selection
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Acceptance Criteria#4
• Related_Bugs: N/A
• Related_Test_Cases: Login, Utility Setup

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Onboarding should include multiple premises mapped to different areas (e.g., "Downtown")
  • Each premise must be linked with consumers under different categories
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Premises: Central Plaza, Westside Mall
  • Area: Downtown
  • Consumer counts pre-mapped per premise
• Prior_Test_Cases:- N/A

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Navigate to Premise Selection	Premise list loads according to set premises in onboarding	All available premises	Full list displayed
2	Apply area filter	Filtered premises shown according to area set in onboarding	"Downtown" area	Correct filtering
3	Verify consumer counts	Accurate counts displayed as per premises	Per premise counts	Real-time calculation
4	Select multiple premises	Selection checkboxes work	Central Plaza, Westside Mall	Multi-selection works
5	Verify total consumer update	Sidebar count updates for consumer	Combined consumer count	Dynamic calculation
6	Clear area filter	All premises shown again	Reset filter	Filter reset works

Verification Points:

• Primary_Verification: Premises, consumer counts, and filters should behave according to configuration set in the Onboarding module, Selection of multiple premises should dynamically reflect total consumer count in the sidebar according to premises.
• Secondary_Verifications: Premise list should load completely on navigation without delay or missing data, Area filter dropdown should display all available onboarding areas, Multi-select checkbox should allow multiple premise selection and deselection, Sidebar should auto-update total consumer count accurately based on selected premises, Clearing the filter should restore the full premises list with accurate data.
• Negative_Verification: Try selecting premises before the list is fully loaded – UI should prevent actions or handle gracefully, Ensure that consumer count doesn’t update if backend data fails or count logic breaks – should throw error or fallback gracefully.

---

BX03US02_TC_007 :- Verify Consumer Eligibility Rules

Title: Verify Consumer Eligibility Rules

Created By: TSarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Consumer Eligibility
• Test Type: Functional/Business Rule
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Not-Automated

Enhanced Tags: HappyPath, Consumer Services, Database, Onboarding Services

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Consumer Eligibility
• Integration_Points: Billing system, Consumer Services, Database
• Code_Module_Mapped: (BX03US02) - Consumer Eligibility
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

• Primary_Stakeholder: Product
• Report_Categories: -
• Trend_Tracking: Yes
• Executive_Visibility: Yes
• Customer_Impact_Level: High

Requirements Traceability:

• Related_Requirements: - Acceptance Criteria#4
• Related_Bugs: N/A
• Related_Test_Cases: Login, Utility Setup, Consumer Creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Selected premises must have consumers with mixed statuses: Active, Temp Disconnect, Paused, Disconnected
  • Disconnected consumers should have their outstanding dues cleared (to be excluded)
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Consumer statuses:
    • Active (Green)
    • Temp Disconnect (Yellow)
    • Paused
    • Disconnected (with cleared dues)
  • At least 100 consumers across selected premises for valid percentage breakdown
• Prior_Test_Cases: N/A

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Navigate to Consumers tab	Consumer list loads according to selected premises	Selected premises consumers	Filtered list shown
2	Verify Active consumers included	Green status badges shown	Active consumers	Eligible consumers visible
3	Verify Temp Disconnect included	Yellow status badges shown	Temp Disconnect consumers	Eligible consumers visible
4	Verify Paused consumers excluded	Not visible in list	Paused consumers	Ineligible consumers hidden
5	Verify Disconnected excluded if outstanding clear	Not visible in list	Disconnected consumers	Ineligible consumers hidden
6	Check connection status breakdown	Correct percentages shown acooring to (total consumer by status / total consumer *100)	92% Active, 6% Paused, 2% Disconnected	Accurate calculation

Verification Points:

Primary_Verification: Consumer list should reflect consumers linked only to the selected premises, Only eligible consumer statuses (Active, Temp Disconnect) should be included in the displayed list, Connection status breakdown should accurately represent the status-wise percentage distribution of consumers.

Secondary_Verifications:

Active consumers should be clearly indicated with green status badges, Temporary Disconnected consumers should appear with yellow badges and still be included, Paused consumers should not be listed; filter logic should exclude them from the UI, Disconnected consumers should be excluded only if outstanding amounts are cleared; system should check backend flag before exclusion, Connection status breakdown formula should follow:
Status % = (No. of consumers in that status / Total selected consumers) × 100, Tooltip or breakdown section (if available) should reflect correct count and percentage per status.

Negative_Verification:

Without selecting premise the consumer connection should be 0%, check inactive consumer (temp. disconnection)

---

BX03US02_TC_008:- Verify Last Run Summary Display

Title: Verify Last Run Summary Display

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Summary Display
• Integration_Points: - Consumer Services, Billing System, Onboarding System, Auth Services, Database
• Code_Module_Mapped: (BX03US02) - Last Run Summary
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Acceptance Criatria #12,13,14
• Related_Bugs: N/A
• Related_Test_Cases: Login, Utility Setup, Consumer Creation, Meter Data Management Workflow (Note:- here we should attached workflow id instead of test cases)

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • At least one completed bill cycle (e.g., “Monthly-Central”) with historical billing data, initiator info, and run timestamps
  • Actual and estimated bill counts recorded for that cycle
• User_Roles_Permissions:
  • Billing Manager or any role with permission to view bill cycle details
• Test_Data:
  • Cycle Name: “Monthly-Central”
  • Run Date: May 15, 2025
  • Initiator: Arjun S.
  • Billing Summary: 1224 Processed, 1002 Actual, 206 Estimated
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Click on cycle name	Cycle details page opens	"Monthly-Central"	Detail view loads
2	Verify run date	Correct run date displayed	May 15, 2025	Last execution date
3	Verify initiator	User name shown according to the utility invite user	Arjun S.	Who initiated run
4	Verify days between runs	Correct calculation	14 mins	Time calculation
5	Verify actual vs estimated	Percentage shown as per generated bills (actual or est bill generated/ total generated bills * 100)	82% Actual	Ratio calculation
6	Check billing summary count	Correct counts display according to previous billing data	1224 Processed, 1002 Actual, 206 Estimated	Accurate totals

Verification Points:

Primary_Verification: Last run summary details (run date, initiator, actual vs estimated %, billing summary counts) should match the latest billing cycle execution data, The summary should reflect accurate, real-time data fetched from the billing engine logs or data repository.

Secondary_Verifications: Run Date should match the last successful billing execution date (e.g., May 15, 2025), "Days between runs" or "time since last run" should be correctly calculated (e.g., 14 mins if current run just happened), Actual vs Estimated percentage should be calculated using the formula:- Actual/Estimated % = (Actual or Estimated Bills Generated / Total Bills Generated) × 100, Billing summary count

Negative_Verification:

If no run has been performed yet, the detail view should show "No data available" or a placeholder – not blank or misleading values. check initior name after creation of bill cycle even if we inactive or delete that user according to the utility invite user, check the % count accuracy

---

BX03US02_TC_009 :- Verify Financial Summary Calculations

Title: Verify Financial Summary Calculations

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Financial Summary
• Test Type: Functional/Calculation
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Financial metrics
• Integration_Points: Consumer Services, Billing System, Onboarding System, Auth Services, Database
• Code_Module_Mapped: (BX03US02) - Financial Summary
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - Acceptance Criatria#13, 14
• Related_Bugs: N/A
• Related_Test_Cases: Utility Setup, Consumer Creation, Meter Data Management Workflow

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • At least one completed bill cycle with finalized bills, recorded payments, and applied late fees
  • Consumer payment and billing data must be available for the selected cycle
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Billed Amount: $243,500
  • Average Bill: $201.57
  • Outstanding Amount: $1,240
  • Late Fees: $560
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	View financial summary section	Section displays correctly	Cycle financial data	All metrics visible
2	Verify billed amount	Correct total shown	$243,500	Billed Amount = Sum of all individual consumer bills in the cycle
3	Verify average bill	Correct calculation	$201.57	Amount ÷ Bills
4	Verify outstanding amount	Current balance shown	$1,240	Unpaid balances (Outstanding = Sum of (Consumer's Billed Amount - Paid Amount) )
5	Verify late fees	Penalty amount shown in red color	$560	Fee calculation (Late Fees = Sum of all consumer-level late fee charges )
6	Cross-verify calculations	Math accuracy confirmed	Manual calculation	Calculations match

Verification Points:

Primary_Verification: Financial summary must accurately show billed amount, average bill, outstanding, and late fees based on cycle data.

Secondary_Verifications:

• Billed Amount = Sum of all consumer bills
• Average Bill = Billed Amount ÷ Number of bills
• Outstanding = Billed - Paid amount (per consumer)
• Late Fees = Sum of individual late charges
• All values should be correctly formatted in currency and visible.

Negative_Verification: Overpayment (credit note) should not show negative outstanding, amount match to the database data,

---

BX03US02_TC_010:- Verify Monthly Trend Chart Display

Title: Verify Monthly Trend Chart Display

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Trend Analysis
• Test Type: Functional/Visual
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Monthly Trend dashboard metrics
• Integration_Points: Consumer Services, Billing System, Onboarding System, Auth Services, Database
• Code_Module_Mapped: (BX03US02) - Monthly Trend
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: -AC#15
• Related_Bugs: N/A
• Related_Test_Cases: Utility Setup, Consumer Creation, Meter Data Management Workflow

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Historical revenue and consumption data for at least 5 months available in the system
  • Data must be filtered and aggregated correctly for chart display
• User_Roles_Permissions:
  • Billing Manager or user with access to dashboard/chart views
• Test_Data:
  • Revenue: Jan ~195K, Feb ~200K
  • Consumption: Jan ~195K, Feb ~200K
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	View monthly trend chart	Chart displays correctly	5-months system generated filtered revenue data	Visual representation
2	Verify data points for revenue in blue color	Correct values shown acoording to higest revenue on "y" axis	Jan: ~195K, Feb: ~200K	Historical accuracy
3	Verify data points for consumption in green color	Correct values shown acoording to higest consumption on "y" axis	Jan: ~195K, Feb: ~200K	Historical accuracy
4	Check chart interactivity	Hover tooltips work	Detailed values on hover	Interactive elements
5	Verify chart legend	Legend displays correctly	Revenue and Consumption	Clear labeling and tab running

Verification Points Summary:

• Primary_Verification:
  Monthly trend chart should accurately display revenue and consumption data for the last 5 months.
• Secondary_Verifications:
  • Revenue shown in blue, consumption in green, aligned to Y-axis values.
  • Data points must match backend monthly summaries.
  • Chart legend should clearly label both series.
  • Tooltip should show exact values on hover.
  • X-axis = months, Y-axis = values (K format or full number as per config).
• Negative_Verification:
  • Chart should handle empty/missing data without breaking.
  • Incorrect color codes or mismatched legends should be flagged.
  • Hover or tooltip failures should be logged as UI/UX bugs.

---

BX03US02_TC_011 :- Verify Run History Tracking

Title: Verify Run History Tracking

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Run History
• Test Type: Functional
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Run metrics
• Integration_Points: Consumer Services, Billing System, Onboarding System, Auth Services, Database
• Code_Module_Mapped: (BX03US02) - Run metrics
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: -AC#17, 18
• Related_Bugs: N/A
• Related_Test_Cases: Utility Setup, Consumer Creation, Meter Data Management Workflow

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Multiple historical run records present with accurate timestamps, initiators, and consumer counts
  • Export functionality enabled for the run history data
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Run initiators: Arjun S., System, Priya M.
  • Run intervals: 30, 32, 27, 31 days
  • Consumer counts: 1,222; 1,215; 1,198; 1,180
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Navigate to Run History tab	History table loads	Historical run data	Complete history shown
2	Verify chronological order	Latest runs first	Descending date order	Correct sorting
3	Verify initiator tracking	User names displayed according to the utility invite user	Arjun S., System, Priya M.	Audit trail present
4	Verify days between runs	Correct calculations	30, 32, 27, 31 days	Interval tracking
5	Verify consumer counts	Historical counts shown	1,222, 1,215, 1,198, 1,180	Account growth tracking
6	Check export functionality	Export button works	Full history data	Data export successful

Verification Points Summary:

• Primary_Verification:
  Run History tab should display complete historical data in descending order with accurate details for each cycle run.
• Secondary_Verifications:
  • Latest runs should appear first (sorted by date).
  • Initiator names.
  • Days between runs should be correctly calculated.
  • Consumer counts should reflect actual billed numbers per run.
  • Export button should download full run history in the correct format (e.g., CSV, Excel).
• Negative_Verification:
  • If history is empty, appropriate message ("No run history available") should appear.
  • Delete previous initior from invite user, never remove the name
  • Export errors (e.g., empty file, wrong format) should be logged.

---

BX03US02_TC_012:- Verify Consumer List Search and Filter

Title: Verify Consumer List Search and Filter

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Consumer Management
• Test Type: Functional
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Consumer metrics
• Integration_Points: Consumer Services, Billing System, Onboarding System, Auth Services, Database
• Code_Module_Mapped: (BX03US02) - Consumer Management
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

• Primary_Stakeholder: Product
• Report_Categories: -
• Trend_Tracking: Yes
• Executive_Visibility: Yes
• Customer_Impact_Level: High

Requirements Traceability:

• Related_Requirements: AC#18
• Related_Bugs: N/A
• Related_Test_Cases: Utility Setup, Consumer Creation, Meter Data Management Workflow

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Consumer data uploaded and linked to billing cycles with attributes: name, account number, status, and area
  • Statuses include Active, Temp Disconnected
  • Areas include "North Zone" and others
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Consumer Name: "Kavita Patil"
  • Account Number: "ACC-10045"
  • Status Filter: Active, Temp Disconnected
  • Area Filter: North Zone
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Navigate to Consumer List tab	Consumer table loads	All cycle consumers	Complete list shown
2	Search by consumer name, partial search	Filtered results shown	"Kavita Patil"	Name search works
3	Search by account number	Specific consumer found	"ACC-10045"	Account search works
4	Apply status filter	Filtered by status	"Active/Temp. Disconnected" status	Status filtering works
5	Apply area filter	Filtered by location	"North Zone"	Area filtering works
6	Combine multiple filters	Combined filtering works	Status + Area	Multiple criteria work

Verification Points (Summary):

Primary_Verification:

• Consumer list should update correctly based on search/filter actions as per selected premise.

Secondary_Verifications:

• Partial name and exact account number search should return correct results.
• Status and area filters should filter consumers accurately.
• Combined filters (status + area) should apply together using AND logic.

Negative_Verification:

• Invalid search/filter should show "No results found".
• Special characters or non-existent inputs should not break functionality.
• Clearing filters should restore default consumer list.

---

BX03US02_TC_013 :- Verify Export Functionality Across Views

Title: Verify Export Functionality Across Views

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Export/Reporting
• Test Type: Functional
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Export functionality
• Integration_Points: Consumer Services, Billing System, Onboarding System, Auth Services, Database
• Code_Module_Mapped: (BX03US02) - Export functionality
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: AC10
• Related_Bugs: N/A
• Related_Test_Cases: Utility Setup, Consumer Creation, Meter Data Management Workflow, Cycle creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Bill cycles, consumer data, and run history records present in the system
  • Export feature enabled and configured to generate .xlsx files
  • Filtering functionality working on lists prior to export
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Full cycle list data
  • Filtered consumer selection data
  • Complete run history data
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Export cycle list	Excel file downloads	All cycles data	Complete data export
2	Export consumer selection	Selected consumers exported	Filtered consumer list	Partial data export
3	Export run history	Historical data exported	Complete run history	Time-series data
4	Verify file format	Excel format correct	.xlsx file	Proper formatting
5	Verify data completeness	All columns included	Complete field set	No data loss
6	Verify filtered exports	Only filtered data exported	Applied filters respected	Correct scope

Verification Points (Summary):

Primary_Verification:

• Exported files should contain accurate data based on export type (cycle, consumer, history).

Secondary_Verifications:

• Files should download in proper .xlsx format.
• Exported data should include all relevant columns with no missing fields.
• Filtered exports must reflect only the data shown after applying filters.

Negative_Verification:

• Export should not proceed if no data is available show warning message.
• Exported data should not include backend Ids
• Incorrect filters should not export unrelated data.

---

BX03US02_TC_014 :- Verify System Behavior with Large Dataset

Title: Verify System Behavior with Large Dataset

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags: HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Load metrics
• Integration_Points: Billing system, Consumer database
• Code_Module_Mapped: (BX03US02) - Load metrics
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - N/A
• Related_Bugs: N/A
• Related_Test_Cases: Utility Setup, Consumer Creation, Meter Data Management Workflow, Cycle creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Bill cycle with 10,000+ consumers loaded in the system
  • Filters and export functionality optimized for large datasets
  • Pagination implemented on list views
• User_Roles_Permissions:
  • Billing Manager or user with access to large dataset views and export
• Test_Data:
  • Bill cycle linked to 10,000+ consumer records
  • Various filter combinations applicable on dataset
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Load cycle with 10,000+ consumers	Page loads within SLA	Large consumer dataset	Performance maintained
2	Apply filters on large dataset	Response < 1 second	Multiple filter criteria	Fast filtering
3	Export large dataset	Export completes successfully	10,000+ records	No timeout errors
4	Verify pagination	Page navigation works	Large result sets	Proper pagination

Verification Points (Summary):

Primary_Verification:

• System should handle large datasets (10,000+ consumers) efficiently without performance degradation.

Secondary_Verifications:

• Page load and filter response times should be within SLA (e.g., < 1 second).
• Export should complete successfully without timeouts or data loss.
• Pagination should work correctly across all result pages.

Negative_Verification:

• after fileter pagination
• list view data after search
  • check billed amount matching after generated bills, actual bill, estemeted bills

---

BX03US02_TC_015:- Verify Error Handling for External System Failures

Title: Verify Error Handling for External System Failures

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Error Handling
• Test Type: Integration/Negative
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Regression
• Automation Status: Not-Automated

Enhanced Tags:  HappyPath, Consumer Services, Onboarding Services, Meter Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Error Handling
• Integration_Points: Billing system, Consumer database
• Code_Module_Mapped: (BX03US02)- Error Handling
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: - N/A
• Related_Bugs: N/A
• Related_Test_Cases: Onb workflow, Cx workflow, Mx workflow, cycle creation

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • Meter data service (MX API) integrated and available for normal operation
  • System configured to handle API errors and retries
• User_Roles_Permissions:
  • Billing Manager or user role that triggers meter data fetch
• Test_Data:
  • Simulated API error responses (timeouts, 500 errors) from MX API
  • Cross-module API error scenarios
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Simulate meter data service error	Graceful error handling	Unavailable service	Proper error message for error of mx api
3	Check error notifications for error in cross mudule api	User informed of issues	Clear error messaging	User awareness
4	Verify retry mechanism	System attempts reconnection	Automatic recovery	Resilient behavior

Verification Points (Summary):

Primary_Verification:

• System should handle API/service failures gracefully with user-friendly error messages.

Secondary_Verifications:

• Errors in MX or cross-module APIs should trigger clear, actionable notifications.
• Retry mechanisms should automatically attempt reconnection or recovery.
• No crash or data corruption should occur during failures.

Negative_Verification:

• Meter data unable to featch
• unable to featch consumer data/meter data/onboarding data

---

BX03US02_TC_016 :- Verify Role-Based Access Control

Title: Verify Role-Based Access Control

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags:  HappyPath, Auth Services

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Access Control metrics
• Integration_Points: Billing system, Consumer database
• Code_Module_Mapped: (BX03US02) - Access Control metrics
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: N/A
• Related_Bugs: N/A
• Related_Test_Cases: Invited user, utility setup

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites Format:

• Setup_Requirements:
  • User accounts with defined roles: Billing Manager, Specialist, and unauthorized user
  • Role-based access control (RBAC) implemented for Bill Cycle module
• User_Roles_Permissions:
  • Billing Manager
• Test_Data:
  • Credentials for each user role
• Prior_Test_Cases: Invite User

Test Procedure:

Step #	Action	Expected Result	Test Data	Comments
1	Login as Billing Manager	Full access granted	Manager credentials	All features available
2	Verify cycle creation access	Create button visible	Manager role	Creation permitted
3	Verify edit/delete access for Billing Manager	Edit options available	Active cycles	Modification permitted
5	Verify restricted access	No create/edit buttons	Specialist role	Proper restrictions
6	Test unauthorized access	Access denied properly	Invalid permissions	Security enforced

Verification Points (Summary):

Primary_Verification:

• Access to features should align with the user's role and permission level.

Secondary_Verifications:

• Billing Manager should have full access (create, edit, delete).
• Specialist or lower roles should have restricted access (view-only or limited actions).

Negative_Verification:

• Unauthorized users should not be able to access or manipulate protected actions (e.g., create/edit)

---

BX03US02_TC_017 :- Verify system must provide consumption analysis with high and low usage identification

Title: Verify system must provide consumption analysis with high and low usage identification

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

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

Enhanced Tags:  HappyPath, Auth Services

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of consumption analysis
• Integration_Points: Billing system, Consumer database
• Code_Module_Mapped: (BX03US02) - consumption analysis
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: #AC5
• Related_Bugs: N/A
• Related_Test_Cases: Invited user, utility setup

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites:

• Setup_Requirements: Consumer billing history for last 3 billing cycles, including at least 3 high-usage and 3 low-usage consumers
• User_Roles_Permissions: Billing Manager access
• Test_Data: Usage in kWh for multiple consumers over 3 cycles
• Prior_Test_Cases: Login, Navigate to BX → Bill Cycle → View Consumer Data

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Navigate to Consumption Summery	Section loads with visual Count	Valid usage history	Ensure responsive UI
2	Verify High Usage Count in orange color indicates	Consumers with usage above defined threshold (e.g., >500 kWh) are shown in orange highlight or tooltip	24	Tooltip: “High Usage” label
3	Verify Low Usage Count in blue color indicates	Consumers with usage below threshold (e.g., <100 kWh) shown in green	18	Tooltip: “Low Usage” label
4	Verify Total Consumption value	Displays sum of all consumers’ water usage (e.g., 15,683 KL)	Actual consumer usage data	Compare with backend calculation
5	Verify Average Consumption value	Displays average (e.g., 12.8 KL) using formula: Total Consumption ÷ No. of Consumers	1225 consumers (for example)	Check rounded display

Verification Points:

• Primary_Verification: High/Low, total and average usage correctly detected and marked
• Secondary_Verifications: Tooltips, visual trends, color-coded flags
• Negative_Verification: Missing or incorrect flags, tooltip errors, broken links

---

BX03US02_TC_018 :-  Verify Active Cycle Deletion Prevention Rules

Title: Verify Active Cycle Deletion Prevention Rules

Created By: Sarvesh Created Date: 2025-05-27 Version: 1.0

Classification:

• Module/Feature: Cycle Deletion
• Test Type: Security
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Manual

Enhanced Tags:  HappyPath, Auth Services, Database

MOD-Bx, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High

Business Context:

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

Quality Metrics:

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

Coverage Tracking:

• Feature_Coverage: 100% of Cycle Deletion
• Integration_Points: Billing system, Consumer database
• Code_Module_Mapped: (BX03US02) - Cycle Deletion
• Requirement_Coverage: Complete
• Cross_Platform_Support: Web

Stakeholder Reporting:

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

Requirements Traceability:

• Related_Requirements: #AC19
• Related_Bugs: N/A
• Related_Test_Cases: Invited user, utility setup

Test Environment:

• Environment: Staging
• Browser/Version: Chrome 115+
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: Billing service, Consumer database, Metrics API
• Performance_Baseline: < 1 second load time
• Data_Requirements: Active billing cycles, consumer data

Prerequisites:

• Setup_Requirements: At least 2 active billing cycles present
• User_Roles_Permissions: Billing Manager
• Test_Data: 24 total cycles, 18 active
• Prior_Test_Cases: BX03US02_TC_003

Test Procedure:

Step	Action	Expected Result	Test Data	Comments
1	Navigate to Billing → Bill Cycle list	List view with all cycles appears	24 cycles data	Includes both active/inactive
2	Identify an Active Billing Cycle	Status = Active, Deactivate/Delete buttons visible	18 active cycles	Based on current state
3	Attempt to Delete Active Cycle	Error/Warning message: "Cannot delete active billing cycle. Please deactivate first."	Valid active cycle	Confirm message display
4	Click Deactivate, then Delete	Deactivate confirmation → Successfully deleted	Same active cycle	Two-step validation

Verification Points:

• Primary_Verification: Deletion restricted for active cycles
• Secondary_Verifications: Proper validation messages, UI control disabled/enabled accordingly
• Negative_Verification: Direct delete bypasses restriction, or no alert is shown

---

Test Execution Matrix

Browser/Device Combinations

Test Suite	Chrome 115+	Resolution	Device	Priority
Dashboard	✓	1920x1080	Desktop	P1
Cycle Creation	✓	1920x1080	Desktop	P1
Premise Selection	✓	1024x768	Tablet	P2
Monitoring	✓	375x667	Mobile	P3

---