At that point, that's just testing for the sake of testing, which is just silly - nobody needs you to prove that the compiler/interpreter/library/framework in fact works the way its maintainers have already tested it to work
Yeah, the most you should be testing there is “it’s a function and it calls the (mock) db and returns data of type whatever”.
That’s like... 2 minutes of test writing, tops?
I think that we really need to discuss unit testing as a group more. Specifically: what a unit test isn’t. It’s amazing how popular some misguided and ill-informed ideas about them are...
