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/10 Acceptance Criteria Covered)
- Total Test Cases: 20 (10 Functional + 2 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
- Complete Working Hours Setup Journey
- Access Working Days Schedule → Configure weekdays → Set hours → Apply quick presets → Save changes
- Calendar Review and Management Journey
- View calendar → Navigate months → Review existing holidays → Make modifications → Confirm changes
Integration Point Scenarios
- Field Operations Integration
- Working hours impact on field scheduling
- Holiday considerations for meter reading operations
- O&M scheduling coordination with calendar settings
- Notification System Integration
- Calendar change notifications to relevant departments
- Automated updates for schedule modifications
- System-wide holiday announcements
- 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
- 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
- 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
- Authentication & Authorization
- Role-based access validation
- Unauthorized access prevention
- Session management for calendar modifications
- Audit trail for all calendar changes
- 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
- Browser Compatibility
- Chrome (latest 2 versions) - primary browser
- Cross-browser functionality validation
- Desktop resolution optimization (1920x1080+)
- System Compatibility
- Windows 10/11 compatibility
- Organization timezone integration
- Multi-utility environment support
Usability Scenarios
- User Experience
- Intuitive calendar navigation
- Clear holiday type distinction (color coding)
- Easy working hours configuration with sliders
- Quick time preset functionality
- 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
- 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
- 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
- Malformed Data
- Invalid date formats
- Special characters in holiday names
- Negative time values
- Non-existent dates (Feb 30, etc.)
- Security Testing
- SQL injection attempts in holiday names
- XSS prevention in text fields
- Unauthorized API access attempts
- Role escalation prevention
System Failure Scenarios
- Network Issues
- Calendar loading during network interruption
- Save operations during connectivity loss
- Recovery from partial data saves
- Offline vs. online state management
- 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 Case 1: AC1 - Support Three Holiday Types (Federal, Company, Observed)
Test Case Metadata
Test Case ID: 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
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
Test Environment
Environment: Staging
Browser/Version: Chrome 118+
Device/OS: Windows 10/11
Screen_Resolution: Desktop-1920x1080
Dependencies: Calendar Service, Database, Authentication Service
Performance_Baseline: < 3 seconds page load
Data_Requirements: Valid user account with Utility Administrator role
Prerequisites
Setup_Requirements: Calendar & Scheduling module enabled
User_Roles_Permissions: Utility Administrator access
Test_Data: Login credentials for Utility Administrator (admin@testutility.com / TestPass123!)
Prior_Test_Cases: User authentication must pass
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Navigate to Calendar & Scheduling module | Module loads successfully, displays Holiday Calendar section | N/A | Verify page loads < 3 seconds |
2 | Click on Holiday Calendar section | Calendar view displays with option to add holidays | 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 | Click on Holiday Type dropdown | Dropdown displays exactly three options: Federal Holiday, Company Holiday, Observed Holiday | N/A | AC1 Verification: Three holiday types available |
5 | Select "Federal Holiday" from dropdown | Federal Holiday option selected and highlighted | Holiday Type: Federal Holiday | Verify Federal type selection |
6 | Enter holiday name and save | Holiday saved with Federal type, appears with blue color coding | Holiday Name: "Tax Day" | Verify Federal holiday creation |
7 | Add second holiday with "Company Holiday" type | Company Holiday saved with green color coding | Holiday Name: "Company Picnic", Type: Company Holiday | Verify Company type functionality |
8 | Add third holiday with "Observed Holiday" type | Observed Holiday saved with orange color coding | Holiday Name: "Memorial Day Observed", Type: Observed Holiday | 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: System provides exactly three holiday types (Federal, Company, Observed) in dropdown and processes each type correctly
Secondary_Verifications: Each holiday type has distinct visual representation, saves correctly to database
Negative_Verification: No additional holiday types available, no invalid type combinations possible
Test Case 2: AC2 - Manual Holiday Addition Capability
Test Case Metadata
Test Case ID: ONB02US04_TC_002
Title: Validate Users Can Manually Add Holidays to Calendar System
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: Automated
Enhanced Tags for 17 Reports Support
Requirements Traceability
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Navigate to Holiday Calendar section | Calendar interface loads with add holiday capability | N/A | Verify manual entry interface |
2 | Select date April 20, 2025 | Date becomes selected, holiday entry form appears | Date: April 20, 2025 | Verify date selection |
3 | Enter holiday name manually | Text input accepts holiday name | Holiday Name: "Earth Day Celebration" | AC2 Verification: Manual input field working |
4 | Select holiday type from dropdown | Holiday type selection available | Type: Company Holiday | Verify type selection |
5 | Click "Add Holiday" button | Holiday successfully added to calendar | N/A | AC2 Verification: Manual addition complete |
6 | Verify holiday appears in calendar | Holiday visible on selected date with proper formatting | N/A | Verify successful manual 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 holiday appears in holidays list | Both manually added holidays visible in sidebar 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
Test Case 3: AC3 - Visual Holiday Type Distinction in Calendar
Test Case Metadata
Test Case ID: ONB02US04_TC_003
Title: Validate Calendar Visually Distinguishes Between Holiday Types with Color Coding
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0
Classification
Module/Feature: Calendar & Scheduling Management
Test Type: UI/Visual
Test Level: System
Priority: P2-High
Execution Phase: Regression
Automation Status: Manual
Enhanced Tags for 17 Reports Support
Requirements Traceability
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Add Federal Holiday to calendar | Holiday appears with blue color coding | Holiday: "Independence Day", Type: Federal | AC3 Verification: Federal = Blue |
2 | Add Company Holiday to calendar | Holiday appears with green color coding | Holiday: "Company Anniversary", Type: Company | AC3 Verification: Company = Green |
3 | Add Observed Holiday to calendar | Holiday appears with orange color coding | Holiday: "Christmas Observed", Type: Observed | AC3 Verification: Observed = Orange |
4 | View calendar with all three types | All holidays visible with distinct colors | N/A | Verify simultaneous visual distinction |
5 | Check holiday legend/key | Legend shows color coding explanation | N/A | AC3 Verification: Visual legend available |
6 | Navigate to different month and back | Color coding persists across navigation | Navigate Apr → May → Apr | Verify color consistency |
7 | Verify color accessibility compliance | Colors meet accessibility contrast requirements | N/A | Verify WCAG compliance |
8 | Test color distinction for colorblind users | Alternative visual indicators available if needed | N/A | AC3 Final Verification: Accessible distinction |
Verification Points
Primary_Verification: Calendar uses distinct, consistent color coding for each of the three holiday types
Secondary_Verifications: Colors are accessible, legend provided, consistency maintained
Negative_Verification: No color confusion, no missing visual distinctions
Test Case 4: AC4 - Working Hours Configurable for Each Day of Week
Test Case Metadata
Test Case ID: ONB02US04_TC_004
Title: Validate Working Hours Configuration for Each Individual Day of the Week
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: P1-Critical
Execution Phase: Regression
Automation Status: Automated
Enhanced Tags for 17 Reports Support
Requirements Traceability
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Navigate to Working Days Schedule section | Working days configuration interface displays | 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
Requirements Traceability
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
Requirements Traceability
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
Requirements Traceability
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 "Save Changes" button | Success message appears, changes confirmed | N/A | AC7 Verification: Save functionality working |
3 | Verify immediate UI update | Main working days view immediately shows new hours | Display: Monday 8:00 AM - 4:00 PM | AC7 Verification: Immediate application |
4 | Refresh browser page | Working hours persist after page refresh | N/A | Verify database persistence |
5 | Navigate away and return to section | Configuration remains as saved | N/A | Verify session persistence |
6 | Check API response for saved hours | API returns updated working hours configuration | GET /api/v1/calendar/working-hours | AC7 Verification: API immediate update |
7 | Modify Tuesday hours and save | Tuesday changes also immediately applied | 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 Points
Primary_Verification: Working hours can be saved and are immediately visible and 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 Management
Test Case Metadata
Test Case ID: ONB02US04_TC_008
Title: Validate Role-Based Access Control for Calendar Management Functions
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0
Classification
Module/Feature: Calendar & Scheduling Management
Test Type: Security/Functional
Test Level: System
Priority: P1-Critical
Execution Phase: Security
Automation Status: Automated
Enhanced Tags for 17 Reports Support
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Login as Utility Administrator | Access granted to calendar with utility-specific edit rights | utiladmin@testutility.com | Verify Utility Admin access |
2 | Add holiday as Utility Admin | Holiday successfully added for specific utility | Holiday: "Utility Safety Day" | Verify write permissions |
3 | Login as System Admin | Access granted with cross-utility configuration capabilities | sysadmin@testutility.com | Verify System Admin elevated access |
4 | Configure multi-utility settings | Successfully access cross-utility configuration panel | N/A | Verify System Admin privileges |
5 | Login as O&M Manager | Access granted with read-only calendar view | ommanager@testutility.com | Verify limited access |
6 | Attempt to modify as O&M Manager | Modification controls disabled/unavailable | N/A | Verify read-only enforcement |
7 | Login as Meter Reading Supervisor | Access granted with working hours view capability | supervisor@testutility.com | Verify role-specific access |
8 | Verify audit trail captures all actions | All user actions logged with proper attribution | 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
Test Case 9: Holiday Import Standard Holidays Functionality
Test Case Metadata
Test Case ID: ONB02US04_TC_009
Title: Validate Import Standard Holidays Feature for Bulk Holiday Management
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
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Navigate to Holiday Management section | Import standard holidays option available | N/A | Verify import feature access |
2 | Click "Import Standard Holidays" | Import dialog opens with configuration options | N/A | Verify import interface |
3 | Select year and holiday types | Year 2025 selected, Federal holidays checked | Year: 2025, Type: Federal | Configure import parameters |
4 | Execute import process | Import completes successfully with progress indication | N/A | Verify bulk import functionality |
5 | Verify imported holidays appear | 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 handles duplicate prevention appropriately | 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: Standard holidays can be imported efficiently with proper categorization
Secondary_Verifications: Import handles duplicates, selective import works, performance acceptable
Negative_Verification: No data corruption during import, no system performance degradation
Test Case 10: Calendar Month Navigation and Performance
Test Case Metadata
Test Case ID: ONB02US04_TC_010
Title: Validate Calendar Month Navigation Performance and Visual Updates
Created By: Arpita
Created Date: June 08, 2025
Version: 1.0
Classification
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
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Navigate to Holiday Calendar (initial load) | Calendar loads for April 2025 within 3 seconds | N/A | Measure initial load performance |
2 | Click forward navigation arrow (April → May) | May 2025 loads within 1 second with holidays | N/A | Test forward navigation performance |
3 | Navigate backward (May → April) | April loads within 1 second, maintains data | N/A | Test backward navigation performance |
4 | Rapidly navigate through 6 months | Each transition < 1 second, no performance degradation | Apr→May→Jun→Jul→Aug→Sep | Test rapid navigation |
5 | Navigate across year boundary | 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 performance maintained with 50+ holidays | N/A | Test performance under load |
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
Test Case 11: Working Hours Time Boundary and Validation
Test Case Metadata
Test Case ID: ONB02US04_TC_011
Title: Validate Working Hours Time Boundary Handling and Input Validation
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: Full
Automation Status: Automated
Enhanced Tags for 17 Reports Support
Test Procedure
Step # | Action | Expected Result | Test Data | Comments |
|---|---|---|---|---|
1 | Set working hours from 00:00 to 23:59 | Maximum 24-hour range accepted and saved | Start: 00:00, End: 23:59 | Test maximum boundary |
2 | Attempt 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: 23:59 | Test midnight boundary |
8 | Validate time format consistency | 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
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 original holiday unchanged | Original "New Year" holiday remains intact | 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
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
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 format | 400 Bad Request with validation error | {"monday": {"start": "25:00", "end": "17:00"}} | Test time validation |
5 | Test missing required fields | 400 Bad Request with field validation | {"monday": {"enabled": true, "start": "08: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
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
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
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
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
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
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 priority covering all 7 Acceptance Criteria
Test Cases:
- ONB02US04_TC_001 (AC1: Three Holiday Types Support)
- ONB02US04_TC_002 (AC2: Manual Holiday Addition)
- ONB02US04_TC_004 (AC4: Working Hours Per Day Configuration)
- ONB02US04_TC_007 (AC7: Working Hours Save & Apply)
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 functionality
Test Cases:
- All Smoke Test 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 (Holiday API Testing)
- ONB02US04_TC_014 (Working Hours API 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-platform and integration
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. Acceptance Criteria Traceability Matrix
Acceptance Criteria | Test Case(s) | Verification Method | Priority | Status |
|---|---|---|---|---|
AC1: Support three holiday types (federal, company, observed) | TC_001 | Dropdown validation, Type functionality testing | P1-Critical | ✓ Covered |
AC2: Users must be able to manually add holidays | TC_002 | Manual entry process validation | P1-Critical | ✓ Covered |
AC3: Calendar must visually distinguish between holiday types | TC_003 | Color coding verification, Visual distinction testing | P2-High | ✓ Covered |
AC4: Working hours configurable for each day of week | TC_004 | Individual day configuration testing | P1-Critical | ✓ Covered |
AC5: Weekend working status must be definable | TC_005 | Weekend status configuration testing | P2-High | ✓ Covered |
AC6: System must provide quick time presets | TC_006 | Preset functionality and availability testing | P2-High | ✓ Covered |
AC7: Working hours must be savable and immediately applicable | TC_007 | Save functionality and real-time application testing | P1-Critical | ✓ Covered |
Coverage Summary:
- Total Acceptance Criteria: 7
- Test Cases Covering AC: 7 (100% coverage)