Add fuzzing infrastructure and failing test cases#10
Conversation
- Create `fuzz-generator` crate for automated testing - Add `fuzz-generator` to workspace members - Add discovered failing test cases to `test-data/` - Identify issues with quoting/escaping and enum variant collisions in codegen Co-authored-by: zahash <36153955+zahash@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
Introduces a fuzzing tool to the workspace to generate diverse JSON inputs for testing the robustness of the codegen crates. The fuzzer identified failing test cases related to string escaping in keys and potential enum variant collisions, which have been added to the test data.
PR created automatically by Jules for task 3562269172543571879 started by @zahash