Testebenen

Testebenen is a term used primarily in German-language and, by extension, Dutch-language quality assurance literature to describe the different stages at which software testing is performed. The concept helps organize testing work, allocate resources, and clarify responsibilities across teams. While the exact terminology varies, typical testebenen include unit testing at the lowest level, followed by integration testing, system testing, and acceptance testing at the highest level. Additional non-functional testebenen such as performance testing, security testing, and usability testing may be defined as part of the broader testing strategy.

Unit testing targets individual components or functions in isolation. It aims to verify that a small piece of code behaves correctly, often using automated tests and test doubles to simulate dependencies. Integration testing checks the interactions between units or modules to ensure that combined parts function together as intended. There are various approaches to integration testing, including top-down and bottom-up strategies, and the use of mocks or stubs to emulate missing components.

System testing evaluates the complete and integrated system against the defined requirements. It is typically performed in an environment that mirrors production and focuses on end-to-end functionality, data flows, and overall behavior. Acceptance testing, conducted by customers or end users or by a dedicated QA team, assesses whether the system meets user needs and defined acceptance criteria before release.

Usage and variations of the term can differ by organization. Some teams prefer the terms test levels or test layers, and the concrete definitions of each level may be adapted to fit the project’s methodology and compliance requirements.