Loading content
Manual testing is a hands-on method for validating software quality by human testers. It covers exploratory, functional and regression testing without automation and excels at usability and visual checks and ad-hoc investigations. It complements automated testing, aiding risk discovery, acceptance criteria validation and exploratory test design.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
Manual testing checks software through deliberate human interaction instead of fully automated test execution.
It emerged from evaluating software in real usage situations and through human judgment. No single originator or definite founding year is established.
A person follows a scenario, observes behavior, and records preconditions, steps, expected results, and actual results. Test cases provide repeatability; exploratory testing seeks unexpected findings. Browser, device, data, and version are part of the test context.
A concrete usage flow bounds the purpose and starting state.
Visible behavior and traceable notes form the finding.
Open-ended probing finds risks beyond predefined cases.
Manual testing is valuable for exploratory, visual, and user-facing questions. It takes time and scales poorly for frequent regression checks, which are candidates for automation.
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.