5 ms·
This sort of discussion often gets confused because people have different ideas about what integration tests are and therefore talk past each other. I generall
by skybrian 9y ago
This sort of discussion often gets confused because people have different ideas about what integration tests are and therefore talk past each other.
I generally avoid the term altogether and recommend testing stable API's (which are often public) and avoiding testing internal API's that are more likely to change. This assumes you have a stable API, but that's true of most libraries.
- betageek 9y agoExactly - Integration tests !== E2E tests
- profalseidol 9y agoMartin Fowler solves this by introducing: SubcutaneousTest https://martinfowler.com/bliki/SubcutaneousTest.html https://martinfowler.com/bliki/SubcutaneousTest.html
- MartinCron 9y agoCatchy.
- Lord_Zero 9y agoI think we are discussing what it means to test a stable API or an internal API. Not just testing them in general. We're talking about making architecture decisions on your code in the interest of test-ability. Regardless of the visibility of your API you will still need to unit test the logic will you not? Do you test your controllers and then the response from your service layer? Is all your logic in your actions?