2 ms·
In such a system there's typically two kinds of E2E. E2E for the team's service and end to end for the entire system. If you can't write the former without acc
by pydry 6y ago
In such a system there's typically two kinds of E2E. E2E for the team's service and end to end for the entire system.
If you can't write the former without acceptable debugging tools your tests suck and you should rewrite them.
If you are a team writing a micro service in an ecosystem of micro services, you need to write E2E tests that mock systems external to yours and have very clear agreements/contracts about how they interact as well as a QA team to test the system as a whole coz otherwise each bug that crosses a layer degenerates into an orgy of finger pointing. Ideally debugging at that scale should be rare and done with multiple members from multiple teams.
- geoelectric 6y agoIn almost every org I’ve been in, E2E meant full thickness UI to datastore and back tests. That’s where I was coming from. I’ve never considered the single service tests E2E, more either a component test suite or a public API unit test suite (same thing). I agree you’d want those with collaborators mocked, and it’s where I’d lean the bulk of my test strategy for a system like that from a QA POV (as well as promoting internal API unit testing from a dev POV).