Glossary · System coordination, integration and orchestration
End-to-end test
Also known as: E2E test, end-to-end testing
German: End-to-End-Test
In software and systems engineering, an end-to-end test is a test that exercises a complete workflow through all involved systems and interfaces, from the initial input to the final result, under conditions close to real operation.
- System integration
In one sentence
An end-to-end test exercises a complete workflow through all involved systems and interfaces, from the first input to the final result.
Example
An end-to-end test releases an order in the ERP and checks that it reaches the MES, is produced on the line, and that the finished quantity is booked back correctly.
How it applies
- Testing: End-to-end tests find errors that unit and interface tests (see Interface test) miss, such as mismatched assumptions between three or more systems. They are slow and fragile, so they complement rather than replace lower-level tests.
- Commissioning: Site acceptance tests often include end-to-end scenarios. Include abnormal cases: cancellations, restarts, communication loss and data corrections.
- Documentation: Test specifications should name the workflow, the systems and versions involved (the Integration baseline), the test data and the expected result in each system. The resulting records are evidence for acceptance.
End-to-end test vs. validation
An end-to-end test checks that a workflow behaves as specified. Validation confirms that the system fulfills its intended use for its users. End-to-end tests can contribute evidence to validation but do not replace it.