🧪 test: improve edge case coverage for invalid update values#32
Conversation
Added a test case for `store.update` that verifies the state remains unchanged when invalid parameters like `null` or a string are passed. This improves the test coverage and ensures the behavior defined in `dispatchUpdate` remains reliable. Co-authored-by: johnstrand <11484777+johnstrand@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. |
🎯 What: Added a missing edge case test for the
store.updatefunction when receiving invalid values.📊 Coverage: Now validates that calling
store.update(null)orstore.update("string")does not unintentionally mutate state.✨ Result: Improved test coverage and reliability for state updates via
Squawk.update.PR created automatically by Jules for task 8338251468620585122 started by @johnstrand