Test Levels describes the hierarchy of tests (unit, integration, system, acceptance) for systematic software quality assurance. It defines purpose, scope and responsibilities at each level and guides test strategy, automation effort and fault localization. It also supports prioritization and allocation of testing resources.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What organizes, connects, or makes decisions possible.
Test levels classify examinations by scope: from individual units through integrated components to the complete system and acceptance.
The division into test levels grew from software-testing practice and was popularized through testing standards and the ISTQB vocabulary. It gives teams a shared language for checking quality and requirements at different scopes.
Unit tests check small building blocks in isolation; integration tests examine their interaction. System tests consider the integrated product, while acceptance tests assess its suitability for users or customers. Each level has its own objectives, data, responsibilities and characteristic failure modes.
Tests are organized by the system scope and the purpose of the examination.
Several levels complement one another, moving from individual components to a usable system.
Teams assign responsibility, automation and diagnosis to the appropriate level.
Test levels support a balanced test strategy, faster fault isolation and clear ownership of each examination.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.