Calendar & Scheduling Management (ONB02US04)

User Story ID: ONB02US04
Feature: Calendar & Scheduling Management for B2B Utility SaaS
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

---

Overall Coverage Summary

Total Coverage: 100% (10/107/7 Acceptance Criteria Covered)

• Total Test Cases: 2085 (1875 Functional + 210 Non-Functional)
• Total Acceptance Criteria: 7 (Based on user story requirements)
• Coverage Percentage: (7/7) × 100 = 100%

---

1. Test Scenario Analysis

A. Functional Test Scenarios

Core Functionality Scenarios

1. Holiday Management
   • Add manual holidays with different types (Federal, Company, Observed)
   • Import standard holidays functionality
   • Edit existing holidays
   • Delete holidays
   • View holiday calendar with color-coded display
   • Navigate between months/years in calendar view
2. Working Days Configuration
   • Configure working hours for individual weekdays
   • Set weekend working status (working/non-working)
   • Use quick time presets for schedule configuration
   • Modify start and end times using sliders and direct input
   • Save and apply working hours changes
3. Calendar Visualization
   • Display holidays with proper color coding by type
   • Navigate calendar months (April 2025 example)
   • Select dates for holiday management
   • View existing holidays for selected dates

Business Rules Scenarios

1. Holiday Validation Rules
   • Prevent duplicate holidays on same date
   • Require holiday name and type for new entries
   • Validate holiday types (Federal/Company/Observed)
   • Ensure proper date selection and validation
2. Working Hours Validation
   • Validate time range between 00:00-23:59
   • Ensure start time is before end time
   • Apply timezone considerations (organization-level)
   • Validate working day status configuration
3. Role-Based Access Control
   • Utility Administrator: modify holidays/working hours for specific utility
   • System Admin: configure across multiple utilities
   • O&M Manager: read-only access for scheduling reference
   • Meter Reading Supervisor: working hours management access

User Journey Scenarios

1. Complete Holiday Setup Journey
   • Navigate to Calendar & Scheduling → Holiday Management
   • Select date on calendar → Add holiday → Configure type → Save
   • View and verify holiday appears correctly
2. Complete Working Hours Setup Journey
   • Access Working Days Schedule → Configure weekdays → Set hours → Apply quick presets → Save changes
3. Calendar Review and Management Journey
   • View calendar → Navigate months → Review existing holidays → Make modifications → Confirm changes

Integration Point Scenarios

1. Field Operations Integration
   • Working hours impact on field scheduling
   • Holiday considerations for meter reading operations
   • O&M scheduling coordination with calendar settings
2. Notification System Integration
   • Calendar change notifications to relevant departments
   • Automated updates for schedule modifications
   • System-wide holiday announcements
3. Multi-Utility Management
   • Cross-utility calendar configuration by System Admin
   • Utility-specific settings by Utility Administrator
   • Centralized vs. distributed calendar management

B. Non-Functional Test Scenarios

Performance Scenarios

1. Calendar Loading Performance
   • Initial calendar page load < 3 seconds
   • Month navigation response time < 1 second
   • Holiday data retrieval and display < 2 seconds
   • Working hours configuration save operation < 1 second
2. Concurrent User Scenarios
   • Multiple administrators modifying calendars simultaneously
   • Performance under typical utility organization load (50-100 concurrent users)
   • System response during peak configuration periods

Security Scenarios

1. Authentication & Authorization
   • Role-based access validation
   • Unauthorized access prevention
   • Session management for calendar modifications
   • Audit trail for all calendar changes
2. Data Protection
   • Calendar data encryption in transit and at rest
   • Secure storage of working hours configurations
   • Protection against calendar data manipulation
   • Compliance with utility industry security standards

Compatibility Scenarios

1. Browser Compatibility
   • Chrome (latest 2 versions) - primary browser
   • Cross-browser functionality validation
   • Desktop resolution optimization (1920x1080+)
2. System Compatibility
   • Windows 10/11 compatibility
   • Organization timezone integration
   • Multi-utility environment support

Usability Scenarios

1. User Experience
   • Intuitive calendar navigation
   • Clear holiday type distinction (color coding)
   • Easy working hours configuration with sliders
   • Quick time preset functionality
2. Error Handling
   • Clear validation messages for invalid inputs
   • Graceful handling of duplicate holiday scenarios
   • User-friendly error messages for time range issues

C. Edge Case & Error Scenarios

Boundary Conditions

1. Date Boundaries
   • Adding holidays at year boundaries (Dec 31, Jan 1)
   • Maximum holidays per year validation
   • Historical vs. future date handling
   • Leap year date management
2. Time Boundaries
   • Working hours at midnight boundaries (00:00, 23:59)
   • Time zone edge cases
   • Weekend working hour configurations
   • 24-hour schedule configurations

Invalid Input Scenarios

1. Malformed Data
   • Invalid date formats
   • Special characters in holiday names
   • Negative time values
   • Non-existent dates (Feb 30, etc.)
2. Security Testing
   • SQL injection attempts in holiday names
   • XSS prevention in text fields
   • Unauthorized API access attempts
   • Role escalation prevention

System Failure Scenarios

1. Network Issues
   • Calendar loading during network interruption
   • Save operations during connectivity loss
   • Recovery from partial data saves
   • Offline vs. online state management
2. Data Inconsistency
   • Conflicting calendar configurations
   • Corrupted holiday data recovery
   • Working hours configuration conflicts
   • Multi-user concurrent modification handling

---

2. Detailed Test Cases Aligned with Acceptance Criteria

Test CaseCoverage 1:Mapping:

1. ✅ AC1 - Support Three Holiday Types (Federal, Company, Observed)

   Test Case Metadata

   Test Case ID:AC1: ONB02US04_TC_001
   Title: Validate System Support for Three Holiday Types - Federal, Company, and Observed
   Created By: Arpita
   Created Date: June 08, 2025
   Version: 1.0

   Classification

   Module/Feature: Calendar & Scheduling Management
   Test Type: Functional/UI
   Test Level: System
   Priority: P1-Critical
   Execution Phase: Smoke
   Automation Status: Planned-for-Automation

   Enhanced Tags for 17 Reports Support

   Tags: MOD-Calendar, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Low, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Holiday-Management, Core-Feature, auth-Services, Onboarding-Services, cx-Services, API, Database, HappyPath, Cross-module

   Business Context

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

   Quality Metrics

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

   Coverage Tracking

   Feature_Coverage: 33% of Holiday Management (Holiday Types)
   Integration_Points: Calendar Display, Database Storage, Authentication Service
   Code_Module_Mapped: Onboarding
   Requirement_Coverage: Complete - AC1
   Cross_Platform_Support: Web

   Stakeholder Reporting

   Primary_Stakeholder: Product
   Report_Categories: Quality-Dashboard, Module-Coverage, Feature-Adoption
   Trend_Tracking: Yes
   Executive_Visibility: Yes
   Customer_Impact_Level: Medium

   Requirements Traceability

   Related_Requirements: AC1 - The system must support three holiday types (federal, company, observed) - 12 test cases
   

2. ✅ Related_Bugs:AC2: N/AUsers must be able to manually add holidays - 10 test cases
   
3. ✅ Related_Test_Cases:AC3: ONB02US04_TC_002,The ONB02US04_TC_003calendar must visually distinguish between holiday types - 8 test cases

   Test

4. ✅ Environment

   Environment:AC4: StagingWorking hours must be configurable for each day of the week - 15 test cases
   

5. ✅ Browser/Version:AC5: ChromeWeekend 118+working status must be definable - 8 test cases
   
6. ✅ Device/OS:AC6: WindowsThe 10/11system must provide quick time presets - 6 test cases
   
7. ✅ Screen_Resolution:AC7: Desktop-1920x1080Working hours must be savable and immediately applicable - 10 test cases
   

Test Scenario Summary

A. Functional Test Scenarios

Core Functionality

1. Dependencies:Holiday Management System
   • Import standard holidays
   • Manual holiday addition/modification/deletion
   • Holiday type classification (Federal, Company, Observed)
   • Calendar visualization with color coding
   • Monthly/annual view navigation
2. Working Days Configuration
   • Weekday working hours setup
   • Weekend working status configuration
   • Quick time presets utilization
   • Individual day configuration
   • Bulk schedule application
3. Calendar Visualization & Navigation
   • Monthly calendar display
   • Holiday highlighting and categorization
   • Date selection and management
   • Timeline navigation (previous/next month)

Business Rules Validation

• Role-based access control enforcement
• Holiday type validation and categorization
• Working hours time range validation (00:00-23:59)
• Duplicate holiday prevention
• Mandatory save operation validation
• Timezone handling from organization setup

User Journey Scenarios

• Utility Administrator: Complete holiday management workflow
• System Admin: Working hours configuration across utilities
• O&M Manager: Calendar viewing and operational planning
• Meter Reading Supervisor: Schedule validation and viewing

Integration Points

• Organization timezone integration
• User role and permission system integration
• Audit trail system integration
• Field operations scheduling system integration

B. Non-Functional Test Scenarios

Performance Testing

• Page load times (<3 seconds requirement)
• Calendar rendering performance
• Holiday data loading efficiency
• Working hours configuration response times
• Concurrent user handling

Security Testing

• Role-based access control validation
• Authentication and authorization
• Data protection and audit trails
• Session management
• Input validation and sanitization

Compatibility Testing

• Chrome Latest browser support
• Responsive design validation
• Cross-resolution testing
• Timezone handling accuracy

Usability Testing

• User interface intuitiveness
• Navigation flow efficiency
• Error message clarity
• Help guide accessibility

C. Edge Case & Error Scenarios

Boundary Conditions

• Maximum holidays per year testing
• Working hours edge cases (00:00, 23:59)
• Calendar date boundaries (month/year transitions)
• Long holiday names and descriptions

Invalid Inputs & Error Handling

• Invalid date formats
• Duplicate holiday dates
• Invalid working hour ranges
• Malformed timezone data
• Network connectivity issues

System Failures & Recovery

• Server unavailability scenarios
• Data corruption handling
• Session timeout management
• Concurrent modification conflicts

---

Detailed Test Cases - Organized by Acceptance Criteria

---

AC1: System Must Support Three Holiday Types (Federal, Company, Observed)

ONB02US04_TC_001: Validate Federal Holiday Type Support

Test Case Metadata

• Test Case ID: ONB02US04_TC_001
• Title: Validate Federal Holiday Type Support - Verify system supports Federal holiday type creation and management
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Holiday Management
• Test Type: Functional/UI
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Manual

Enhanced Tags for 17 Reports Support CalendarTags: Service,MOD-Calendar, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-Critical, Revenue-Impact-Medium, Integration-End-to-End, Holiday-Management, Federal-Holiday, Onboarding-Services, API, Database, AuthenticationHappyPath, ServiceCross-Module

Performance_Baseline:Business Context

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

Quality Metrics

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

Coverage Tracking

• Feature_Coverage: 25% of holiday management
• Integration_Points: User authentication, Calendar system
• Code_Module_Mapped: Holiday Management
• 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, Business Rule #3
• Related_Bugs: N/A
• Related_Test_Cases: ONB02US04_TC_002, ONB02US04_TC_003

Test Environment

• Environment: Staging
• Browser/Version: Chrome Latest
• Device/OS: Windows 11
• Screen_Resolution: Desktop-1920x1080
• Dependencies: User authentication system, Calendar database
• Performance_Baseline: < 3 seconds page load
  
• Data_Requirements: Valid userutility accountadministrator with Utility Administrator role

  Prerequisites

  credentials

Setup_Requirements:Prerequisites

• Setup_Requirements: Calendar & Scheduling module enabled
  
• User_Roles_Permissions: Utility Administrator access
  role
• Test_Data: LoginValid credentialslogin forcredentials, Utilitytest Administratorholiday (admin@testutility.com / TestPass123!)
  data
• Prior_Test_Cases: User authentication must pass

  successful

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Login as Utility Administrator	Successful login, dashboard displayed	admin@utility.com / password123
2	Navigate to Calendar & Scheduling module	Module loads successfully, displays Holiday Calendar section	N/A	Verify page loads <within 3 seconds
23	Click on Holiday Calendar section	CalendarHoliday viewcalendar displaysinterface with option to add holidaysdisplayed	N/A	Verify holiday management interface
3	Click on any date to add holiday	Holiday management panel appears on right with Holiday Type dropdown	Date: April 15, 2025	Verify date selection functionality
4	ClickSelect a future date on Holiday Type dropdowncalendar	DropdownDate displaysselection exactly three options: Federal Holiday, Company Holiday, Observed Holidayhighlighted	N/AApril 20, 2025	AC1 Verification: Three holiday types available
5	SelectClick "FederalAdd New Holiday" from dropdown	Federal Holiday option selected and highlightedbutton	Holiday Type:creation Federaldialog Holidayopens	Verify Federal type selection
6	Enter holiday name and save	HolidayField savedaccepts with Federal type, appears with blue color codinginput	Holiday Name: "TaxIndependence Day"	Verify Federal holiday creation
7	Add second holiday withSelect "CompanyFederal Holiday" type	CompanyDropdown Holidayselection saved with green color codingconfirmed	Holiday Name: "Company Picnic", Type: CompanyFederal Holiday	Verify Company type functionality
8	Add third holiday withClick "ObservedAdd Holiday" type	Observed Holiday saved with orange color codingbutton	Holiday Name:saved "Memorialsuccessfully, Dayappears Observed",in Type: Observed Holidaycalendar	Verify Observed type functionality
9	Verify all three holiday types display correctly	Calendar shows three holidays with distinct color coding for each type	N/A	AC1 Final Verification: All three types working

Verification Points

Primary_Verification:

• Primary_Verification: SystemHoliday providesappears exactlyon threeselected holidaydate typeswith (Federal,Federal Company,Holiday Observed)color coding
• Secondary_Verifications: Holiday appears in dropdownmonthly andview, processesaudit eachtrail type correctly
  Secondary_Verifications: Each holiday type has distinct visual representation, saves correctly to database
  created
• Negative_Verification: No additionalduplicate holidayholidays types available,created, no invalidsystem type combinations possible
  errors

---

TestONB02US04_TC_002: CaseValidate 2: AC2 - ManualCompany Holiday AdditionType CapabilitySupport

Test Case Metadata

Test Case ID:Metadata

• Test Case ID: ONB02US04_TC_002
  
• Title: Validate UsersCompany CanHoliday ManuallyType AddSupport Holidays- toVerify Calendarsystem System
  supports Company holiday type creation and management
• Created By: Arpita
  
• Created Date: June 08,10, 2025
  
• Version: 1.0

  Classification

Classification

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

  Manual

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-Calendar, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Product, Customer-All,Enterprise, Risk-Medium, Business-Critical, Revenue-Impact-High,Medium, Integration-Manual-Entry,End-to-End, Holiday-Creation,Management, auth-Services,Company-Holiday, Onboarding-Services, cx-Services, mx-Services, API, Database, HappyPath, Cross-moduleModule

Requirements Traceability

Related_Requirements: AC2 - Users must be able to manually add holidays

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	NavigateLogin toas HolidayUtility Calendar sectionAdministrator	CalendarSuccessful interfacelogin, loadsdashboard with add holiday capabilitydisplayed	N/Aadmin@utility.com / password123	Verify manual entry interface
2	SelectNavigate dateto AprilCalendar 20,& 2025Scheduling module	DateModule becomespage selected,loads holidaywithin entry3 form appearsseconds	Date: April 20, 2025	Verify date selection
3	EnterClick holidayon nameHoliday manually	TextCalendar input accepts holiday namesection	Holiday Name:calendar "Earthinterface Day Celebration"displayed	AC2 Verification: Manual input field working
4	Select holidaya typefuture fromdate dropdownon calendar	Date selection highlighted	May 15, 2025
5	Click "Add New Holiday" button	Holiday typecreation selectiondialog availableopens	Type:
6	Enter holiday name	Field accepts input	"Company Founding Day"
7	Select "Company Holiday" type	Dropdown selection confirmed	Company Holiday	Verify type selection
58	Click "Add Holiday" button	Holiday successfullysaved added to calendar	N/A	AC2 Verification: Manual addition complete
6	Verify holidaysuccessfully, appears in calendar

Verification Points

• Primary_Verification: Holiday visibleappears on selected date with properCompany formatting

  N/A

  VerifyHoliday successfulcolor manualcoding

• Secondary_Verifications: addition

  7

  Add another holiday manually

  System allows multiple manual additions

  Holiday: "Safety Training Day", Date: April 25, 2025

  Verify repeated manual additions

  8

  Check holidayHoliday appears in holidaysmonthly list

  Bothview, manuallyaudit addedtrail created

• Negative_Verification: No duplicate holidays visiblecreated, inno sidebarsystem list

  N/A

  AC2 Final Verification: Manual addition working

  Verification Points

  Primary_Verification: Users can successfully add holidays manually through the interface
  Secondary_Verifications: Manual input validation works, multiple holidays can be added
  Negative_Verification: Invalid manual inputs are rejected with clear error messages

  errors

---

TestONB02US04_TC_003: CaseValidate 3: AC3 - VisualObserved Holiday Type Distinction in CalendarSupport

Test Case Metadata

Test Case ID:Metadata

• Test Case ID: ONB02US04_TC_003
  
• Title: Validate Calendar Visually Distinguishes BetweenObserved Holiday TypesType withSupport Color- Coding
  Verify system supports Observed holiday type creation and management
• Created By: Arpita
  
• Created Date: June 08,10, 2025
  
• Version: 1.0

  Classification

Classification

• Module/Feature: Calendar & SchedulingHoliday Management 
  
• Test Type: UI/Visual
  Functional/UI
• Test Level: System
  
• Priority: P2-High
  P1-Critical
• Execution Phase: Regression
  Smoke
• Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-Calendar, P2-High,P1-Critical, Phase-Regression,Smoke, Type-UI,Functional, Platform-Web, Report-QA,Product, Customer-All,Enterprise, Risk-Low,Medium, Business-High,Critical, Revenue-Impact-Medium, Integration-Visual-Display,End-to-End, Color-Coding,Holiday-Management, cx-Observed-Holiday, Onboarding-Services, API, Database, HappyPath, Cross-moduleModule

Requirements Traceability

Related_Requirements: AC3 - The calendar must visually distinguish between holiday types

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	AddLogin Federalas HolidayUtility to calendarAdministrator	HolidaySuccessful appearslogin, withdashboard blue color codingdisplayed	Holiday:admin@utility.com "Independence/ Day", Type: Federalpassword123	AC3 Verification: Federal = Blue
2	Add Company HolidayNavigate to calendarCalendar & Scheduling module	HolidayModule appearspage withloads greenwithin color3 codingseconds	Holiday: "Company Anniversary", Type: Company	AC3 Verification: Company = Green
3	AddClick Observedon Holiday toCalendar calendarsection	Holiday appearscalendar withinterface orange color codingdisplayed	Holiday: "Christmas Observed", Type: Observed	AC3 Verification: Observed = Orange
4	ViewSelect a future date on calendar with all three types	AllDate holidaysselection visible with distinct colorshighlighted	N/AJune 20, 2025	Verify simultaneous visual distinction
5	CheckClick holiday"Add legend/keyNew Holiday" button	LegendHoliday showscreation colordialog coding explanationopens	N/A	AC3 Verification: Visual legend available
6	NavigateEnter toholiday different month and backname	ColorField codingaccepts persists across navigationinput	Navigate"Independence AprDay → May → AprObserved"	Verify color consistency
7	VerifySelect color"Observed accessibilityHoliday" compliancetype	ColorsDropdown meetselection accessibility contrast requirementsconfirmed	N/AObserved Holiday	Verify WCAG compliance
8	TestClick color"Add distinctionHoliday" for colorblind usersbutton	AlternativeHoliday visualsaved indicatorssuccessfully, availableappears ifin neededcalendar	N/A	AC3 Final Verification: Accessible distinction

Verification Points

Primary_Verification:

• Primary_Verification: CalendarHoliday usesappears distinct,on consistentselected date with Observed Holiday color coding
• Secondary_Verifications: forHoliday eachappears ofin themonthly threeview, holidayaudit types
  Secondary_Verifications:trail Colors are accessible, legend provided, consistency maintained
  created
• Negative_Verification: No colorduplicate confusion,holidays created, no missingsystem visual distinctions
  errors

---

TestONB02US04_TC_004: CaseVerify 4:All AC4Three -Holiday WorkingTypes Hours Configurable for Each Day of WeekAvailability

Test Case Metadata

Test Case ID:Metadata

• Test Case ID: ONB02US04_TC_004
  
• Title: ValidateVerify WorkingAll HoursThree ConfigurationHoliday forTypes EachAvailability Individual- DayConfirm ofdropdown thecontains Week
  Federal, Company, and Observed options
• Created By: Arpita
  
• Created Date: June 08,10, 2025
  
• Version: 1.0

  Classification

Classification

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

  Manual

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-WorkingHours,Calendar, P1-Critical, Phase-Regression, Type-Configuration,Functional, Platform-Web, Report-Engineering,QA, Customer-All, Risk-Medium,Low, Business-Critical, Revenue-Impact-High,Low, Integration-Working-Schedule,UI-Validation, auth-Services,Holiday-Types, Onboarding-Services, mx-Services, bx-Services, API, Database, HappyPath, Cross-moduleModule

Requirements Traceability

Related_Requirements: AC4 - Working hours must be configurable for each day of the week

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	NavigateAccess toHoliday WorkingCalendar Daysas ScheduleUtility sectionAdministrator	Working days configurationCalendar interface displaysloaded	N/A	Verify working hours interface
2	Click on Monday configuration	Monday working hours settings panel opens	N/A	AC4 Verification: Individual day access
3	Configure Monday working hours	Start: 8:00 AM, End: 4:00 PM saved successfully	Monday: 8:00 AM - 4:00 PM	Verify Monday-specific configuration
4	Click on Tuesday configuration	Tuesday working hours settings panel opens independently	N/A	AC4 Verification: Independent day configuration
5	Configure Tuesday with different hours	Start: 9:00 AM, End: 5:00 PM saved successfully	Tuesday: 9:00 AM - 5:00 PM	Verify different hours per day
6	Configure Wednesday	Start: 7:00 AM, End: 3:00 PM saved successfully	Wednesday: 7:00 AM - 3:00 PM	Verify third day configuration
7	Configure Thursday	Start: 10:00 AM, End: 6:00 PM saved successfully	Thursday: 10:00 AM - 6:00 PM	Verify fourth day configuration
8	Configure Friday	Start: 8:30 AM, End: 4:30 PM saved successfully	Friday: 8:30 AM - 4:30 PM	Verify fifth day configuration
9	Verify all weekdays show different hours	Main schedule view displays unique hours for each day	N/A	AC4 Final Verification: Individual day configuration working

Verification Points

Primary_Verification: System allows independent working hours configuration for each day of the week
Secondary_Verifications: Changes save correctly, display updates immediately, no cross-day interference
Negative_Verification: Changes to one day don't affect other days, no configuration loss

---

Test Case 5: AC5 - Weekend Working Status Configuration

Test Case Metadata

Test Case ID: ONB02US04_TC_005
Title: Validate Weekend Working Status Can Be Defined as Working or Non-Working
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Functional/Configuration
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: MOD-WorkingHours, P2-High, Phase-Regression, Type-Configuration, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Weekend-Schedule, mx-Services, bx-Services, API, Database, HappyPath, Cross-module

Requirements Traceability

Related_Requirements: AC5 - Weekend working status must be definable

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Navigate to Working Days Schedule section	Weekend section visible with Saturday and Sunday	N/A	Verify weekend configuration access
2	Check default Saturday status	Saturday shows current working status (default: working)	N/A	AC5 Verification: Saturday status definable
3	Toggle Saturday to "Non-working"	Saturday status changes to non-working, hours disabled	Status: Non-working	Verify Saturday status change
4	Check default Sunday status	Sunday shows current status (default: non-working)	N/A	AC5 Verification: Sunday status definable
5	Toggle Sunday to "Working Day"	Sunday becomes working day, hours configuration enabled	Status: Working Day	Verify Sunday status change
6	Configure Sunday working hours	Sunday hours set to 10:00 AM - 2:00 PM	Sunday: 10:00 AM - 2:00 PM	Verify weekend working hours
7	Save weekend configuration	Changes saved successfully	N/A	Verify weekend changes persist
8	Verify final weekend configuration	Saturday: Non-working, Sunday: Working (10:00 AM - 2:00 PM)	N/A	AC5 Final Verification: Weekend status definable

Verification Points

Primary_Verification: Both Saturday and Sunday working status can be independently defined as working or non-working
Secondary_Verifications: Working weekends allow hour configuration, non-working weekends disable hours
Negative_Verification: Status changes are exclusive (can't be both working and non-working)

---

Test Case 6: AC6 - Quick Time Presets Availability

Test Case Metadata

Test Case ID: ONB02US04_TC_006
Title: Validate System Provides Quick Time Presets for Working Hours Configuration
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support

Tags: MOD-WorkingHours, P2-High, Phase-Regression, Type-UI, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-Medium, Revenue-Impact-Medium, Integration-Quick-Presets, UI-Enhancement, cx-Services, mx-Services, HappyPath, Cross-module

Requirements Traceability

Related_Requirements: AC6 - The system must provide quick time presets

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Navigate to Working Days Schedule and select Monday	Working Hours Settings panel opens with presets visible	N/A	Verify quick presets interface
2	Verify quick time presets section	Section shows multiple preset options	Expected: 8AM-3PM, 8AM-4PM, 8AM-6PM, 7AM-3PM, 9AM-5PM	AC6 Verification: Quick presets available
3	Click "8AM - 4PM" preset	Working hours immediately change to 8:00 AM - 4:00 PM	Preset: 8AM-4PM	Verify preset functionality
4	Click "9AM - 5PM" preset	Working hours change to 9:00 AM - 5:00 PM	Preset: 9AM-5PM	Verify second preset
5	Click "7AM - 3PM" preset	Working hours change to 7:00 AM - 3:00 PM	Preset: 7AM-3PM	Verify third preset
6	Click "8AM - 6PM" preset	Working hours change to 8:00 AM - 6:00 PM	Preset: 8AM-6PM	Verify fourth preset
7	Verify sliders update with presets	Time sliders move to match preset selections	N/A	AC6 Verification: Presets update controls
8	Test preset on different day (Tuesday)	Quick presets work consistently across all days	N/A	AC6 Final Verification: Presets available for all days

Verification Points

Primary_Verification: System provides multiple quick time presets that immediately update working hours
Secondary_Verifications: Presets available for all days, sliders update correctly, common schedules covered
Negative_Verification: Presets don't conflict with manual entry, preset selection is reliable

---

Test Case 7: AC7 - Working Hours Save and Immediate Application

Test Case Metadata

Test Case ID: ONB02US04_TC_007
Title: Validate Working Hours Are Savable and Immediately Applicable in System
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Functional/Integration
Test Level: System
Priority: P1-Critical
Execution Phase: Smoke
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-WorkingHours, P1-Critical, Phase-Smoke, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Save-Apply, Real-Time-Update, auth-Services, mx-Services, bx-Services, ax-Services, API, Database, HappyPath, Cross-module

Requirements Traceability

Related_Requirements: AC7 - Working hours must be savable and immediately applicable

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Configure Monday working hours	Hours set to 8:00 AM - 4:00 PM in interface	Monday: 8:00 AM - 4:00 PM	Setup working hours
2	Click "SaveAdd Changes"New Holiday" button	SuccessHoliday messagecreation appears,dialog changes confirmedopens	N/A	AC7 Verification: Save functionality working
3	VerifyClick immediateon UIHoliday updateType dropdown	MainDropdown workingmenu days view immediately shows new hoursexpands	Display: Monday 8:00 AM - 4:00 PM	AC7 Verification: Immediate application
4	RefreshVerify browser"Federal pageHoliday" option	WorkingOption hoursvisible persistand after page refreshselectable	N/AFederal Holiday	Verify database persistence
5	NavigateVerify away"Company andHoliday" return to sectionoption	ConfigurationOption remainsvisible asand savedselectable	N/ACompany Holiday	Verify session persistence
6	CheckVerify API"Observed responseHoliday" for saved hoursoption	APIOption returnsvisible updatedand working hours configurationselectable	GETObserved /api/v1/calendar/working-hoursHoliday	AC7 Verification: API immediate update
7	ModifyVerify Tuesdayno hoursadditional and savetypes	TuesdayOnly changesthree alsotypes immediately appliedavailable	Tuesday: 9:00 AM - 5:00 PM	Verify consistent save behavior
8	Verify both days show updated hours	Both Monday and Tuesday display correct saved hours	N/A	AC7 Final Verification: Save and apply working

Verification

---

AC2: Points

Primary_Verification:Users WorkingMust hoursBe canAble beto savedManually andAdd areHolidays

ONB02US04_TC_005: immediatelyManual visibleHoliday andAddition applicable in the system
Secondary_Verifications: Changes persist across sessions, API updates in real-time, UI reflects changes instantly
Negative_Verification: No save delays, no data loss, no temporary inconsistencies

---

Test Case 8: Role-Based Access Control for Calendar ManagementFunctionality

Test Case Metadata

Test Case ID:Metadata

• Test ONB02US04_TC_008
  Case ID: ONB02US04_TC_005
• Title: ValidateManual Role-BasedHoliday AccessAddition ControlFunctionality for- CalendarVerify Managementusers Functions
  can manually add holidays through the interface
• Created By: Arpita
  
• Created Date: June 08,10, 2025
  
• Version: 1.0

  Classification

Classification

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

  Manual

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-Security,Calendar, P1-Critical, Phase-Security,Smoke, Type-Security,Functional, Platform-Web, Report-Engineering,Product, Customer-Enterprise,All, Risk-High,Medium, Business-Critical, Revenue-Impact-High,Medium, Integration-Authentication,Manual-Input, Security-Testing, Access-Control, auth-Services,Holiday-Addition, Onboarding-Services, rx-Services, API, Database, HappyPath, Cross-moduleModule

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Login as Utility Administrator	Access granted to calendar with utility-specific edit rightsmodule	utiladmin@testutility.admin@utility.com	Verify Utility Admin access
2	AddNavigate holidayto asHoliday UtilityCalendar Adminsection	HolidayInterface successfullydisplays addedcalendar for specific utilityview	Holiday: "Utility Safety Day"	Verify write permissions
3	LoginSelect asdate Systemon Admincalendar	AccessDate grantedbecomes with cross-utility configuration capabilitieshighlighted/selected	sysadmin@testutility.comJuly 25, 2025	Verify System Admin elevated access
4	ConfigureClick multi-utility"Add settingsNew Holiday" button	SuccessfullyHoliday accesscreation cross-utilityform configuration panelopens	N/A	Verify System Admin privileges
5	LoginEnter asholiday O&Mname Managermanually	AccessText grantedfield withaccepts read-only calendar viewinput	ommanager@testutility.com"Custom Holiday Test"	Verify limited access
6	AttemptSelect toholiday modify as O&M Managertype	ModificationType controlsselection disabled/unavailableconfirmed	N/ACompany Holiday	Verify read-only enforcement
7	LoginClick as"Add MeterHoliday" Reading Supervisorbutton	AccessHoliday grantedcreated withand workingvisible hourson view capabilitycalendar	supervisor@testutility.com	Verify role-specific access
8	Verify auditholiday trail captures all actionspersistence	AllHoliday userremains actionsafter loggedpage with proper attributionrefresh	N/A	Verify security logging

Verification Points

Primary_Verification: Each role has appropriate access levels with proper enforcement
Secondary_Verifications: Security audit trail complete, unauthorized actions blocked
Negative_Verification: No privilege escalation, no unauthorized modifications

---

TestONB02US04_TC_006: CasePrevent 9:Duplicate Holiday Import Standard Holidays FunctionalityAddition

Test Case Metadata

Test Case ID:Metadata

• Test ONB02US04_TC_009
  Case ID: ONB02US04_TC_006
• Title: Prevent Duplicate Holiday Addition - Verify system prevents duplicate holidays on same date
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Title:Classification Validate Import Standard Holidays Feature for Bulk

• Module/Feature: Holiday Management
  Created
• Test By:Type: Arpita
  CreatedFunctional/Negative
• Test Date:Level: JuneSystem
• Priority: 08,P1-Critical
• Execution 2025
  Version:Phase: 1.0

  Classification

  Regression
• Automation Status: Manual

Module/Feature: Calendar & Scheduling Management
Test Type: Functional/Integration
Test Level: System
Priority: P2-High
Execution Phase: Full
Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-Calendar, P2-High,P1-Critical, Phase-Full,Regression, Type-Integration,Negative, Platform-Web, Report-Product,QA, Customer-Enterprise,All, Risk-Medium,High, Business-High,Critical, Revenue-Impact-Medium,Low, Integration-Holiday-Import,Validation-Rules, Bulk-Operations,Duplicate-Prevention, Data-Import, cx-Services, mx-Onboarding-Services, API, Database, HappyPath, Cross-moduleModule

Business Context

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

Quality Metrics

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

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	NavigateLogin toas HolidayUtility Management sectionAdministrator	ImportSuccessful standard holidays option availablelogin	N/Aadmin@utility.com / password123	Verify import feature access
2	ClickNavigate "Importto StandardHoliday Holidays"Calendar	ImportCalendar dialoginterface opens with configuration optionsloaded	N/A	Verify import interface
3	SelectAdd year anda holiday typeson specific date	YearHoliday 2025created selected, Federal holidays checkedsuccessfully	Year:"Labor 2025,Day" Type:- Sept 1, 2025 - Federal	Configure import parameters
4	ExecuteTry importto processadd another holiday on same date	ImportSystem completesshows successfullyerror with progress indicationmessage	N/A"Memorial Day" - Sept 1, 2025 - Company	Verify bulk import functionality
5	Verify importederror holidaysmessage appearcontent	Standard holidays visible in calendar with correct types	Expected: New Year's Day, Independence Day, etc.	Verify import accuracy
6	Check import prevents duplicates	System handlesClear duplicate prevention appropriatelymessage displayed	N/A	Verify duplicate handling
7	Test selective import (Company holidays)	Company holidays import without affecting Federal	Type: Company holidays	Verify selective import
8	Verify performance with large import	Import process completes within acceptable timeframe	N/A	Verify import performance

Verification Points

Primary_Verification:

• Primary_Verification: StandardError message "Cannot add duplicate holidays canon bethe importedsame efficientlydate" withdisplayed
• Secondary_Verifications: properOriginal categorization
  Secondary_Verifications:holiday Importremains handles duplicates, selective import works, performance acceptable
  Negative_Verification: No data corruption during import,unchanged, no database corruption
• Negative_Verification: Second holiday not saved to system performance degradation

---

Test Case 10:

AC3: Calendar MonthMust NavigationVisually andDistinguish PerformanceBetween Holiday Types

ONB02US04_TC_007: Visual Holiday Type Distinction

Test Case Metadata

Test Case ID:Metadata

• Test ONB02US04_TC_010
  Case ID: ONB02US04_TC_007
• Title: Visual Holiday Type Distinction - Verify calendar uses different visual indicators for each holiday type
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Title:Classification Validate

• Module/Feature: Calendar MonthVisualization
• Test NavigationType: PerformanceFunctional/UI
• Test andLevel: VisualSystem
• Priority: Updates
  CreatedP1-Critical
• Execution By:Phase: Arpita
  CreatedSmoke
• Automation Date:Status: June 08, 2025
  Version: 1.0

  Classification

  Manual

Module/Feature: Calendar & Scheduling Management
Test Type: Performance/UI
Test Level: System
Priority: P2-High
Execution Phase: Performance
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-Calendar, P2-High,P1-Critical, Phase-Performance,Smoke, Type-Performance,UI, Platform-Web, Report-Engineering,Product, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Calendar-Navigation,Visual-Design, Performance-Testing,Holiday-Display, UI-Response, cx-CX-Services, mx-Services, API, Database, HappyPath, Cross-moduleModule

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Add Federal Holiday	Holiday created successfully	"Memorial Day" - Federal
2	Add Company Holiday	Holiday created successfully	"Founder's Day" - Company
3	Add Observed Holiday	Holiday created successfully	"New Year Observed" - Observed
4	View calendar with all holidays	Each holiday type has distinct visual appearance		Check colors/icons
5	Verify legend/color coding	Legend shows different colors for each type
6	Test calendar navigation	Visual distinction maintained across months

---

AC4: Working Hours Must Be Configurable for Each Day of the Week

ONB02US04_TC_008: Individual Day Working Hours Configuration

Test Case Metadata

• Test Case ID: ONB02US04_TC_008
• Title: Individual Day Working Hours Configuration - Verify each day of week can have unique working hours
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Working Days Configuration
• Test Type: Functional/UI
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Manual

Enhanced Tags for 17 Reports Support Tags: MOD-Calendar, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Workforce-Management, Working-Hours, Onboarding-Services, API, Database, HappyPath, Cross-Module

Step #	Action	Expected Result	Test Data	Comments
1	Login as System Admin	Successful authentication	sysadmin@utility.com / admin456
2	Navigate to HolidayWorking CalendarDays (initial load)Schedule	CalendarWorking loadsdays forinterface April 2025 within 3 secondsdisplayed	N/A	Measure
3	Configure initialMonday loadworking performancehours	Monday set to 8:00 AM - 4:00 PM	8:00 AM - 4:00 PM
4	Configure Tuesday working hours	Tuesday set to 9:00 AM - 5:00 PM	9:00 AM - 5:00 PM
5	Configure Wednesday working hours	Wednesday set to 7:00 AM - 3:00 PM	7:00 AM - 3:00 PM
6	Save configuration	All days show unique working hours
7	Verify individual day settings	Each day maintains its specific hours

---

ONB02US04_TC_009: All Seven Days Configuration Support

Test Case Metadata

• Test Case ID: ONB02US04_TC_009
• Title: All Seven Days Configuration Support - Verify all days of week (Mon-Sun) are configurable
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Working Days Configuration
• Test Type: Functional/Comprehensive
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Regression
• Automation Status: Manual

Enhanced Tags for 17 Reports Support Tags: MOD-Calendar, P1-Critical, Phase-Regression, Type-Functional, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Complete-Week, Seven-Days, Onboarding-Services, API, Database, HappyPath, Cross-Module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Access Working Days Schedule	All seven days visible (Mon-Sun)
2	Configure Monday	Working hours configurable	9:00 AM - 5:00 PM
3	Configure Tuesday	Working hours configurable	8:00 AM - 4:00 PM
4	Configure Wednesday	Working hours configurable	10:00 AM - 6:00 PM
5	Configure Thursday	Working hours configurable	7:00 AM - 3:00 PM
6	Configure Friday	Working hours configurable	9:00 AM - 5:00 PM
7	Configure Saturday	Working hours configurable	8:00 AM - 12:00 PM
8	Configure Sunday	Working hours configurable	Non-working
9	Save all configurations	All seven days saved successfully

---

AC5: Weekend Working Status Must Be Definable

ONB02US04_TC_010: Weekend Working Status Configuration

Test Case Metadata

• Test Case ID: ONB02US04_TC_010
• Title: Weekend Working Status Configuration - Verify weekend days can be set as working or non-working
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Working Days Configuration
• Test Type: Functional/UI
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Manual

Enhanced Tags for 17 Reports Support Tags: MOD-Calendar, P1-Critical, Phase-Smoke, Type-Functional, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-High, Integration-Weekend-Management, Weekend-Status, Onboarding-Services, API, Database, HappyPath, Cross-Module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Access Working Days Schedule as System Admin	Weekend section visible
2	View Saturday configuration	Saturday shows working status option
3	Set Saturday as working day	Saturday enabled with time configuration	9:00 AM - 1:00 PM
4	View Sunday configuration	Sunday shows working status option
5	Set Sunday as non-working	Sunday marked as "Non-working"	Non-working
6	Save weekend configuration	Weekend settings saved successfully
7	Verify weekend status display	Saturday shows working hours, Sunday shows non-working

---

AC6: System Must Provide Quick Time Presets

ONB02US04_TC_011: Quick Time Presets Functionality

Test Case Metadata

• Test Case ID: ONB02US04_TC_011
• Title: Quick Time Presets Functionality - Verify system provides predefined time presets for quick configuration
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Working Days Configuration
• Test Type: Functional/UI
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Manual

Enhanced Tags for 17 Reports Support Tags: MOD-Calendar, P2-High, Phase-Regression, Type-Functional, Platform-Web, Report-Product, Customer-All, Risk-Low, Business-High, Revenue-Impact-Medium, Integration-Time-Presets, Quick-Configuration, CX-Services, Database, HappyPath, Cross-Module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Access Working Days Schedule as System Admin	Interface loaded with preset options
2	Verify "9AM - 5PM" preset available	Preset button visible and clickable	9AM - 5PM
3	Verify "8AM - 4PM" preset available	Preset button visible and clickable	8AM - 4PM
4	Verify "8AM - 6PM" preset available	Preset button visible and clickable	8AM - 6PM
5	Verify "7AM - 3PM" preset available	Preset button visible and clickable	7AM - 3PM
6	Click "9AM - 5PM" preset	All working days updated to 9AM-5PM
7	Click "8AM - 4PM" preset	All working days updated to 8AM-4PM
8	Save configuration	Preset-based configuration saved successfully

---

AC7: Working Hours Must Be Savable and Immediately Applicable

ONB02US04_TC_012: Working Hours Save and Apply Functionality

Test Case Metadata

• Test Case ID: ONB02US04_TC_012
• Title: Working Hours Save and Apply Functionality - Verify working hours are savable and immediately effective
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Working Days Configuration
• Test Type: Functional/Integration
• Test Level: System
• Priority: P1-Critical
• Execution Phase: Smoke
• Automation Status: Manual

Enhanced Tags for 17 Reports Support Tags: MOD-Calendar, P1-Critical, Phase-Smoke, Type-Integration, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Save-Apply, Immediate-Effect, Onboarding-Services, API, Database, HappyPath, Cross-Module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Configure working hours for Monday	Hours set to 8:00 AM - 5:00 PM	8:00 AM - 5:00 PM
2	Click forward"Save navigationChanges" arrow (April → May)button	MaySuccess 2025message loads within 1 second with holidaysdisplayed	N/A	Test forward navigation performance
3	Verify immediate application	Working hours immediately reflected in display
4	Navigate backwardaway (Mayfrom →page	Configuration April)preserved
5	Return to Working Days Schedule	Saved configuration still visible
6	Test with different day configuration	Tuesday set to 9:00 AM - 6:00 PM	9:00 AM - 6:00 PM
7	Save and verify immediate effect	Changes applied instantly

---

Additional Critical Test Cases

ONB02US04_TC_013: Role-Based Access Control - Utility Administrator

Test Case Metadata

• Test Case ID: ONB02US04_TC_020
• Title: Verify users can navigate between different months in holiday calendar
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Calendar Visualization
• Test Type: Functional/UI
• Test Level: System
• Priority: P2-High
• Execution Phase: Regression
• Automation Status: Manual

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Access Holiday Calendar	April loads2025 withincalendar 1 second, maintains datadisplayed	N/A	Default view
2	Click next month arrow	May 2025 calendar loaded
3	Click previous month arrow twice	March 2025 calendar displayed
4	Verify holidays display correctly	Holidays shown with proper color coding
5	Test backwardrapid navigation	Smooth transitions, no errors		Performance check

---

Role-Based Access Control Test Cases

ONB02US04_TC_030: Utility Administrator Access Rights

Test Case Metadata

• Test Case ID: ONB02US04_TC_030
• Title: Verify Utility Administrator has appropriate access rights for calendar management
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support Tags: MOD-Security, P1-Critical, Phase-Smoke, Type-Security, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-User-Management, Role-Based-Access

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Login as Utility Administrator	Access granted to Calendar module	utility.admin@test.com
2	Verify holiday management access	Add/Edit/Delete buttons visible and functional
3	Verify working hours access	Configuration options available
4	Test save functionality	Changes can be saved successfully
5	Verify scope limitation	Can only modify specific utility settings

---

ONB02US04_TC_031: O&M Manager Read-Only Access

Test Case Metadata

• Test Case ID: ONB02US04_TC_031
• Title: Verify O&M Manager has read-only access to calendar information
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

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

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Login as O&M Manager	Access granted to view calendar	om.manager@test.com
2	Verify calendar viewing	Can view holidays and working hours
3	Test modification attempts	Add/Edit/Delete buttons not visible/disabled
4	Attempt direct URL access to edit	Access denied or redirected		Security test
5	Verify error handling	Appropriate access denied messages

---

Performance Test Cases

ONB02US04_TC_040: Page Load Performance

Test Case Metadata

• Test Case ID: ONB02US04_TC_040
• Title: Verify Calendar & Scheduling module loads within performance requirements
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

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

Enhanced Tags for 17 Reports Support Tags: MOD-Performance, P2-High, Phase-Performance, Type-Load, Platform-Web, Report-Engineering, Customer-All, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-System-Performance, Load-Time

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Clear browser cache	Cache cleared		Fresh load test
2	Navigate to Calendar module	Page loads within 3 seconds		Measure with dev tools
3	Switch between calendar months	Each transition <1 second		Navigation performance
4	RapidlyLoad navigateworking throughhours 6 monthsconfiguration	EachInterface transitionloads <within 12 second, no performance degradationseconds	Apr→May→Jun→Jul→Aug→Sep	TestComponent rapid navigationperformance
5	NavigateTest acrosswith yearmultiple boundaryholidays	December 2025 to January 2026 loads smoothly	Dec 2025 → Jan 2026	Test year boundary performance
6	Return to starting month	April 2025 loads correctly with all original data	Navigate back to April 2025	Verify data consistency
7	Monitor network requests during navigation	Efficient API calls, minimal data transfer	N/A	Test network optimization
8	Test with large holiday dataset	Navigation performancePerformance maintained with 50+ holidays	N/A	Test performance underData load test

Verification Points

Primary_Verification: Calendar month navigation maintains < 1 second response time consistently
Secondary_Verifications: Data loads correctly, year boundaries handled smoothly, network efficiency maintained
Negative_Verification: No performance degradation, no data loss during navigation, no memory leaks

---

API Test Case 11: Working Hours Time Boundary and ValidationCases

TestONB02US04_TC_050: CaseHoliday MetadataCreation API

Test Case ID:Metadata

• Test ONB02US04_TC_011
  Case ID: ONB02US04_TC_050
• Title: ValidateVerify Workingholiday Hourscreation TimeAPI Boundary Handlingfunctionality and Input Validation
  validation
• Created By: Arpita
  
• Created Date: June 08,10, 2025
  
• Version: 1.0

  Classification

Classification

• Module/Feature: CalendarAPI & Scheduling Management
  Integration
• Test Type: Functional/Validation
  API/Integration
• Test Level: System
  Integration
• Priority: P2-High
  P1-Critical
• Execution Phase: Full
  Regression
• Automation Status: Automated

  Manual

Enhanced Tags for 17 Reports Support

Tags: Tags: MOD-WorkingHours,API, P2-High,P1-Critical, Phase-Full,Regression, Type-Validation,API, Platform-Web, Report-QA,Engineering, Customer-All, Risk-Medium,High, Business-Medium,Critical, Revenue-Impact-Low,High, Integration-Time-Validation,API-Endpoints, Edge-Cases, Boundary-Testing, mx-Services, bx-Services, API, Database, Cross-moduleHoliday-CRUD

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Send POST request to create holiday	HTTP 201 Created response	{"name": "Test Holiday", "date": "2025-07-04", "type": "federal"}
2	Verify response structure	JSON contains holiday ID and details
3	Check database persistence	Holiday saved in database
4	Test duplicate prevention	HTTP 409 Conflict for duplicate date	Same date, different name
5	Test invalid data	HTTP 400 Bad Request for invalid input	Invalid date format

---

Integration Test Cases

ONB02US04_TC_060: Timezone Integration

Test Case Metadata

• Test Case ID: ONB02US04_TC_060
• Title: Verify calendar system correctly handles organization timezone settings
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

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

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Set organization timezone to EST	Timezone updated in org settings	Eastern Standard Time
2	Add holiday at specific time	Holiday time reflects EST	12:00 PM EST
3	Switch to PST organization	Time displays adjusted to PST	Pacific Standard Time
4	Verify working hours display	Hours shown in correct timezone
5	Test daylight saving transition	Times adjust automatically	During DST change period

---

Error Handling Test Cases

ONB02US04_TC_070: Network Connectivity Issues

Test Case Metadata

• Test Case ID: ONB02US04_TC_070
• Title: Verify system behavior during network connectivity issues
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Error Handling
• Test Type: Negative/Error
• Test Level: System
• Priority: P3-Medium
• Execution Phase: Regression
• Automation Status: Manual

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Load calendar module	Normal operation
2	Simulate network disconnection	Graceful error handling		Use dev tools
3	Attempt to save holiday	Appropriate error message displayed
4	Restore network connection	System recovers automatically
5	Retry save operation	Data saved successfully

---

Edge Case Test Cases

ONB02US04_TC_080: Boundary Working Hours

Test Case Metadata

• Test Case ID: ONB02US04_TC_080
• Title: Verify system handles boundary working hours (00:00 and 23:59)
• Created By: Arpita
• Created Date: June 10, 2025
• Version: 1.0

Classification

• Module/Feature: Working Hours
• Test Type: Boundary/Edge
• Test Level: System
• Priority: P3-Medium
• Execution Phase: Regression
• Automation Status: Manual

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Set working hours fromstart time to 00:00 to 23:59	Maximum 24-hour range acceptedAccepted and saved	Start:00:00 00:00, End: 23:59(midnight)	Test maximum boundary
2	AttemptSet working hours end time before start time	Validation error: "End time must be after start time"	Start: 17:00, End: 08:00	Test invalid time range
3	Set identical start and end times	Validation error: "Start and end times cannot be identical"	Start: 09:00, End: 09:00	Test zero duration
4	Input time beyond 24-hour format	Validation error: "Invalid time format"	Start: 25:00, End: 17:00	Test invalid time values
5	Test fractional time inputs	System accepts 30-minute increments correctly	Start: 09:30, End: 17:30	Test half-hour support
6	Verify timezone context display	Times display correctly in organization timezone (EST)	Org timezone: EST (-5 UTC)	Test timezone handling
7	Test boundary at midnight transition	System handles 23:30-23:59 appropriately	Start: 23:30, End:to 23:59	TestAccepted midnightand boundary
8saved	Validate23:59 time(11:59 format consistencyPM)	All displays use consistent 12-hour AM/PM format	N/A	Test format standardization

Verification Points

Primary_Verification: System correctly validates all time boundary conditions and invalid inputs
Secondary_Verifications: Error messages clear and helpful, timezone handling accurate
Negative_Verification: Invalid configurations rejected, no data corruption from boundary values

---

Test Case 12: Duplicate Holiday Prevention and Validation

Test Case Metadata

Test Case ID: ONB02US04_TC_012
Title: Validate System Prevents Duplicate Holiday Addition on Same Date
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Functional/Validation
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-Calendar, P2-High, Phase-Regression, Type-Validation, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Low, Integration-Data-Validation, Error-Handling, Business-Rules, cx-Services, mx-Services, API, Database, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Add initial holiday to calendar	Holiday "New Year" added successfully on April 11, 2025	Holiday: "New Year", Date: April 11, 2025, Type: Federal	Establish baseline holiday
2	Attempt to add second holiday on same date	Error message appears: "Holiday already exists on this date"	Holiday: "Spring Festival", Date: April 11, 2025, Type: Company	Test duplicate prevention
3	Verify original24-hour holidayoperation unchangeddisplay	OriginalShows "Newcorrectly Year"as holiday00:00 remains- intact23:59	N/A	Verify data integrity
4	Try different holiday type on same date	Still prevented with same error message	Holiday: "Special Day", Date: April 11, 2025, Type: Observed	Test prevention across types
5	Select different date for new holiday	Holiday addition succeeds on different date	Holiday: "Spring Festival", Date: April 12, 2025, Type: Company	Verify normal functionality
6	Test edit existing holiday instead	Edit functionality available for existing holiday	Edit "New Year" holiday details	Verify edit option provided
7	Verify error message user-friendly	Clear guidance provided in error message	Expected: "To modify, please edit existing holiday"	Test error message clarity
8	Test duplicate prevention in API	API returns 409 Conflict for duplicate attempts	POST /api/v1/calendar/holidays	Test API-level validation

Verification Points

Primary_Verification: System reliably prevents duplicate holidays on the same date with clear error messaging
Secondary_Verifications: Data integrity maintained, alternative actions suggested, API validation consistent
Negative_Verification: No duplicate creation possible, no data corruption, no workaround exploitation

---

Test Case 13: API Testing - Holiday Management Operations

Test Case Metadata

Test Case ID: ONB02US04_TC_013
Title: Validate Holiday Management API Endpoints for CRUD Operations
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: API/Integration
Test Level: Integration
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-API, P1-Critical, Phase-Regression, Type-API, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-API-Testing, Backend-Services, Critical-Path, auth-Services, mx-Services, API, Database, HappyPath, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	POST new holiday via API	201 Created with holiday details in response	{"name": "Earth Day", "date": "2025-04-22", "type": "company"}	Test holiday creation API
2	GET holiday by ID	200 OK with correct holiday data returned	GET /api/v1/calendar/holidays/{id}	Test holiday retrieval
3	GET holidays for specific month	200 OK with filtered holiday list	GET /api/v1/calendar/holidays?month=4&year=2025	Test holiday filtering
4	PUT update existing holiday	200 OK with updated holiday data	{"name": "Earth Day Celebration", "type": "federal"}	Test holiday update
5	DELETE holiday by ID	204 No Content, holiday removed	DELETE /api/v1/calendar/holidays/{id}	Test holiday deletion
6	Test API authentication	401 Unauthorized without valid token	Request without Authorization header	Test API security
7	Test invalid holiday data	400 Bad Request with validation errors	{"name": "", "date": "invalid-date"}	Test input validation
8	Test API response time	All operations complete within 500ms	N/A	Test performance requirement

Verification Points

Primary_Verification: All holiday CRUD operations work correctly via API with proper status codes
Secondary_Verifications: Authentication enforced, validation working, performance targets met
Negative_Verification: Invalid requests rejected, unauthorized access blocked, data integrity maintained

---

Test Case 14: API Testing - Working Hours Configuration

Test Case Metadata

Test Case ID: ONB02US04_TC_014
Title: Validate Working Hours Configuration API for Schedule Management
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: API/Integration
Test Level: Integration
Priority: P1-Critical
Execution Phase: Regression
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-API, P1-Critical, Phase-Regression, Type-API, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-API-Testing, Working-Hours-API, Critical-Path, auth-Services, mx-Services, bx-Services, API, Database, HappyPath, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	PUT working hours configuration	200 OK with updated configuration returned	{"monday": {"enabled": true, "start": "08:00", "end": "17:00"}}	Test working hours update
2	GET current working hours	200 OK with complete schedule configuration	GET /api/v1/calendar/working-hours	Test configuration retrieval
3	PUT weekend working configuration	200 OK with weekend schedule updated	{"saturday": {"enabled": false}, "sunday": {"enabled": true, "start": "10:00", "end": "14:00"}}	Test weekend configuration
4	Test invalid time format24:00	400 Bad RequestRejected with validation error	{"monday": {"start": "25:00", "end": "17:00"}}24:00	Test time validation
5	Test missingnegative requiredtime fieldsvalues	400 Bad RequestRejected with fieldvalidation validationerror	{"monday": {"enabled": true, "start": "08:00"}}-01:00	Test required field validation
6	Test bulk day configuration	200 OK with all days updated	Complete week configuration object	Test bulk update
7	Verify API response time	All operations under 500ms response time	N/A	Test performance requirement
8	Test API data persistence	GET returns saved configuration accurately	N/A	Test data persistence

Verification Points

Primary_Verification: Working hours API properly handles all configuration operations with validation
Secondary_Verifications: Bulk operations supported, performance requirements met, data persistence verified
Negative_Verification: Invalid inputs rejected, unauthorized changes blocked, no data loss

---

Test Case 15: Cross-Browser Compatibility Testing

Test Case Metadata

Test Case ID: ONB02US04_TC_015
Title: Validate Calendar & Scheduling Functionality Across Multiple Browsers
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Compatibility/UI
Test Level: System
Priority: P2-High
Execution Phase: Full
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-Compatibility, P2-High, Phase-Full, Type-Compatibility, Platform-Web, Report-QA, Customer-All, Risk-Medium, Business-Medium, Revenue-Impact-Medium, Integration-Cross-Browser, Compatibility-Testing, Multi-Platform, cx-Services, HappyPath, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Test holiday addition in Chrome 118+	Holiday added successfully, proper display	Holiday: "Test Holiday", Date: April 15, 2025	Test Chrome compatibility
2	Test same functionality in Firefox 110+	Identical behavior and visual presentation	Same holiday data	Test Firefox compatibility
3	Test in Safari 16+	All features work with consistent UI	Same holiday data	Test Safari compatibility
4	Test in Edge Latest	Feature parity maintained across browsers	Same holiday data	Test Edge compatibility
5	Test working hours configuration cross-browser	Sliders and controls work consistently	Monday: 9:00 AM - 5:00 PM	Test UI component consistency
6	Test calendar navigation in all browsers	Month navigation smooth in all environments	Navigate Apr → May → Jun	Test navigation consistency
7	Verify visual consistency	Color coding and layout identical across browsers	N/A	Test visual consistency
8	Test responsive behavior	Layout adapts properly in all browsers	Resize to 1366x768, 1024x768	Test responsive design

Verification Points

Primary_Verification: Calendar & Scheduling works identically across Chrome, Firefox, Safari, and Edge
Secondary_Verifications: Visual consistency maintained, responsive design works, performance similar
Negative_Verification: No browser-specific bugs, no functionality gaps, no layout issues

---

Test Case 16: Timezone Handling and Multi-Location Support

Test Case Metadata

Test Case ID: ONB02US04_TC_016
Title: Validate Timezone Handling for Multi-Location Utility Organizations
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Functional/Integration
Test Level: System
Priority: P1-Critical
Execution Phase: Integration
Automation Status: Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-Timezone, P1-Critical, Phase-Integration, Type-Integration, Platform-Web, Report-Engineering, Customer-Enterprise, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Timezone-Handling, Data-Consistency, Global-Operations, auth-Services, Onboarding-Services, mx-Services, bx-Services, API, Database, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Configure organization timezone to EST	System displays all times in EST format	Org Timezone: EST (-5 UTC)	Test baseline timezone setting
2	Add working hours in EST context	Hours saved correctly with timezone metadata	Monday: 9:00 AM - 5:00 PM EST	Test timezone-aware storage
3	Switch organization to PST	Existing times convert and display in PST	Same working hours now show as 6:00 AM - 2:00 PM PST	Test timezone conversion
4	Add holiday in PST context	Holiday saved with correct timezone reference	Holiday: "West Coast Day", April 20, 2025	Test timezone-aware holiday creation
5	Verify UTC storage in database	API returns times in UTC for consistency	GET /api/v1/calendar/working-hours	Test UTC backend storage
6	Test DST transition handling	System correctly handles daylight saving changes	Test during DST transition period	Test DST support
7	Multi-user timezone scenario	Users in different zones see data in their org timezone	EST user vs PST user viewing same data	Test multi-user consistency
8	Test timezone edge cases	System handles timezone boundaries correctly	Test at midnight UTC transitions	Test edge case handling

Verification Points

Primary_Verification: All time data correctly handles timezone conversions and displays appropriately
Secondary_Verifications: UTC storage maintained, DST transitions handled, multi-user consistency
Negative_Verification: No time drift, no data corruption during timezone changes

---

Test Case 17: Performance Testing Under Concurrent Load

Test Case Metadata

Test Case ID: ONB02US04_TC_017
Title: Validate Calendar System Performance Under Concurrent User Load
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Performance/Load
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-High, Integration-Multi-User, Concurrency-Testing, Load-Testing, auth-Services, mx-Services, bx-Services, ax-Services, API, Database, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Simulate 25 concurrent users	System maintains < 3 second page load times	25 simultaneous calendar access	Test initial load scaling
2	Scale to 50 concurrent users	Performance maintained, API responses < 500ms	50 users performing various operations	Test medium load
3	Reach 100 concurrent users	System stable, 95th percentile < 5 seconds	100 users with mixed operations	Test full target load
4	Test concurrent holiday additions	All additions processed without conflicts	20 users adding holidays simultaneously	Test write operation concurrency
5	Test concurrent working hours changes	Changes processed correctly with proper queuing	15 users modifying different days	Test configuration concurrency
6	Monitor database performance	Query response times remain under 200ms average	N/A	Test database scaling
7	Check error rate under load	Error rate stays below 1% threshold	N/A	Test system stability
8	Verify recovery after load test	System returns to normal performance levels	N/A	Test recovery capability

Verification Points

Primary_Verification: System maintains acceptable performance under 100 concurrent users
Secondary_Verifications: Error rates low, database performance stable, recovery successful
Negative_Verification: No system crashes, no data corruption, no memory leaks

---

Test Case 18: Security Penetration and Vulnerability Testing

Test Case Metadata

Test Case ID: ONB02US04_TC_018
Title: Validate Calendar Security Against Common Vulnerabilities and Attacks
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Security/Penetration
Test Level: System
Priority: P1-Critical
Execution Phase: Security
Automation Status: Semi-Automated

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, Integration-Security-Testing, Penetration-Testing, Vulnerability-Assessment, auth-Services, rx-Services, API, Database, Cross-module

Test Procedure

Step #	Attack Vector	Expected Result	Test Data	Comments
1	SQL injection in holiday name	Input sanitized, no database access	Holiday Name: "'; DROP TABLE holidays; --"	Test SQL injection prevention
2	XSS attempt in holiday description	Script tags escaped, no code execution	Description: "<script>alert('XSS')</script>"	Test XSS prevention
3	CSRF attack on working hours API	Request rejected without valid CSRF token	Forged PUT request without token	Test CSRF protection
4	Authentication bypass attempt	Unauthorized access blocked consistently	Direct API calls without authentication	Test authentication enforcement
5	Session hijacking simulation	Stolen sessions invalidated appropriately	Captured session token misuse	Test session security
6	Role escalation via parameter tampering	Privilege escalation attempts blocked	Modified role parameters in requests	Test authorization integrity
7	API enumeration and brute force	Rate limiting applied, attacks detected	Rapid API endpoint scanning	Test API security measures
8	Input validation boundary testing	All malformed inputs properly rejected	Various injection payloads	Test input sanitization

Verification Points

Primary_Verification: All common security vulnerabilities properly mitigated with appropriate responses
Secondary_Verifications: Security headers present, audit logging complete, encryption verified
Negative_Verification: No sensitive data exposure, no unauthorized access possible

---

Test Case 19: Data Export and Business Intelligence Integration

Test Case Metadata

Test Case ID: ONB02US04_TC_019
Title: Validate Calendar Data Export and Business Intelligence Reporting Features
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Functional/Integration
Test Level: System
Priority: P2-High
Execution Phase: Full
Automation Status: Manual

Enhanced Tags for 17 Reports Support

Tags: MOD-BI-Integration, P2-High, Phase-Full, Type-Integration, Platform-Web, Report-Product, Customer-Enterprise, Risk-Medium, Business-High, Revenue-Impact-Medium, Integration-Data-Export, BI-Reporting, Business-Intelligence, cx-Services, mx-Services, ax-Services, API, Database, HappyPath, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Export holiday data to CSV	Complete holiday list exported with all attributes	Export: All 2025 holidays, Format: CSV	Test CSV export functionality
2	Export working hours to Excel	Working hours configuration exported in structured format	Export: All working hours, Format: Excel	Test Excel export capability
3	Generate PDF calendar report	Visual calendar with holidays exported as PDF	Month: April 2025, Format: PDF	Test PDF generation
4	Filter export by holiday type	Export contains only Federal holidays	Filter: Federal holidays only	Test filtered export
5	Export audit trail data	Complete activity log exported for compliance	Date range: March 1-31, 2025	Test audit export
6	Test large dataset export performance	Export of full year data completes efficiently	All 2025 calendar data	Test export scalability
7	Verify export data accuracy	Exported data matches system display exactly	Cross-reference with UI display	Test data integrity
8	Test API-based data export	Programmatic export via API endpoints works	GET /api/v1/calendar/export	Test API export capability

Verification Points

Primary_Verification: Calendar data exports successfully in multiple formats with complete accuracy
Secondary_Verifications: Performance acceptable for large datasets, filtering works correctly
Negative_Verification: No data truncation, no format corruption, no sensitive data exposure

---

Test Case 20: System Integration with Field Operations

Test Case Metadata

Test Case ID: ONB02US04_TC_020
Title: Validate Calendar Integration with Field Operations and Mobile Systems
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0

Classification

Module/Feature: Calendar & Scheduling Management
Test Type: Integration/End-to-End
Test Level: System
Priority: P1-Critical
Execution Phase: Integration
Automation Status: Semi-Automated

Enhanced Tags for 17 Reports Support

Tags: MOD-Integration, P1-Critical, Phase-Integration, Type-E2E, Platform-Web, Report-Engineering, Customer-All, Risk-High, Business-Critical, Revenue-Impact-High, Integration-Field-Operations, End-to-End-Testing, Mobile-Integration, mx-Services, bx-Services, ax-Services, API, Database, HappyPath, Cross-module

Test Procedure

Step #	Action	Expected Result	Test Data	Comments
1	Add holiday in calendar system	Holiday information propagates to field operations	Holiday: "Maintenance Day", April 28, 2025	Test holiday propagation
2	Verify field schedules respect holiday	No work orders automatically scheduled on holiday	N/A	Test scheduling integration
3	Modify working hours in calendar	Field operations system updates schedule availability	Change Monday: 7:00 AM - 3:00 PM	Test working hours sync
4	Check mobile app receives updates	Mobile field application shows updated calendar data	N/A	Test mobile integration
5	Test emergency override capability	Critical work can override holiday restrictions	Emergency work order on holiday	Test business rule flexibility
6	Verify meter reading schedule adjustment	Meter reading routes adjust to new working hours	N/A	Test utility-specific integration
7	Test real-time notification system	Calendar changes trigger field operation notifications	N/A	Test notification integration
8	Validate bidirectional data sync	Field operation changes reflect in calendar system	Schedule conflict from field system	Test two-way integration

Verification Points

Primary_Verification: Calendar changes properly integrate with field operations and mobile systems in real-time
Secondary_Verifications: Bidirectional sync works, notifications sent correctly, emergency overrides function
Negative_Verification: No scheduling conflicts, no data inconsistencies, no sync failures

---

3. Test Suite Organization

Smoke Test Suite (20 minutes)

Criteria: P1 prioritypriority, coveringbasic allfunctionality 7validation Acceptance Criteria
Test Cases:

• ONB02US04_TC_001 (AC1:Add ThreeFederal Holiday Types Support)Holiday)
• ONB02US04_TC_002ONB02US04_TC_010 (AC2: Manual Holiday Addition)
• ONB02US04_TC_004 (AC4:Configure Working Hours Per Day Configuration)Hours)
• ONB02US04_TC_007ONB02US04_TC_030 (AC7:Utility WorkingAdmin HoursAccess)
• ONB02US04_TC_040 Save(Page &Load Apply)Performance)

Execution: Every build deployment
Expected Duration: 20 minutes
Pass Criteria: 100% pass rate required for production deployment

Regression Test Suite (60 minutes)

Criteria: P1-P2 priority, covers all Acceptance Criteria plus core functionalityfeatures and integration
Test Cases:

•  All Smokefunctional Testtest Cases
• ONB02US04_TC_003 (AC3: Visual Holiday Type Distinction)
• ONB02US04_TC_005 (AC5: Weekend Working Status)
• ONB02US04_TC_006 (AC6: Quick Time Presets)
• ONB02US04_TC_008 (Role-Based Access Control)
• ONB02US04_TC_012 (Duplicate Holiday Prevention)
• ONB02US04_TC_013 (Holidaycases, API Testing)
• ONB02US04_TC_014tests, (Workingrole-based Hoursaccess APIcontrol Testing)

Execution: Before each release
Expected Duration: 60 minutes
Pass Criteria: 95% pass rate required

Full Test Suite (4 hours)

Criteria: All test cases including cross-platformedge cases and integrationerror scenarios
Test Cases:

• All Regression Test Cases
• ONB02US04_TC_009 (Holiday Import)
• ONB02US04_TC_010 (Calendar Navigation Performance)
• ONB02US04_TC_011 (Time Boundary Validation)
• ONB02US04_TC_015 (Cross-Browser Compatibility)
• ONB02US04_TC_016 (Timezone Handling)
• ONB02US04_TC_017 (Performance Under Load)
• ONB02US04_TC_019 (Data Export & BI)
• ONB02US04_TC_020 (Field Operations Integration)

Execution: Weekly or major release cycles
Expected Duration: 4 hours
Pass Criteria: 90% pass rate required

Security & Compliance Suite (2 hours)

Criteria: Security, audit, and compliance focused testing
Test Cases:

• ONB02US04_TC_008 (Role-Based Access Control)
• ONB02US04_TC_018 (Security Penetration Testing)
• Additional audit trail validation tests
• Compliance reporting tests

Execution: Monthly or security-focused releases
Expected Duration: 2 hours
Pass Criteria: 100% pass rate required for security tests

---

4.Cross-Platform Acceptance Criteria TraceabilityTesting Matrix

Test Case	Chrome Latest	Responsive Design	Performance
Holiday Management	✓	✓	<3s load
Working Hours Config	✓	✓	<3s load
Calendar Navigation	✓	✓	<1s transition
Role-based Access	✓	✓	<2s verification

---

API Test Collection (Critical Operations)

Holiday Management APIs

• POST /api/holidays - Create holiday
• GET /api/holidays - Retrieve holidays
• PUT /api/holidays/{id} - Update holiday
• DELETE /api/holidays/{id} - Delete holiday

Working Hours APIs

• POST /api/working-hours - Configure hours
• GET /api/working-hours - Retrieve configuration
• PUT /api/working-hours - Update hours

Validation APIs

• POST /api/validate/holiday-date - Check duplicates
• POST /api/validate/working-hours - Validate time ranges

---

Performance Benchmarks

Acceptance CriteriaOperation	TestExpected Case(s)Performance	VerificationCritical Method	Priority	StatusThreshold
AC1: Page Support three holiday types (federal, company, observed)Load	TC_001<3 seconds	Dropdown5 validation, Type functionality testing	P1-Critical	✓ Coveredseconds
AC2: Calendar Users must be able to manually add holidaysNavigation	TC_002<1 second	Manual2 entry process validation	P1-Critical	✓ Coveredseconds
AC3: Holiday Calendar must visually distinguish between holiday typesSave	TC_003<2 seconds	Color3 coding verification, Visual distinction testing	P2-High	✓ Coveredseconds
AC4:  Working hoursHours configurable for each day of weekSave	TC_004<2 seconds	Individual3 day configuration testing	P1-Critical	✓ Coveredseconds
AC5: API Weekend working status must be definableResponse	TC_005<500ms	Weekend1 status configuration testing	P2-High	✓ Coveredsecond
AC6:

---

Integration Test Map

Internal System mustDependencies

1. User provideAuthentication quickSystem
   • Role validation
   • Permission enforcement
   • Session management
2. Organization Management
   • Timezone configuration
   • Utility-specific settings
   • Multi-tenant isolation
3. Audit Trail System
   • Change tracking
   • User action logging
   • Compliance reporting

External System Integration Points

1. Field Operations Management
   • Schedule synchronization
   • Working hours alignment
   • Holiday impact assessment
2. Workforce Management
   • Staff scheduling
   • Overtime calculations
   • Holiday pay determination

---

Validation Checklist

✅ All acceptance criteria covered: 3 holiday types, manual addition, visual distinction, configurable hours, weekend status, time presets

TC_006

Preset✅ functionality and availability testing

P2-High

✓ Covered

AC7:

All Workingbusiness hoursrules must be savable and immediately applicable

TC_007

Save functionality and real-time application testing

P1-Critical

✓ Covered

Coverage Summary:

• Total Acceptance Criteria:tested: 7Role permissions, validation rules, save requirements, timezone handling

• ✅ TestCross-browser Cases Covering AC:compatibility: 7Chrome (100%Latest coverage)focus with responsive design validation

✅ Performance benchmarks defined: <3 second page loads, <1 second navigation

✅ Security considerations: Role-based access control, audit trails, input validation

✅ Integration points tested: User management, organization settings, external systems

✅ Edge cases covered: Boundary conditions, invalid inputs, network issues, timezone transitions

✅ API tests for critical operations: Holiday CRUD, working hours configuration, validation endpoints

✅ Proper tagging for 17 reports: Module, priority, phase, type, platform, stakeholder mapping

✅ Realistic test data: Utility-specific holidays, working hours, user roles, timezone scenarios