3 ms·

Different people tend to have completely different ideas about what an integration test is. At one extreme, some people think it means that you have your entir

Different people tend to have completely different ideas about what an integration test is. At one extreme, some people think it means that you have your entire system running and then you have some headless bot simulate clicks and evaluate the system's behavior based on the UI... From my point of view, any test that traverses through the logic of more than one kind of object is an integration test. Primitive types don't count. I actually find integration tests much more useful than unit tests. It's unusual for me to come across a unit of code that is so complex on its own that it needs to be tested in isolation. I think that simple units of code is actually a sign of good de

jondubois 9y ago
...sign. Isn't that the whole idea behind keeping methods short and classes high cohesion? The simpler your unit of code is, the less useful your unit test becomes. By that definition, I reach the opposite conclusion as the author's. The problem with unit tests is that they assume that most of the complexity lies in individual functions. From my experience, most of the complexity and unpredictability of software lies in the wiring logic between components. Most difficult software bugs are not the result of a function not working correctly - Most of the time, it is simply the result of a function not being used correctly... E.g. Someone make an incorrect assumpti