Integration tests check whether a limited set of components work together; end-to-end (E2E) tests check whether a broader, integrated system can complete an important workflow. Most teams need both: use focused integration tests to cover risky boundaries, then a smaller set of E2E tests to verify critical user journeys.
Integration testing vs. end-to-end testing
| Dimension | Integration test | End-to-end test |
|---|---|---|
| Scope | A limited group of components or a specific integration point | A broad workflow across an integrated system |
| Main question | Do these components communicate and handle data correctly? | Can the system achieve a user-facing goal through the workflow? |
| Typical boundaries or paths | Database, API, queue, filesystem, or serialization | A critical journey that crosses multiple features or services |
| Dependencies | Often a smaller environment; may use a real dependency or a test double | Exercises more of the application and its dependencies |
| Feedback and diagnosis | Often faster and more focused; a failure can point toward the tested boundary | Often slower; more of the stack may be responsible for a failure |
| Best use | Finding defects at component boundaries | Building confidence in a small set of important complete workflows |
These are tendencies, not guarantees. A broad integration test can be slow or difficult to diagnose, while a carefully designed E2E test can be reliable and useful. Describe the actual scope and dependencies of a test rather than relying on its label.
| # | Preview | Product | Price | |
|---|---|---|---|---|
| 1 |
|
Software Testing | $29.82 | Buy on Amazon |
| 2 |
|
Introduction to Software Testing | $61.23 | Buy on Amazon |
| 3 |
|
Testing Computer Software | $17.15 | Buy on Amazon |
| 4 |
|
A Practitioner's Guide to Software Test Design | $29.93 | Buy on Amazon |
| 5 |
|
Clean Code: A Handbook of Agile Software Craftsmanship | $30.87 | Buy on Amazon |
What an integration test checks
An integration test exercises collaboration across a limited boundary. For example, a test might send a record through an application component and verify that it is stored and read back correctly from a test database. Another might check that an API client parses a service response, or that a producer and consumer handle a queue message consistently.
Google’s 2015 guidance describes an integration test as testing a small group of units together, often two. Martin Fowler’s 2018 guide uses a narrower definition: testing one integration point at a time, such as an application talking to a database or parsing another service’s response. Fowler also notes that some teams use “integration test” to mean broader system coverage. Google Testing Blog (2015) · Martin Fowler (2018)
Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Clear out junk files and repair common Windows errors3Scan for outdated or missing drivers - takes under a minute#1 Best Overall
- Database boundary: Does the application persist, retrieve, and interpret data as intended?
- API boundary: Does the client send the expected request and handle the response, including errors?
- Queue boundary: Do messages retain the expected shape and behavior between producer and consumer?
- Filesystem or serialization boundary: Are files or encoded data written and read in the expected format?
Where practical, run a local dependency or a test instance. Fowler cautions against automated tests that bombard a production service. Record whether the test uses a real dependency or a test double; that choice changes what the test can prove.
What an end-to-end test checks
An E2E test checks a broad, integrated outcome: can a user or external caller complete a meaningful task through the system? A checkout journey, for example, may cross authentication, a cart, payment handling, and order confirmation. The test is valuable because it exercises their orchestration together, not just each boundary in isolation.
Google’s 2021 guidance describes this in terms of Critical User Journeys: workflows that combine a user’s goal with the steps needed to reach it. Such tests can reveal failures that narrower tests cannot establish on their own. Google Testing Blog (2021)
Rank #2
Does an E2E test have to use a browser?
No. Browser automation is a common way to test a user-facing workflow, but broad system scope—not a particular interface—is the defining idea. An API-driven test can cover a substantial server-side workflow without touching a graphical UI. Conversely, a browser test may use test doubles for external services, so it does not necessarily exercise every real dependency. State what the test drives and which dependencies it replaces. Martin Fowler’s practical guide discusses this scope distinction.
Which kind should you choose?
Choose an integration test for boundary risk
When a defect could arise from data mapping, serialization, persistence, a service call, queue behavior, or filesystem access, start with a focused test of that boundary. It can exercise the risky collaboration with less setup than a full journey, and its failure is more likely to narrow the search area.
Choose an E2E test for critical workflow risk
Use E2E coverage when success depends on several parts being orchestrated correctly and the user-visible outcome matters. Keep the set purposeful: broad tests have more dependencies, may take longer, and can leave more possible causes when they fail. Those trade-offs are reasons to select journeys carefully, not reasons to eliminate them.
Rank #3
Investigate failures at the narrowest useful layer
If two components fail to integrate, an appropriately scoped integration test may expose the defect with less setup than an E2E journey. If the failure depends on orchestration across the larger system, a broad test is needed. A layered suite uses each test for the risk it can actually reveal.
How to distribute the test portfolio
Google’s Testing Blog offered a “good first guess” of 70% unit tests, 20% integration tests, and 10% E2E tests in 2015, while explicitly noting that the right mix differs by team. Treat it as a starting heuristic, not a proven optimum or a quota. Google Testing Blog (2015)
Free tools Windows power users keep installed
One-click scans. No signup required.
Google’s 2024 discussion retains the general pyramid intuition—more unit than integration tests, and more integration than E2E tests—while emphasizing that growing suites require further trade-off decisions. The useful question is not whether a team matches a percentage, but whether its tests cover important risks with a sustainable feedback cycle. Google Testing Blog (2024)
Rank #4
Watch for a test hourglass
A suite with many unit and E2E tests but few medium-sized integration tests can leave a gap in sustainable component-integration coverage. Google’s discussion of the “test hourglass” points to system and testability architecture, along with appropriately scoped integration tests, as ways to address that gap. Google Testing Blog (2020)
Document scope, not just labels
Testing terminology is inconsistent across teams and sources. Google’s 2010 discussion itself asks, “Just what, exactly, is an integration test?” For each important test category, document what code or workflow it exercises, which dependencies are real, and which are replaced. That gives reviewers more useful information than a label alone. Google Testing Blog (2010)
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Use ScreenshotNeo for browser-based checks
If part of your E2E coverage needs a screenshot of a web page, ScreenshotNeo is a website screenshot API and MCP server for developers. A screenshot is a useful visual artifact, but it does not by itself prove that a workflow succeeded; pair it with assertions for the behavior you need to verify.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Clear out junk files and repair common Windows errorsFree Scan →Best Value
Or skip the browser setup:
One GET request returns an image or PDF. For example, cURL can save a screenshot as WebP:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpSee the ScreenshotNeo API documentation for request parameters and response details. ScreenshotNeo removes cookie banners, popups, and chat widgets before capture; bot checks, blank pages, and failed loads are never billed; an MCP server lets AI agents take screenshots; and 1,000 screenshots a month are free with no card, with paid plans starting at $5 for 3,000. Sign up for free.
Frequently Asked Questions
Can an integration test use a real database?
Yes. An integration test may use a real dependency or a test double; document which one it uses because that affects what the test verifies.
Can an API test count as end-to-end?
It can, if it exercises a broad integrated workflow and verifies the system outcome. The interface alone does not determine the test category.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
