4 ms·
The “change capture”/straight jacket style tests LLMs like to output drive me nuts. But humans write those all the time too so I shouldn’t be that surprised eit
by girvo 11mo ago
The “change capture”/straight jacket style tests LLMs like to output drive me nuts. But humans write those all the time too so I shouldn’t be that surprised either!
- mulmboy 11mo agoWhat do these look like?
- pmg101 11mo ago1. Take every single function, even private ones. 2. Mock every argument and collaborator. 3. Call the function. 4. Assert the mocks were called in the expected way. These tests help you find inadvertent changes, yes, but they also create constant noise about changes you intend.
- ornornor 11mo agoJuniors on one of the teams I work with only write this kind of tests. It’s tiring, and I have to tell them to test the behaviour, not the implementation. And yet every time they do the same thing. Or rather their AI IDE spits these out.
- senbrow 11mo agoThese tests also break encapsulation in many cases because they're not testing the interface contract, they're testing the implementation.
- girvo 11mo agoYou beat me to it, and yep these are exactly it. “Mock the world then test your mocks”, I’m simply not convinced these have any value at all after my nearly two decades of doing this professionally