Granted lots of mediocre engineers also use the “freeze the results” method for meaningless test coverage,
I’d be interested what you mean by this? Isn’t all unit tests just freezing the result? A method is an algorithm for certain inputs you expect certain outputs, you unit tests these inputs and matching outputs, and add coverage for edge cases because it’s cheap to do with unit tests and these “freeze the results” or rather lock them in so you know that piece of code always works as expected or it’s “frozen/locked in”
RamRabbit@lemmy.world 14 hours ago
It is pretty common to write unit tests for functionality that doesn’t exist (test driven development). ‘freezing the results’ is ok, as long as you know the results are currently correct. The AI has no way of knowing this and poor programmers often don’t verify either.
It is very easy to write a shit test.
kameecoding@lemmy.world 9 hours ago
Oh yeah for sure, I have seen tests that are pretty useless, for me the way I do it is I write the first one or two tests then instruct copilot to follow the patterns and then it does well, ofc I have to double check it, but reading is easier than having to write it.