Skip to main content

Meter Device Summary Dashboard (MX01US01)

#

Total Test cases :-16
Total Acceptance Criteria Coverage

  • AC13: ✓ System updates dashboard metrics at least once every 24 hours (Steps 1-12)
  • Coverage: 1/16 Acceptance Criteria = 6.25%


criteria:-

Test Scenario Analysis

A. Functional Test Scenarios

Core Functionality:

  • Dashboard KPI display with 8 meter statistic cards
  • Meter search functionality (Device # and Meter # options)
  • Service module access (Add Single Meter, Add Bulk Meters, View All Meters, Raise Service Orders)
  • Search results display with comprehensive meter details

Business Rules:

  • Total Meters calculation excluding disposed meters
  • Percentage calculations for all meter categories
  • Role-based service module access
  • Real-time data updates (24-hour cycle)

User Journeys:

  • Meter Manager: Monitor fleet health → Search specific meters → Access service modules
  • Meter Supervisor: Review inventory → Track faulty meters → Plan maintenance

Integration Points:

  • SMART360 Database connectivity
  • Meter Data Service API
  • User Authentication Service
  • External WX Module for service orders

Data Flow:

  • Database → API → Dashboard KPI cards
  • Search input → Query processing → Results display
  • Service module selection → Navigation → Form/List views

B. Non-Functional Test Scenarios

Performance: Dashboard load <1 second, Search response <500ms, Concurrent user support Security: Role-based access control, B2B utility data protection Compatibility: Chrome Latest browser support, Desktop 1920x1080 resolution Usability: Intuitive navigation, clear error messaging, consistent UI Reliability: 24-hour data refresh, system stability, error recovery

C. Edge Case & Error Scenarios

Boundary Conditions: Maximum meter counts, empty search results, invalid permissions Invalid Inputs: Malformed device numbers, SQL injection attempts, unauthorized access System Failures: Database connectivity issues, API timeouts, service unavailability Data Inconsistencies: Missing meter data, calculation errors, stale information

Complete Test Cases

Test Case 1: Dashboard KPI Cards Display Validation

# Test Case Metadata

  • Test Case ID: MX01US01_TC_001
  • Title: Verify Dashboard Displays All KPI Cards with Accurate Meter Statistics and Calculations
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

  • Module/Feature: Meter Services
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

# Enhanced Tags for 17 Reports Support Tags: MOD-Services, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium, Revenue-Impact-Medium, Inventory-View, Navigation, MX-Service, Database, happy-path

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 80% of inventory view functionality
  • Integration_Points: Navigation-Service, Meter-List-Service, Database
  • Code_Module_Mapped: ServiceModuleController, MeterListController, MX-Inventory-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Feature-Usage, Navigation-Flow, User-Journey
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service Module Router, Meter List Service, Database
  • Performance_Baseline: <2 seconds navigation time
  • Data_Requirements: Complete meter inventory data

# Prerequisites

  • Setup_Requirements: Dashboard accessible, user authenticated
  • User_Roles_Permissions: Meter Manager or Supervisor with View All permissions
  • Test_Data: Complete meter inventory (9,875 meters excluding disposed)
  • Prior_Test_Cases: TC_001 dashboard loaded successfully

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Locate "View All Meters" card

Card visible with list/grid icon


Third service card

2

Verify card description

Shows "Browse and search the complete meter inventory"


Inventory access description

3

Verify list icon display

List/grid icon visible on card


Visual indicator

4

Hover over "View All Meters" card

Card shows hover effect (shadow, color change)


Interactive feedback

5

Click on "View All Meters" card

Navigation initiated, loading indicator appears



6

Verify navigation success

Navigates to Meter List page


URL contains /meter-list

7

Verify page load time

Page loads within 2 seconds


Performance check

8

Verify meter list page load

Complete meter inventory displays in table/grid format


All meters except disposed

9

Verify meter list contains sample data

Shows meters matching dashboard totals (9,875 total)


Data consistency

10

Verify breadcrumb navigation

Shows "Dashboard > View All Meters"


Navigation context

# Verification Points

  • Primary_Verification: Service card accessible and navigates to complete meter inventory
  • Secondary_Verifications: Data consistency with dashboard totals, navigation time
  • Negative_Verification: No broken links, missing data, or unauthorized access

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Navigation success and inventory display validation]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Service card and inventory page screenshots]

# Acceptance Criteria Coverage

  • AC10: ✓ System provides access to the View All Meters functionality with proper description (Steps 1-2, 5-6)
  • Coverage: 1/16 Acceptance Criteria = 6.25%

Test Case 2: Device Number Search Functionality

# Test Case Metadata

  • Test Case ID: MX01US01_TC_002
  • Title: Verify Meter Search Functionality Using Device Number with Comprehensive Results Display
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Search, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Point, Search-Device, Results-Display, MX-Service, Database, happy-path

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

# Coverage Tracking

  • Feature_Coverage: 85% of search functionality
  • Integration_Points: Search-Service, Database-Query-Engine
  • Code_Module_Mapped: SearchController, MeterQueryService, ResultsFormatter, MX-Search-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Feature-Coverage, Search-Performance, User-Experience
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Search Service, Database with sample meter data
  • Performance_Baseline: <500ms search response time
  • Data_Requirements: Sample device data: DEV-5678, DEV-4231, DEV-7891

# Prerequisites

  • Setup_Requirements: Dashboard loaded successfully, search functionality accessible
  • User_Roles_Permissions: Authenticated user (Meter Manager or Supervisor)
  • Test_Data: Device IDs from sample data section
  • Prior_Test_Cases: TC_001 dashboard display must pass

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Locate Meter Search section on dashboard

Search section visible with radio buttons and input field


Below KPI cards

2

Verify default search option

"Device #" radio button selected by default



3

Verify search input field state

Input field enabled and placeholder text visible

Placeholder: "Enter device number..."


4

Click on "Device #" radio button if not selected

Radio button becomes selected, "Meter #" deselected



5

Enter valid device number in search field

Text appears correctly in input field

DEV-5678

No special characters issues

6

Click Search button

Search request initiated, loading indicator appears



7

Verify search response time

Results appear within 500ms


Use browser dev tools

8

Verify search results table headers

Headers: Device ID, Device Type, Meter Number, Installation Date, Location, Status


All 6 columns present

9

Verify specific device result data

DEV-5678, Smart Electric, 12542901, 2024-01-15, Block A, Zone 3, Active

Sample data values

All fields populated

10

Verify result formatting

Date format: YYYY-MM-DD, Status with appropriate color coding


Status: green for Active

11

Test second device search

Clear field, enter DEV-4231, click Search

DEV-4231


12

Verify second device results

DEV-4231, Smart Water, 10385672, 2023-11-02, Block C, Zone 1, Faulty

Sample data values

Status: red for Faulty

13

Test third device search

Clear field, enter DEV-7891, click Search

DEV-7891


14

Verify third device results

DEV-7891, Basic Gas, 20475632, 2022-08-17, Block B, Zone 2, Normal

Sample data values

Status: normal color

# Verification Points

  • Primary_Verification: Device search returns correct meter information with all required fields
  • Secondary_Verifications: Response time under 500ms, proper formatting, status color coding
  • Negative_Verification: No incorrect device data, missing fields, or performance issues

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Record search results and response times]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Search results screenshots]

# Acceptance Criteria Coverage

  • AC6: ✓ System allows searching by either Device # or Meter # (Steps 2-4)
  • AC7: ✓ System displays comprehensive search results including device ID, type, meter number, installation date, location, and status (Steps 8-14)
  • Coverage: 2/16 Acceptance Criteria = 12.5%



Test Case 3: Meter Number Search Functionality

# Test Case Metadata

  • Test Case ID: MX01US01_TC_003
  • Title: Verify Meter Search Functionality Using Meter Number with Accurate Results
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Search, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Search-Meter, Validation, MX-Service, Database, happy-path

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

# Coverage Tracking

  • Feature_Coverage: 85% of search functionality
  • Integration_Points: Search-Service, Database-Query-Engine
  • Code_Module_Mapped: SearchController, MeterQueryService, ResultsFormatter, MX-Search-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Feature-Coverage, Search-Performance, User-Experience
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Search Service, Database with sample meter data
  • Performance_Baseline: <500ms search response time
  • Data_Requirements: Sample meter numbers: 12542901, 10385672, 20475632

# Prerequisites

  • Setup_Requirements: Dashboard loaded successfully, search functionality accessible
  • User_Roles_Permissions: Authenticated user (Meter Manager or Supervisor)
  • Test_Data: Meter numbers from sample data section
  • Prior_Test_Cases: TC_001 dashboard must be accessible

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Click on "Meter #" radio button

Radio button selected, "Device #" deselected



2

Verify input field placeholder

Placeholder changes to "Enter meter number..."



3

Enter valid meter number

Text appears in search field

12542901


4

Click Search button

Search executes, results display


Response time <500ms

5

Verify meter search results

DEV-5678, Smart Electric, 12542901, 2024-01-15, Block A, Zone 3, Active

Sample data


6

Test second meter number

Clear and search for 10385672

10385672


7

Verify second result

DEV-4231, Smart Water, 10385672, 2023-11-02, Block C, Zone 1, Faulty

Sample data

Status: Faulty

8

Test third meter number

Clear and search for 20475632

20475632


9

Verify third result

DEV-7891, Basic Gas, 20475632, 2022-08-17, Block B, Zone 2, Normal

Sample data

Status: Normal

# Verification Points

  • Primary_Verification: Meter number search returns correct device information
  • Secondary_Verifications: All result fields populated, proper status display
  • Negative_Verification: No duplicate results or incorrect data mapping

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Record search results and response times]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Search results screenshots]

# Acceptance Criteria Coverage

  • AC6: ✓ System allows searching by either Device # or Meter # (Steps 1-2)
  • AC7: ✓ System displays comprehensive search results including device ID, type, meter number, installation date, location, and status (Steps 5, 7, 9)
  • Coverage: 2/16 Acceptance Criteria = 12.5%



Test Case 4: Add Single Meter Service Module Access

# Test Case Metadata

  • Test Case ID: MX01US01_TC_004
  • Title: Verify Add Single Meter Service Module Access and Navigation Functionality
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

  • Module/Feature: Meter Services
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

# Enhanced Tags for 17 Reports Support Tags: MOD-Services, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Service-Module, Navigation, MX-Service, Cross-service, happy-path

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

# Coverage Tracking

  • Feature_Coverage: 75% of service module functionality
  • Integration_Points: Navigation-Service, Form-Rendering-Service
  • Code_Module_Mapped: ServiceModuleController, NavigationHandler, MX-Service-Module
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Feature-Usage, Navigation-Flow, User-Journey
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service Module Router, Add Meter Form Service
  • Performance_Baseline: <2 seconds navigation time
  • Data_Requirements: N/A

# Prerequisites

  • Setup_Requirements: Dashboard accessible, user authenticated
  • User_Roles_Permissions: Meter Manager or Supervisor with Add Meter permissions
  • Test_Data: N/A
  • Prior_Test_Cases: TC_001 dashboard loaded successfully

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Scroll to Meter Services section

Services section visible with 4 service cards


Below search section

2

Locate "Add Single Meter" card

Card visible with plus icon and title


First service card

3

Verify card description text

Shows "Register a new meter device in the system"


Below card title

4

Verify card visual elements

Icon, title, description properly aligned and styled


UI consistency check

5

Hover over "Add Single Meter" card

Card shows hover effect (shadow, color change)


Interactive feedback

6

Click on "Add Single Meter" card

Navigation initiated, loading indicator appears



7

Verify navigation success

Successfully navigates to Add Meter form page


URL contains /add-meter

8

Verify form page load time

Page loads within 2 seconds


Performance check

9

Verify form page elements

Add meter form displays with required fields


Form validation

10

Verify breadcrumb navigation

Shows "Dashboard > Add Single Meter"


Navigation context

# Verification Points

  • Primary_Verification: Service card accessible and navigates to correct form
  • Secondary_Verifications: Visual design, hover effects, navigation time
  • Negative_Verification: No broken links, error pages, or unauthorized access

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Navigation success and timing results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Service card and form page screenshots]

# Acceptance Criteria Coverage

  • AC8: ✓ System provides access to the Add Single Meter functionality with proper description (Steps 2-3, 6-7)
  • Coverage: 1/16 Acceptance Criteria = 6.25%



Test Case 5: Add Bulk Meters Service Module Access

# Test Case Metadata

  • Test Case ID: MX01US01_TC_005
  • Title: Verify Add Bulk Meters Service Module Access and Data Upload Navigation
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

  • Module/Feature: Meter Services
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P2-High
  • Execution Phase: Regression
  • Automation Status: Manual

# Enhanced Tags for 17 Reports Support Tags: MOD-Services, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Bulk-Import, Navigation, MX-Service, Cross-service, happy-path

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

# Coverage Tracking

  • Feature_Coverage: 75% of bulk import functionality
  • Integration_Points: Navigation-Service, File-Upload-Service
  • Code_Module_Mapped: ServiceModuleController, BulkImportHandler, MX-Bulk-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Feature-Usage, Navigation-Flow, User-Journey
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service Module Router, Bulk Upload Service
  • Performance_Baseline: <2 seconds navigation time
  • Data_Requirements: N/A

# Prerequisites

  • Setup_Requirements: Dashboard accessible, user authenticated
  • User_Roles_Permissions: Meter Manager or Supervisor with Bulk Import permissions
  • Test_Data: N/A
  • Prior_Test_Cases: TC_001 dashboard loaded successfully

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Locate "Add Bulk Meters" card in services section

Card visible with upload icon and title


Second service card

2

Verify card description

Shows "Import multiple meters via spreadsheet"


Bulk import description

3

Verify upload icon display

Upload/document icon visible on card


Visual indicator

4

Hover over "Add Bulk Meters" card

Card shows hover effect (shadow, color change)


Interactive feedback

5

Click on "Add Bulk Meters" card

Navigation initiated, loading indicator appears



6

Verify navigation success

Navigates to data upload module


URL contains /bulk-upload

7

Verify upload page load time

Page loads within 2 seconds


Performance check

8

Verify upload page elements

File upload interface with instructions displayed


Upload functionality

9

Verify supported file formats

Shows accepted formats (.xlsx, .csv)


File type validation

10

Verify breadcrumb navigation

Shows "Dashboard > Add Bulk Meters"


Navigation context

# Verification Points

  • Primary_Verification: Service card accessible and navigates to bulk upload interface
  • Secondary_Verifications: Visual design, file format support, navigation time
  • Negative_Verification: No broken links, error pages, or unauthorized access


Test Case 6: View All Meters Service Module Access

# Test Case Metadata

  • Test Case ID: MX01US01_TC_006
  • Title: Verify View All Meters Service Module Access and Complete Inventory Navigation
  • Created By: QA Test Generator
  • Created Date: 2025-06-02


# Classification

  • Module/Feature: Meter Services
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

# Enhanced Tags for 17 Reports Support Tags: MOD-Services, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Service-Orders, WX-Integration, MX-Service, Cross-service, happy-path

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 85% of service order functionality
  • Integration_Points: WX-Module, Service-Order-Management, External-Systems
  • Code_Module_Mapped: ServiceModuleController, ServiceOrderController, MX-WX-Integration
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Feature-Usage, Integration-Testing, Business-Impact
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service Module Router, WX Module, Service Order Management
  • Performance_Baseline: <2 seconds navigation time
  • Data_Requirements: N/A

# Prerequisites

  • Setup_Requirements: Dashboard accessible, user authenticated, WX module available
  • User_Roles_Permissions: Meter Manager or Supervisor with Service Order permissions
  • Test_Data: N/A
  • Prior_Test_Cases: TC_001 dashboard loaded successfully

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

click on view icon card in services section

Card visible with upload icon and title


Second service card

2

Verify card description

Shows "Import multiple meters via spreadsheet"


Bulk import description

3

Verify upload icon display

Upload/document icon visible on card


Visual indicator

4

Hover over "Add Bulk Meters" card

Card shows hover effect (shadow, color change)


Interactive feedback

5

Click on "Add Bulk Meters" card

Navigation initiated, loading indicator appears



6

Verify navigation success

Navigates to data upload module


URL contains /bulk-upload

7

Verify upload page load time

Page loads within 2 seconds


Performance check

8

Verify upload page elements

File upload interface with instructions displayed


Upload functionality

9

Verify supported file formats

Shows accepted formats (.xlsx, .csv)


File type validation

10

Verify breadcrumb navigation

Shows "Dashboard > Add Bulk Meters"


Navigation context

Test Case 7: Raise Service Orders Module Access

# Test Case Metadata

  • Test Case ID: MX01US01_TC_007
  • Title: Verify Raise Service Orders Service Module Access and Service Type Selection
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

  • Module/Feature: Meter Services
  • Test Type: Functional
  • Test Level: Integration
  • Priority: P1-Critical
  • Execution Phase: Regression
  • Automation Status: Manual

# Enhanced Tags for 17 Reports Support Tags: MOD-Services, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Service-Orders, WX-Integration, MX-Service, Cross-service, happy-path

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 85% of service order functionality
  • Integration_Points: WX-Module, Service-Order-Management, External-Systems
  • Code_Module_Mapped: ServiceModuleController, ServiceOrderController, MX-WX-Integration
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Product
  • Report_Categories: Feature-Usage, Integration-Testing, Business-Impact
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Service Module Router, WX Module, Service Order Management
  • Performance_Baseline: <2 seconds navigation time
  • Data_Requirements: N/A

# Prerequisites

  • Setup_Requirements: Dashboard accessible, user authenticated, WX module available
  • User_Roles_Permissions: Meter Manager or Supervisor with Service Order permissions
  • Test_Data: N/A
  • Prior_Test_Cases: TC_001 dashboard loaded successfully

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Locate "Raise Service Orders" card

Card visible with service/wrench icon


Fourth service card

2

Verify card description

Shows service order creation description


Maintenance/inspection requests

3

Verify service icon display

Service/wrench icon visible on card


Visual indicator

4

Hover over "Raise Service Orders" card

Card shows hover effect (shadow, color change)


Interactive feedback

5

Click on "Raise Service Orders" card

Navigation initiated, loading indicator appears



6

Verify navigation success

Navigates to service order form


URL contains /service-orders

7

Verify form page load time

Page loads within 2 seconds


Performance check

8

Verify service type selection enabled

Service type dropdown/options available


Key differentiator from add meter

9

Verify form has meter selection

Can select meters for service orders


Integration with meter data

10

Verify service order types

Shows maintenance, inspection, replacement options


Business rule validation

11

Verify breadcrumb navigation

Shows "Dashboard > Raise Service Orders"


Navigation context

# Verification Points

  • Primary_Verification: Service card accessible and navigates to service order form with type selection
  • Secondary_Verifications: Service type options, meter selection integration, navigation time
  • Negative_Verification: No broken links, missing service types, or unauthorized access

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Navigation success and service form validation]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Service card and form page screenshots]

# Acceptance Criteria Coverage

  • AC11: ✓ System provides access to the Raise Service Orders functionality with proper description (Steps 1-2, 5-6)
  • Coverage: 1/16 Acceptance Criteria = 6.25%

Test Case 8: Dashboard Performance Under Normal Load

# Test Case Metadata

  • Test Case ID: MX01US01_TC_008
  • Title: Verify Dashboard Load Performance and Response Times Under Normal Operating Conditions
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Performance, P1-Critical, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-Medium, Load-Testing, Response-Time, MX-Service, Database, happy-path

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

# Coverage Tracking

  • Feature_Coverage: 90% of performance scenarios
  • Integration_Points: Database-Connection-Pool, Cache-Service, Load-Balancer
  • Code_Module_Mapped: DashboardController, PerformanceMonitor, MX-Performance-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Performance-Metrics, System-Health, SLA-Compliance
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Database, Cache Service, Load Balancer
  • Performance_Baseline: Dashboard <1 second, Search <500ms, API <500ms
  • Data_Requirements: Full dataset with 9,875 meters

# Prerequisites

  • Setup_Requirements: Performance monitoring tools enabled
  • User_Roles_Permissions: Valid user credentials
  • Test_Data: Complete meter dataset
  • Prior_Test_Cases: System baseline established

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Open browser dev tools performance tab

Performance monitoring active


Record network timing

2

Clear browser cache and cookies

Clean performance baseline


Ensure fresh load

3

Navigate to dashboard URL

Page load initiated


Start performance recording

4

Measure initial page load time

Complete load under 1 second

Target: <1000ms

DOM content + resources

5

Verify all KPI cards loaded

8 cards display with data within baseline


No loading indicators remain

6

Test search performance

Execute device search

DEV-5678

Measure response time

7

Verify search response time

Results display within 500ms

Target: <500ms

From click to results

8

Test multiple rapid searches

Execute 5 consecutive searches

Different device IDs

System stability

9

Verify consistent performance

All searches maintain <500ms response


No performance degradation

10

Measure memory usage

Monitor browser memory consumption


Memory leak detection

11

Test concurrent dashboard access

Open 3 browser tabs with dashboard


Multi-tab performance

12

Verify performance consistency

All tabs maintain <1 second load time


No resource conflicts

# Verification Points

  • Primary_Verification: Dashboard loads within 1 second, search responds within 500ms
  • Secondary_Verifications: Memory usage stable, multiple tabs perform consistently
  • Negative_Verification: No timeouts, memory leaks, or performance degradation

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Performance metrics and timing results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if performance issues found]
  • Screenshots_Logs: [Performance monitoring screenshots]

# Acceptance Criteria Coverage

  • AC13: ✓ System updates dashboard metrics at least once every 24 hours (Performance baseline validation)
  • Coverage: 1/16 Acceptance Criteria = 6.25%

Test Case 9: Invalid Search Input Error Handling

# Test Case Metadata

  • Test Case ID: MX01US01_TC_009
  • Title: Verify Error Handling and User Feedback for Invalid Search Inputs and Edge Cases
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Search, P2-High, Phase-Regression, Type-Negative, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Error-Handling, Edge-Cases, User-Experience, MX-Service, Database

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 95% of error scenarios
  • Integration_Points: Search-Validation-Service, Error-Handler
  • Code_Module_Mapped: SearchValidator, ErrorMessageService, MX-Validation-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Error-Handling, User-Experience, Edge-Case-Coverage
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Search Service, Validation Service, Error Handler
  • Performance_Baseline: Error messages display within 200ms
  • Data_Requirements: Invalid search terms, special characters, empty strings

# Prerequisites

  • Setup_Requirements: Dashboard loaded, search functionality accessible
  • User_Roles_Permissions: Any authenticated user
  • Test_Data: Invalid search terms, special characters, empty strings
  • Prior_Test_Cases: TC_001 dashboard must be functional

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Select "Device #" radio button

Radio button selected



2

Enter non-existent device number

Text appears in search field

INVALID-999


3

Click Search button

Search executes, error handling triggered



4

Verify "No results found" message

Clear message displays below search

"No results found for 'INVALID-999'"


5

Verify error message styling

Error message has appropriate styling (color, icon)


User-friendly display

6

Test empty search input

Clear field, leave empty, click Search

""


7

Verify empty input validation

Error message: "Please enter a search term"


Input validation

8

Test special characters in device search

Enter special characters

@#$%^&*()


9

Verify special character handling

Appropriate error or sanitized search


Security consideration

10

Test very long device number

Enter 50+ character string

DEVICE-123456789012345678901234567890123456789012345


11

Verify long input handling

System handles gracefully without errors


Input length validation

12

Switch to "Meter #" and test invalid meter

Select Meter #, enter invalid number

999999999


13

Verify meter number error handling

"No results found" message displays


Consistent error handling

14

Test SQL injection attempt

Enter SQL injection string

' OR 1=1 --


15

Verify security protection

Input sanitized, no security breach


Security validation

16

Test with leading/trailing spaces

Enter " DEV-5678 " with spaces

" DEV-5678 "


17

Verify space handling

System trims spaces and finds result


Input normalization

# Verification Points

  • Primary_Verification: All invalid inputs handled gracefully with appropriate error messages
  • Secondary_Verifications: Error message styling, response times, input sanitization
  • Negative_Verification: No system crashes, security vulnerabilities, or unclear error states

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Error messages and system behavior recorded]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if issues discovered]
  • Screenshots_Logs: [Error message screenshots]

# Acceptance Criteria Coverage

  • No direct AC coverage - This test case covers error handling scenarios not explicitly mentioned in acceptance criteria
  • Coverage: 0/16 Acceptance Criteria = 0%

Test Case 10: Role-Based Access Control Validation

# Test Case Metadata

  • Test Case ID: MX01US01_TC_010
  • Title: Verify Role-Based Access Control for Meter Manager and Supervisor Service Module Permissions
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

  • Module/Feature: Security and Access Control
  • Test Type: Security
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Security
  • Automation Status: Manual

# Enhanced Tags for 17 Reports Support Tags: MOD-Security, P1-Critical, Phase-Security, Type-Security, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, RBAC, Authentication, Authorization, MX-Service, Cross-service

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 100% of role-based scenarios
  • Integration_Points: Authentication-Service, Authorization-Service, RBAC-Engine
  • Code_Module_Mapped: AuthController, PermissionValidator, RoleManager, MX-Auth-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Security-Compliance, Access-Control, Risk-Management
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Authentication Service, RBAC Service, User Management System
  • Performance_Baseline: Authentication response <2 seconds
  • Data_Requirements: Valid Meter Manager and Meter Supervisor test accounts

# Prerequisites

  • Setup_Requirements: Test user accounts configured with appropriate roles
  • User_Roles_Permissions: Meter Manager and Meter Supervisor test credentials
  • Test_Data: manager@utility.com, supervisor@utility.com credentials
  • Prior_Test_Cases: User account setup completed

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Logout any current user session

User logged out successfully


Clear authentication state

2

Login with Meter Manager credentials

Successful authentication and dashboard access

manager@utility.com / Test123!


3

Navigate to dashboard

Dashboard loads with manager permissions



4

Verify Meter Manager service access

All 4 service modules visible and accessible

Add Single, Add Bulk, View All, Raise Orders


5

Click on "Add Single Meter"

Successfully navigates to add meter form


Permission validation

6

Return to dashboard and test "Add Bulk Meters"

Successfully navigates to bulk upload



7

Return to dashboard and test "View All Meters"

Successfully navigates to meter list



8

Return to dashboard and test "Raise Service Orders"

Successfully navigates to service order form



9

Logout Meter Manager

User logged out successfully



10

Login with Meter Supervisor credentials

Successful authentication

supervisor@utility.com / Test123!


11

Navigate to dashboard

Dashboard loads with supervisor permissions



12

Verify Meter Supervisor KPI access

Can view all dashboard KPI cards


Data visibility check

13

Test supervisor service module access

Verify appropriate service modules accessible

Per role permissions


14

Verify any restricted modules

Modules requiring higher permissions show as disabled/hidden


Permission enforcement

15

Test search functionality access

Both roles can use search functionality


Basic functionality access

16

Verify role-specific data filtering

Each role sees appropriate meter data scope


Data access control

# Verification Points

  • Primary_Verification: Each role has correct access to service modules per business rules
  • Secondary_Verifications: Data visibility, navigation permissions, feature availability
  • Negative_Verification: No unauthorized access, privilege escalation, or data leakage

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Role permissions and access results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if security issues found]
  • Screenshots_Logs: [Access control evidence]

# Acceptance Criteria Coverage

  • AC12: ✓ System restricts access to service modules based on user role permissions (Steps 4-8, 13-14)
  • Coverage: 1/16 Acceptance Criteria = 6.25%

Test Case 11: Data Refresh and Real-Time Updates

# Test Case Metadata

  • Test Case ID: MX01US01_TC_011
  • Title: Verify Dashboard Data Updates Within 24-Hour Refresh Cycle and Real-Time Synchronization
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-DataSync, P2-High, Phase-Integration, Type-Integration, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Real-Time, Data-Refresh, MX-Service, Database, Cross-service

# Business Context

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

# Quality Metrics

  • Risk_Level: Medium
  • Complexity_Level: High
  • Expected_Execution_Time: 25 hours (overnight test)
  • Reproducibility_Score: Medium
  • Data_Sensitivity: High
  • Failure_Impact: High

# Coverage Tracking

  • Feature_Coverage: 90% of data refresh scenarios
  • Integration_Points: Database-Sync-Service, Meter-Data-Pipeline, Cache-Manager
  • Code_Module_Mapped: DataRefreshService, SyncScheduler, CacheInvalidator, MX-Sync-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Data-Integrity, System-Integration, SLA-Compliance
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Database, Data Pipeline, Scheduler Service
  • Performance_Baseline: Data updates within 24 hours
  • Data_Requirements: Controlled test data with known update schedule

# Prerequisites

  • Setup_Requirements: Data refresh schedule configured, test meters in database
  • User_Roles_Permissions: Database access for test data manipulation
  • Test_Data: Baseline meter counts at test start
  • Prior_Test_Cases: TC_001 baseline dashboard working

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Record current dashboard timestamp

Note "Last updated" timestamp at dashboard bottom


Baseline recording

2

Record current KPI values

Document all 8 KPI card values

Total: 9,875, Active: 8,542, etc.


3

Insert new meter record in database

Add test meter to trigger data change

Test Device: TEST-001

Controlled data change

4

Wait for next refresh cycle

Monitor for data update within 24 hours


Automated monitoring

5

Refresh dashboard page

Load latest dashboard data


Manual page refresh

6

Verify timestamp updated

"Last updated" shows new timestamp


Within 24-hour window

7

Verify KPI values reflect changes

Total meters increased to 9,876

Expected: 9,876

Data consistency

8

Verify percentage recalculations

All percentages recalculated with new total


Automatic recalculation

9

Test real-time meter status change

Update test meter status to "Faulty"

TEST-001 → Faulty


10

Wait for next refresh cycle

Monitor for status change reflection



11

Verify faulty meter count updated

Faulty meters count increased by 1

Expected: 413

Status change tracking

12

Clean up test data

Remove test meter from database


Test cleanup

# Verification Points

  • Primary_Verification: Data updates within 24-hour cycle with accurate calculations
  • Secondary_Verifications: Timestamp accuracy, percentage recalculations, status changes
  • Negative_Verification: No stale data, calculation errors, or refresh failures

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Data refresh timing and accuracy results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if sync issues found]
  • Screenshots_Logs: [Before/after dashboard screenshots]

# Acceptance Criteria Coverage

  • AC13: ✓ System updates dashboard metrics at least once every 24 hours (Steps 1-12)
  • Coverage:/Feature:** Dashboard KPI Display
  • Test Type: Functional
  • Test Level: System
  • Priority: P1-Critical
  • Execution Phase: Smoke
  • Automation Status: Planned-for-Automation



Test Case 12: KPI Percentage Calculation Accuracy

# Test Case Metadata

  • Test Case ID: MX01US01_TC_012
  • Title: Verify Mathematical Accuracy of All KPI Percentage Calculations and Business Rule Compliance
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Calculations, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Mathematical-Validation, Business-Rules, MX-Service, Database, happy-path

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 100% of calculation scenarios
  • Integration_Points: Calculation-Engine, Database-Aggregation-Service
  • Code_Module_Mapped: KPICalculationEngine, MeterStatisticsService, MX-Calculation-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Business-Rules-Compliance, Mathematical-Accuracy, Data-Integrity
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Dashboard Service, Calculation Engine, Database
  • Performance_Baseline: Calculations complete within dashboard load time
  • Data_Requirements: Sample data: Total(9,875), Electric(4,128), Water(3,254), Gas(1,160), Normal(7,845), Faulty(412), RNT(285)

# Prerequisites

  • Setup_Requirements: Dashboard accessible with sample data loaded
  • User_Roles_Permissions: Any authenticated user
  • Test_Data: Sample data from user story
  • Prior_Test_Cases: TC_001 dashboard must display KPI cards

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to dashboard and load KPI data

All KPI cards display with values



2

Calculate Electric Meters percentage manually

(4,128 ÷ 9,875) × 100 = 41.8%

4,128 electric meters

Manual calculation

3

Verify Electric Meters percentage display

Dashboard shows 41.8% for Electric Meters

Expected: 41.8%

Precision to 1 decimal

4

Calculate Water Meters percentage manually

(3,254 ÷ 9,875) × 100 = 32.9%

3,254 water meters


5

Verify Water Meters percentage display

Dashboard shows 32.9% for Water Meters

Expected: 32.9%


6

Calculate Gas Meters percentage manually

(1,160 ÷ 9,875) × 100 = 11.7%

1,160 gas meters


7

Verify Gas Meters percentage display

Dashboard shows 11.7% for Gas Meters

Expected: 11.7%


8

Verify meter type total validation

Electric + Water + Gas = Total Meters

4,128 + 3,254 + 1,160 = 8,542 ≠ 9,875

Note: Missing 1,333 meters

9

Calculate Normal Condition percentage

(7,845 ÷ 9,875) × 100 = 79.5%

7,845 normal meters


10

Verify Normal Condition percentage display

Dashboard shows 79.5% for Normal Condition

Expected: 79.5%


11

Calculate Faulty Meters percentage

(412 ÷ 9,875) × 100 = 4.2%

412 faulty meters


12

Verify Faulty Meters percentage display

Dashboard shows 4.2% for Faulty Meters

Expected: 4.2%


13

Calculate RNT Meters percentage

(285 ÷ 9,875) × 100 = 2.9%

285 RNT meters


14

Verify RNT Meters percentage display

Dashboard shows 2.9% for RNT Meters

Expected: 2.9%


15

Calculate Active Meters percentage

(8,542 ÷ 9,875) × 100 = 86.5%

8,542 active meters


16

Verify Active Meters percentage (if displayed)

Dashboard shows 86.5% for Active Meters

Expected: 86.5%


17

Verify condition total validation

Normal + Faulty + RNT should account for categorized meters

7,845 + 412 + 285 = 8,542

Matches active meters

# Verification Points

  • Primary_Verification: All percentage calculations mathematically accurate to 1 decimal place
  • Secondary_Verifications: Totals validate, no rounding errors, consistent decimal precision
  • Negative_Verification: No calculation errors, missing percentages, or inconsistent totals

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Calculation accuracy and percentage validation results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if calculation errors found]
  • Screenshots_Logs: [KPI cards with percentage values]

# Acceptance Criteria Coverage

  • AC2: ✓ System categorizes meters by type (Electric, Water, Gas) with accurate counts and percentages (Steps 2-7)
  • AC3: ✓ System categorizes meters by condition status (Normal, Faulty, RNT) with accurate counts and percentages (Steps 9-14)
  • Coverage: 2/16 Acceptance Criteria = 12.5%

Test Case 13: Concurrent User Performance Testing

# Test Case Metadata

  • Test Case ID: MX01US01_TC_013
  • Title: Verify Dashboard Performance and Data Consistency with Multiple Concurrent Users
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Performance, P2-High, Phase-Performance, Type-Performance, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Concurrent-Users, Load-Testing, MX-Service, Database, Cross-service

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 85% of concurrent scenarios
  • Integration_Points: Load-Balancer, Database-Connection-Pool, Session-Manager
  • Code_Module_Mapped: ConcurrencyManager, LoadBalancer, MX-Scalability-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: Performance-Metrics, Scalability-Testing, System-Capacity
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Medium

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Load Balancer, Database Connection Pool, Session Management
  • Performance_Baseline: <1 second per user, consistent across 10+ concurrent users
  • Data_Requirements: Full meter dataset for realistic load testing

# Prerequisites

  • Setup_Requirements: Load testing tools configured, multiple user accounts available
  • User_Roles_Permissions: 10 valid user accounts with appropriate permissions
  • Test_Data: Complete meter dataset (9,875 meters)
  • Prior_Test_Cases: TC_001 and TC_008 baseline performance established

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Setup 10 concurrent user sessions

10 browser instances/tabs opened

Users 1-10

Load testing simulation

2

Simultaneously navigate all users to dashboard

All dashboards load within 1 second each


Performance consistency

3

Verify data consistency across sessions

All users see identical KPI values

Same data for all users


4

Execute concurrent searches

All 10 users search simultaneously

Mixed device/meter searches


5

Measure search response times

All searches complete within 500ms


Performance under load

6

Test concurrent service module access

Users access different service modules simultaneously


Resource contention testing

7

Monitor system resource usage

CPU, memory, database connections stable


System stability check

8

Verify no data corruption

All users continue to see accurate, consistent data


Data integrity validation

9

Test peak load scenario

Increase to 15 concurrent users

Users 1-15

Stress testing

10

Measure degradation under peak load

Performance degradation <10%


Acceptable performance loss

11

Verify system recovery

Return to 10 users, performance normalizes


Recovery validation

12

Clean up test sessions

Close all concurrent sessions


Resource cleanup

# Verification Points

  • Primary_Verification: System supports 10+ concurrent users with <10% performance degradation
  • Secondary_Verifications: Data consistency, resource stability, recovery capability
  • Negative_Verification: No system crashes, data corruption, or resource exhaustion

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Concurrent user performance and stability results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if performance issues found]
  • Screenshots_Logs: [Performance monitoring data]

# Acceptance Criteria Coverage

  • No direct AC coverage - This test case covers scalability requirements not explicitly mentioned in acceptance criteria
  • Coverage: 0/16 Acceptance Criteria = 0%

# Test Case Metadata

  • Test Case ID: MX01US01_TC_014
  • Title: Verify Search Results Display All Required Fields with Proper Formatting and Data Accuracy
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Search, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Results-Format, Data-Display, MX-Service, Database, happy-path

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 90% of results display scenarios
  • Integration_Points: Search-Results-Formatter, Database-Query-Service
  • Code_Module_Mapped: ResultsFormatter, SearchResultsController, MX-Display-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: User-Experience, Data-Presentation, Format-Validation
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Search Service, Results Formatter, Database
  • Performance_Baseline: Results display within 500ms
  • Data_Requirements: Sample device data: DEV-7891, DEV-4231, DEV-5678

# Prerequisites

  • Setup_Requirements: Dashboard loaded, search functionality working
  • User_Roles_Permissions: Any authenticated user
  • Test_Data: Sample device data from user story
  • Prior_Test_Cases: TC_002 and TC_003 basic search functionality working

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Execute device search

Search completes successfully

DEV-7891


2

Verify results table headers

Headers: Device ID, Device Type, Meter Number, Installation Date, Location, Status

All 6 required columns


3

Verify Device ID field

Shows "DEV-7891" in correct format

DEV-7891


4

Verify Device Type field

Shows "Basic Gas"

Basic Gas


5

Verify Meter Number field

Shows "20475632" as numeric value

20475632


6

Verify Installation Date field

Shows "2022-08-17" in YYYY-MM-DD format

2022-08-17

Date formatting

7

Verify Location field

Shows "Block B, Zone 2" with proper formatting

Block B, Zone 2

Location display

8

Verify Status field

Shows "Normal" with appropriate color coding

Normal

Status indicator

9

Test different status displays

Search for faulty meter to verify status colors

DEV-4231 (Faulty)

Color coding validation

10

Verify faulty meter status display

Status shows "Faulty" with red indicator

Faulty status


11

Test active meter status

Search for active meter

DEV-5678 (Active)


12

Verify active meter status display

Status shows "Active" with green indicator

Active status


13

Verify table responsiveness

Results table adjusts properly to browser width


UI responsiveness

14

Verify data alignment

All columns properly aligned (left, center, right as appropriate)


Visual consistency

15

Test column sorting

Click on column headers to verify sorting functionality


Interactive features

16

Verify results pagination

If multiple results, pagination controls work correctly


Large result sets

# Verification Points

  • Primary_Verification: All required fields display with proper formatting and accurate data
  • Secondary_Verifications: Color coding, alignment, responsiveness, sorting functionality
  • Negative_Verification: No missing fields, incorrect formatting, or broken layout

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Results format and field validation results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if formatting issues found]
  • Screenshots_Logs: [Search results display screenshots]

# Acceptance Criteria Coverage

  • AC7: ✓ System displays comprehensive search results including device ID, type, meter number, installation date, location, and status (Steps 2-8)
  • Coverage: 1/16 Acceptance Criteria = 6.25%

Test Case 15: API Response Validation for Dashboard Data

# Test Case Metadata

  • Test Case ID: MX01US01_TC_015
  • Title: Verify Dashboard API Endpoints Return Accurate Meter Data with Proper Response Structure
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-API, P1-Critical, Phase-API, Type-API, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Backend-Validation, Data-Integrity, MX-Service, Database, Cross-service

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 95% of API scenarios
  • Integration_Points: Dashboard-API, Database-Connection, Authentication-Service
  • Code_Module_Mapped: DashboardAPIController, MeterDataService, MX-API-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: Engineering
  • Report_Categories: API-Performance, Data-Integrity, Backend-Quality
  • Trend_Tracking: Yes
  • Executive_Visibility: Yes
  • Customer_Impact_Level: High

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Device/OS: Windows 10/11
  • Screen_Resolution: Desktop-1920x1080
  • Dependencies: Dashboard API, Database, Authentication Service
  • Performance_Baseline: API responses <500ms
  • Data_Requirements: Sample meter data matching user story

# Prerequisites

  • Setup_Requirements: API endpoints accessible, authentication configured
  • User_Roles_Permissions: Valid API credentials
  • Test_Data: Sample data: Total(9,875), Electric(4,128), Water(3,254), Gas(1,160), Normal(7,845), Faulty(412), RNT(285)
  • Prior_Test_Cases: Authentication and database connectivity working

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Execute API call to dashboard data endpoint

API responds with 200 status code

GET /api/meter-summary


2

Verify API response time

Response received within 500ms

Target: <500ms

Performance requirement

3

Verify response structure

JSON contains all required KPI fields


Schema validation

4

Verify total meters count

API returns totalMeters: 9875

Expected: 9875


5

Verify active meters count

API returns activeMeters: 8542

Expected: 8542


6

Verify electric meters count

API returns electricMeters: 4128

Expected: 4128


7

Verify water meters count

API returns waterMeters: 3254

Expected: 3254


8

Verify gas meters count

API returns gasMeters: 1160

Expected: 1160


9

Verify normal condition count

API returns normalMeters: 7845

Expected: 7845


10

Verify faulty meters count

API returns faultyMeters: 412

Expected: 412


11

Verify RNT meters count

API returns rntMeters: 285

Expected: 285


12

Verify pending service orders

API returns pendingServiceOrders: 156

Expected: 156


13

Verify pending installations

API returns pendingInstallations: 78

Expected: 78


14

Verify data types

All numeric fields return as integers/numbers


Type validation

15

Test API with invalid authentication

API returns 401 Unauthorized

Invalid token

Security validation

16

Test API response caching

Verify appropriate cache headers


Performance optimization

17

Test API error handling

Invalid parameters return proper error codes


Error handling

# Verification Points

  • Primary_Verification: API returns all required data fields matching dashboard display
  • Secondary_Verifications: Response time, data types, authentication security, error handling
  • Negative_Verification: No missing fields, incorrect data types, or security bypasses

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [API response validation and performance results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if API issues found]
  • Screenshots_Logs: [API response data and timing]

# Acceptance Criteria Coverage

  • AC1: ✓ System displays accurate total count of all registered meters (Step 4)
  • AC2: ✓ System categorizes meters by type (Electric, Water, Gas) with accurate counts (Steps 6-8)
  • AC3: ✓ System categorizes meters by condition status (Normal, Faulty, RNT) with accurate counts (Steps 9-11)
  • AC4: ✓ System displays count of pending service orders (Step 12)
  • AC5: ✓ System displays count of pending installations (Step 13)
  • Coverage: 5/16 Acceptance Criteria = 31.25%

Test Case 16: Dashboard Last Update Timestamp Validation

# Test Case Metadata

  • Test Case ID: MX01US01_TC_016
  • Title: Verify Dashboard Maintains Accurate Date-Time Stamp of Last Update
  • Created By: QA Test Generator
  • Created Date: 2025-06-02
  • Version: 1.0

# Classification

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

# Enhanced Tags for 17 Reports Support Tags: MOD-Timestamp, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-QA, Customer-All, Risk-Low, Business-Medium, Revenue-Impact-Low, Timestamp-Validation, Data-Freshness, MX-Service, Database, happy-path

# Business Context

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

# Quality Metrics

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

# Coverage Tracking

  • Feature_Coverage: 100% of timestamp scenarios
  • Integration_Points: Timestamp-Service, Data-Refresh-Service
  • Code_Module_Mapped: TimestampManager, DataRefreshService, MX-Timestamp-Service
  • Requirement_Coverage: Complete
  • Cross_Platform_Support: Web

# Stakeholder Reporting

  • Primary_Stakeholder: QA
  • Report_Categories: Data-Quality, System-Monitoring, User-Information
  • Trend_Tracking: Yes
  • Executive_Visibility: No
  • Customer_Impact_Level: Low

# Requirements Traceability

# Test Environment

  • Environment: Staging
  • Browser/Version: Chrome Latest
  • Dependencies: Timestamp Service, System Clock
  • Data_Requirements: Current system time for validation

# Prerequisites

  • Setup_Requirements: Dashboard accessible, system time synchronized
  • User_Roles_Permissions: Any authenticated user
  • Test_Data: Current system timestamp
  • Prior_Test_Cases: TC_001 dashboard loading successfully

# Test Procedure

Step #

Action

Expected Result

Test Data

Comments

1

Navigate to dashboard

Dashboard loads successfully



2

Locate last update timestamp

Timestamp visible at bottom of dashboard



3

Verify timestamp format

Format: "Last updated: YYYY-MM-DD HH:MM:SS" or similar


Standard format

4

Verify timestamp is recent

Timestamp is within last 24 hours


Data freshness check

5

Record current timestamp

Note the displayed timestamp value


Baseline recording

6

Refresh the page

Page reloads successfully



7

Verify timestamp remains same

Same timestamp displayed (no automatic update)


Consistency check

8

Wait for system refresh cycle

Monitor for timestamp change


If applicable

9

Verify timestamp updates after refresh

New timestamp reflects latest update


If refresh occurs

10

Check timestamp accuracy

Timestamp matches server time within acceptable margin


Accuracy validation

# Verification Points

  • Primary_Verification: Dashboard displays accurate last update timestamp
  • Secondary_Verifications: Format consistency, freshness within 24 hours
  • Negative_Verification: No missing timestamp, incorrect format, or stale data indicators

# Test Results (Template)

  • Status: [Pass/Fail/Blocked/Not-Tested]
  • Actual_Results: [Timestamp format and accuracy results]
  • Execution_Date: [Test execution date]
  • Executed_By: [Tester name]
  • Execution_Time: [Actual time taken]
  • Defects_Found: [Bug IDs if timestamp issues found]
  • Screenshots_Logs: [Dashboard timestamp screenshots]

# Acceptance Criteria Coverage

  • AC16: ✓ System maintains accurate date-time stamp of when the dashboard was last updated (Steps 2-10)
  • Coverage: 1/16 Acceptance Criteria = 6.25%

Complete Acceptance Criteria Coverage Summary

Coverage Analysis by Test Case

Test Case

Acceptance Criteria Covered

Coverage %

TC_001

AC1, AC2, AC3, AC4, AC5, AC14

37.5%

TC_002

AC6, AC7

12.5%

TC_003

AC6, AC7

12.5%

TC_004

AC8

6.25%

TC_005

AC9

6.25%

TC_006

AC10

6.25%

TC_007

AC11

6.25%

TC_008

AC13

6.25%

TC_009

None (Error handling)

0%

TC_010

AC12

6.25%

TC_011

AC13

6.25%

TC_012

AC2, AC3

12.5%

TC_013

None (Performance)

0%

TC_014

AC7

6.25%

TC_015

AC1, AC2, AC3, AC4, AC5

31.25%

TC_016

AC16

6.25%

Complete Acceptance Criteria Coverage

AC1: ✓ System displays accurate total count of all registered meters
Covered by: TC_001, TC_015

AC2: ✓ System categorizes meters by type (Electric, Water, Gas) with accurate counts and percentages
Covered by: TC_001, TC_012, TC_015

AC3: ✓ System categorizes meters by condition status (Normal, Faulty, RNT) with accurate counts and percentages
Covered by: TC_001, TC_012, TC_015

AC4: ✓ System displays count of pending service orders with priority indication
Covered by: TC_001, TC_015

AC5: ✓ System displays count of pending installations with today's schedule indication
*Covered by# Meter Device Summary Dashboard - Complete Test Cases User Story Reference: MX01US01 - Device Management Dashboard
Generated Date: June 02, 2025
Test Framework Version: BrowserStack Enhanced Template v2.0


Back to top