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 3 days 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.