End-to-end Testing
End-to-end testing verifies complete business workflows across the entire system, including integrated applications, databases, and external services.
“A test type in which business processes are tested from start to finish under production-like circumstances.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is End-to-end Testing?
End-to-end testing validates that all components work together correctly from the user's perspective by executing realistic business scenarios.
Complete workflow: Tests span multiple integrated systems.
Realistic scenarios: Simulates actual user activities.
Integration focus: Detects issues that isolated testing may miss.
Real World Example
A regulated product team is preparing a release where End-to-end testing appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats End-to-end testing as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between End-to-end testing and similar ideas.
The page becomes useful in practice because End-to-end testing is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which statement BEST describes End-to-end testing in the context of ISTQB terminology?
Question 2
A tester needs to explain End-to-end testing to a non‑technical stakeholder. Which approach is MOST appropriate?
Test your knowledge with real ISTQB-style questions
You’ve learned End-to-end Testing. Test your understanding with topic-specific questions in our Mock Exams.