Loading content
Smoke testing is a lightweight testing method that quickly verifies basic system functionality after changes or deployments. It focuses on critical paths to detect showstoppers early and prevent wasteful deeper testing. Smoke tests are fast, scriptable checks used in CI/CD pipelines and release gating.
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.
Smoke testing uses a few essential checks to determine whether a build is stable enough for further testing.
The term transfers the workshop check for obvious smoke signs in a device to software. Early development and release processes turned it into a fast build check before deeper examination.
Select the most important start, navigation, and core functions. If one fails, stop the next test stage; if all pass, treat that only as permission for broader testing.
A build is a generated, testable version of software.
The critical path covers the essential steps of central use.
The result decides whether the next test stage can begin.
Smoke testing gives teams an early signal of basic stability. It avoids spending deep-test time on an obviously unusable build.
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.