Fuzz test without oracle
An AI agent wrote a Go fuzz test for your custom URL-path parser. It looks thorough:
The agent says 'this fuzzes the parser and will find crashes.' What is this fuzz test actually checking, what is it missing, and how would you give it a real oracle?
Implement
normalize_path(raw: str) → strExamples
in
["/a/b/c"]out"/a/b/c"in
["//a//b/"]out"/a/b"in
["/a/../.."]out""What a strong answer looks like
Treat the AI’s output as a draft to verify, not an answer to trust. Name the specific flaw and the input that triggers it, say how you’d catch it (tests, edge cases, reading critically), and how you’d re-prompt or decompose to get it right.
0:00 of about 22 min
Vibe & agentic: describe the solution in plain language (or narrate it) and the coach grades your approach.
Which questions mattered is sealed until you submit. Telling you now would just be handing over the edge cases.
Run or narrate your approach, then ask the coach.