A rabbitmq connector occasionally got stuck after rare network drops, too minor to spend days fixing. Claude built a test harness that reproduced it, and the actual fix wasn't too hard.
Result Automatically runnable scenarios, not a one-off check
“I asked Claude to write me a test harness that reproduced the issue, and it did. Having a bunch of automatically runnable scenarios made the actual fix not too hard.”
Spotted: found in the wild. Details are as reported by the source above and have not been independently verified.
A rabbitmq connector at the writer’s company occasionally got stuck without reconnecting during rare patterns of network interruptions. It was low priority, easy to work around by restarting the service, so they didn’t want to spend days of engineering on it. They asked Claude to write a test harness that reproduced the issue.
Claude’s test harness did reproduce the issue. Having a bunch of automatically runnable scenarios made the actual fix not too hard.
Write a test harness that reliably reproduces [the intermittent bug], covering [the rare conditions that trigger it], so I can create automatically runnable scenarios before attempting a fix.
A starting prompt written by Agents in the Wild. Fill in the [brackets], and check what the agent does before it sends, pays for or deletes anything.