3 ms·
>I'm pretty sure he means "just use integration tests". Really he means e2e testing. You can drive yourself mad writing integrations that break constantly or p
by ramesh31 5y ago
>I'm pretty sure he means "just use integration tests".
Really he means e2e testing. You can drive yourself mad writing integrations that break constantly or provide false positives. Better to unit test what is truly unit testable, and then rely on e2e to ensure your integrations are fine. Ultimately all that matters is the system running as expected at the user level.
- nicoburns 5y agoI think that depends on the scope of what you're testing. If you have a database, a set of backend services and 1 or more clients (websites, mobile apps, etc), then I think it makes a lot of sense to test the backend services in isolation from the frontends (which would mean not e2e test), but backend by an actual database (so integration tests, not unit tests)