2 ms·
You are then testing other peoples software, which is probably not what you want. In integration testing I see no issue in using a real instance of whatever de
by danielovichdk 3y ago
You are then testing other peoples software, which is probably not what you want.
In integration testing I see no issue in using a real instance of whatever dependency but I would never assert on the inner workings of that dependency - that is within the testing scope for the people that did that dependency, not you.
- randomdata 3y ago> You are then testing other peoples software, which is probably not what you want. And if it is what you want, why would you clutter an unrelated application's codebase with those tests? They are tests that apply to many projects. Ideally they would go alongside the work of the third-party, but failing that, surely the are better found in a new project focused on those tests?