🧪 Add test for initWasm error path - #17
Conversation
Add a test for initWasm network error path using jest and jsdom. It mocks fetch to return a rejected promise to simulate an error, and evaluates the initWasm script from index.html inside a jsdom window to assert that the statusDiv text content is updated with the error message. Included jest dependencies and setup files for the environment. Co-authored-by: paul0728 <44644609+paul0728@users.noreply.github.com>
|
👋 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. |
1 participant
🎯 What: The missing error path test for the
initWasmfunction was addressed.📊 Coverage: The test now covers the scenario where fetching the WASM binary fails (simulated network error), ensuring the catch block is executed and handles the error gracefully.
✨ Result: Increased test coverage for error conditions during WASM initialization.
Includes necessary dependencies (
jest,jest-environment-jsdom,jsdom) and configuration to run tests on inline scripts by extracting them into a JSDOM environment.PR created automatically by Jules for task 16935446410821713249 started by @paul0728