“No Duh,” say senior developers everywhere.
The article explains that vibe code often is close, but not quite, functional, requiring developers to go in and find where the problems are - resulting in a net slowdown of development rather than productivity gains.
I’ve seen it generate working unit tests plenty. In the sense that they pass.
…they do not actually test the functionality. Of course that function returns what you’re asserting - you overwrote its actual output and checked against that!