Post

Jamon
@jamon.dev

Settle an argument: what is an integration test, and is that the same as an end-to-end test? Secondly, is testing a React component a "unit test"?

Artem Zakharchenko
@kettanaito.com

An e2e test is focused on the behaviors related to entire usage flows. This one is the trickiest to define because the "ends" of your software differ based on the software itself. E.g. for a web app, e2e is the end user interacting in your software in the end environment (the browser).

Tomasz Ducin
@ducin.dev

FWIW 😛 I see e2e tests differently, considering webapps. IMO e2e means that the entire environment takes part in the test : Fe, be, db, network etc. E2E tests don't have to rely on browsers BTW! (see backend contract tests) Integration on the other hand means that more than 1 piece is used /1

0 reposts2 likes

Tomasz Ducin
@ducin.dev

There could be a UI integration test, but there could be a backend integration test also (e.g. server side controller communicating with a real socket via HTTP but nothing more than the connection itself, e.g. no DB queries). All in all both E2E and integration could test entire user flows.