Bug: Date parsing error in outcome-resolver service

[WFord26]

Issue Description

Outcome resolver service is throwing \Invalid time value\ errors when processing game results from ESPN API.

Error Details

\
Error checking game result: Invalid time value
\\

Observed In

• CI/CD test runs
• Backend test suite: outcome-resolver.service.test.ts
• Appears to occur during date/time parsing of game data

Impact

• 2 backend tests failing intermittently
• May affect bet settlement for completed games
• Environmental/timing dependent issue

Investigation Needed

1. Identify which date field is causing the parsing error
2. Review date/time handling in ESPN API response processing
3. Add proper date validation and error handling
4. Ensure timezone handling is correct

Reproduction

Run backend tests and check outcome-resolver service logs for date parsing errors.

Priority

Medium - Environmental issue that doesn't block core functionality but should be investigated for production stability.

Related

• Identified during PR Analytics Planning & Dashboard Version Bump #11 merge
• Part of backend test suite improvements

[WFord26]

Fixed in commit 5d3ea11.

Changes Made

• Added validation for missing/null commenceTime before date parsing
• Added check for invalid dates using isNaN(date.getTime())
• Returns null gracefully with appropriate logging instead of throwing errors
• Added commenceTime to all mock games in tests
• Added two new test cases specifically for missing and invalid commenceTime

Test Results

All 23 tests in outcome-resolver.service.test.ts now passing:

• should resolve outcomes for completed games
• should handle API errors gracefully
• should skip games that are not completed
• should handle missing commenceTime gracefully (NEW)
• should handle invalid commenceTime gracefully (NEW)
• Plus 18 other existing tests

The Invalid time value error is now resolved. The service handles edge cases gracefully with proper logging.