A small-scale rule of thumb. This article will land much better with a concrete example, but I am drawing a blank here, so you gotta just blindly trust my say so!
Unit and method tests are still useful to quickly find where the issue occured. If you just test the input and output of the program, no its individual units, then in an error case you still need to figure out where it exactly went wrong. So in short, its not just to check if program behaves correctly, unit tests also helps debugging.
I agree if it’s checking if a method gives the right output for a specific input.
But i’m more concernd with checking if it issued the right side effects, i.e. called right services and so on and then checking if it made right calls to the mocks.
Unit and method tests are still useful to quickly find where the issue occured. If you just test the input and output of the program, no its individual units, then in an error case you still need to figure out where it exactly went wrong. So in short, its not just to check if program behaves correctly, unit tests also helps debugging.
I agree if it’s checking if a method gives the right output for a specific input. But i’m more concernd with checking if it issued the right side effects, i.e. called right services and so on and then checking if it made right calls to the mocks.