Suggest an editImprove this articleRefine the answer for “How do E2E tests differ from unit tests?”. Your changes go to moderation before they’re published.Approval requiredContentWhat you’re changing🇺🇸EN🇺🇦UAPreviewTitle (EN)Short answer (EN)**Unit tests** check an individual function or component in isolation, quickly and without external services. **E2E tests** check the whole scenario, like a user, with real APIs, a database and the UI. **Key point:** a unit test is about small logic, an E2E test is about the real behavior of the whole application end-to-end.Shown above the full answer for quick recall.Answer (EN)ImageThe difference in short: | Criterion | Unit tests | E2E tests | | --- | --- | --- | | **What they check** | an individual function or component in isolation | the whole scenario, like a user | | **Speed** | very fast | slow | | **Dependencies** | no external services (mocks) | real APIs, database, UI | | **Goal** | make sure small parts work correctly on their own | make sure the system works end-to-end without failures | Summary: unit test → about small logic, E2E → about the real behavior of the whole application.For the reviewerNote to the moderator (optional)Visible only to the moderator. Helps review go faster.