🧪 Add explicit DecoderException test in UploadId constructor#100
Conversation
Provides a malformed URL encoded string that throws DecoderException to test the fallback of using the input value as is. Co-authored-by: tomdesair <14034630+tomdesair@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. |
|
coverage: 95.125% (-0.04%) from 95.164% — feature/add-decoder-exception-test-4778707476590793195 into master |
2 participants
🎯 What: The testing gap addressed: Missing error test for
DecoderExceptioninUploadIdconstructor.📊 Coverage: What scenarios are now tested: A malformed URL string starting with
%but not followed by valid hex characters (e.g.%zz) which throws aDecoderExceptionand triggers the fallback branch.✨ Result: The improvement in test coverage: We now explicitly cover the catch block for
DecoderExceptionand verify the value is assigned correctly as-is.PR created automatically by Jules for task 4778707476590793195 started by @tomdesair