🧪 Add tests for loadTrace timings and warnings - #159
Conversation
Implemented tests to cover the `monotonicNow` and `createLoadTrace` logic in `src/loadTrace.ts`. Ensures fallback from `performance.now` to `Date.now` is tested, and that relative timings (`sinceStartMs`, `sincePreviousMs`) and load completion duration logs work properly.
|
👋 Jules, reporting for duty! I'm here to lend a hand with this pull request. When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down. I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job! For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
🎯 What: Missing tests for
createLoadTraceinloadTrace.tsaddressed.📊 Coverage:
monotonicNowfallback logic, relative timing calculations, and debug/warn logs for normal, slow phase, and slow load scenarios are now tested.✨ Result: Enhanced test coverage that guarantees load traces track relative timings deterministically without polluting test runners.
PR created automatically by Jules for task 9752482501169696476 started by @MarsLuay