Fuzzing
Also called Fuzz testing
Throwing huge numbers of random or damaged inputs at a program to see if it crashes or hangs. You do not need to know the right answer, only that it should survive.
Agents tend to write the happy path and test the happy path. A fuzzer has no idea what the happy path is. That makes it especially good for anything that parses input from outside, which is often where the security bugs are.
Say it to your agent
“Write a fuzz test for parseCookie: generate 100,000 strings, some random and some damaged copies of "a=1; b=2", and fail if it throws anything other than our own ParseError. Add every crash you find as a regression test.”