4 ms·
My quandary with this logic is that it leads to a slippery slope. If unit tests are not tests because they don't cover the other parts of the program, by the sa
by majewsky 9y ago
My quandary with this logic is that it leads to a slippery slope. If unit tests are not tests because they don't cover the other parts of the program, by the same logic, integration tests are not tests because they don't cover the other programs you're using it together with. Even end-to-end tests may not be tests because they don't cover the users that interact with your system. And we all know that in many cases, users are the biggest source of entropy in our systems. :)
In the end, you'll always need some combination of unit tests, integration tests and end-to-end tests. Unit and integration tests come from the developer of the software in question, and end-to-end tests are developed by devops or by the sysadmins. And you decide how much testing to do and where based on how much confidence you get out of these tests. A test is only useful and warranted if it being green increases your confidence that the software will work correctly once deployed.