3 ms·
> Integration test the rest if needed. Is there any situation where there is integration, but no need to test it? You seem to be suggesting that if the leaves
by mannykannot 9y ago
> Integration test the rest if needed.
Is there any situation where there is integration, but no need to test it?
You seem to be suggesting that if the leaves are thoroughly tested, nothing can go wrong in their integration, but at the same time, I cannot imagine someone believing that.
- 1_player 9y agoIntegration tests are always needed in some form, because you need to make sure the leaves are actually called, since unit tests are executed in a vacuum, the functions might work but might never be called at all, or might not work because of weird bugs that appear when only testing the whole tree.
- therealdrag0 9y agoExactly, most bugs I see are in integration, mis-matches in data-models or state. But I also work on business-y applications which tend to be more integrations than local business logic.