Repository navigation
🧪 Add error path tests for expectString - #52
Conversation
* Exported expectString from validate-metadata.js * Added negative test cases to validate-metadata.test.js including: * Non-string values * Null values * Empty strings * Whitespace only strings * Valid strings Co-authored-by: akutuva21 <44119804+akutuva21@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: Added missing unit test coverage for the
expectStringerror paths inscripts/validate-metadata.js.📊 Coverage: Now validates that empty strings, whitespace strings, null, and non-string types correctly append error strings to the errors array, as well as testing a happy path where no error is appended for valid strings.
✨ Result: Better error-path test coverage for
expectStringmetadata validation utility, giving higher confidence when modifying this core validation code.PR created automatically by Jules for task 18028944396216067368 started by @akutuva21