Loading content
Testing is the systematic verification of software to find defects, deviations, and quality issues. It includes strategies, techniques and test types (unit, integration, system, acceptance), plus automation and metrics for assessment. The goal is more reliable software, reduced risk, and early detection of regressions.
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 you need to understand to reason about a domain.
Testing examines software deliberately for expected behaviour, defects and quality attributes.
Software testing grew with the first programmable systems from the need to check computing programs reliably. As systems became more complex, formal testing methods and organizations such as ISTQB emerged to structure terminology, techniques and qualifications internationally.
Tests specify inputs, conditions and expected results, then compare them with observed behaviour. Unit, integration, system and acceptance tests inspect different slices; manual and automated checks complement one another. Tests provide evidence about a risk but do not prove a system is defect-free.
Deliberate checks expose gaps between expected and observed software behaviour.
Test cases combine conditions, inputs and oracles so behaviour can be evaluated.
Scope and test type follow risk, system level, change size and available feedback.
Testing informs release decisions, exposes regressions and reduces the risk that changes silently damage existing behaviour.
Where this building block is located in the topic model.
No structure path available.
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.