π§ͺ Add tests for extract_content in secret_scanner.py#1
π§ͺ Add tests for extract_content in secret_scanner.py#1google-labs-jules[bot] wants to merge 1 commit into
Conversation
|
π 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: Testing gap addressed for the
extract_contentfunction inhooks/secret_scanner.py. The function was lacking automated tests.π Coverage: Scenarios for
Writetool (with and without "content" key),Edittool (with and without "new_string" key), and unhandled tool types (returning empty string) are now tested.β¨ Result: 100% test coverage for the
extract_contentfunction, improving reliability and confidence for future refactoring.PR created automatically by Jules for task 7057320559286808141 started by @zknpr