Re:How the Claude Code team thinks about verification
by anshumankmr on Tuesday November 17, 2026 @12:10PM
(#50534595)
Honestly, the amount of bullshit unit tests Claude keeps pushing nowadays. I took a few hours the past few weeks, some with AI, some by myself to hand remove some really dumb fucking test cases. God knows how long the CI must be running when these guys push their code.
[ Parent
| on HN ]
Re:How the Claude Code team thinks about verification
by AlienRobot on Tuesday November 17, 2026 @01:09PM
(#50535623)
I wonder what was it even trained on?
Who ever had the time and will to write unit tests that mock every single function/class being called, checks the strings of thrown errors, etc., for every single function, for several tests per function?
The instant you change the implementation the tests break because it's testing how many times each method has been called of an object that was passed as argument.
That's just an insane way of writing tests. But for AI that's normal for some reason.
It feels like it's making unit tests the "textbook" way that in practice you wouldn't do because in practice half the things it's testing are inconsequential.
Re:How the Claude Code team thinks about verification
by Groxx on Tuesday November 17, 2026 @03:55PM
(#50538060)
[delayed]
Re:How the Claude Code team thinks about verification
by bmitc on Tuesday November 17, 2026 @07:36PM
(#50540322)
Claude Code will often just test that data types, like structs or dataclasses can just have their fields read and written. It's infuriating. I don't let Claude write tests anymore without strict supervision.