Build Verification Test
A Build Verification Test (BVT) is a set of tests that verifies whether a new software build is stable enough for further testing.
“An automated test that validates the integrity of each new build and verifies its key/core functionality, stability, and testability.”
(Definition reproduced from the ISTQB Glossary. Copyright belongs to ISTQB.)
View the complete ISTQB GlossaryWhat is Build Verification Test?
A BVT quickly checks the most important system functions after a build is deployed. If the build fails these tests, detailed testing usually does not continue.
Early validation: Confirms that the build is testable before executing a larger test suite.
Critical functionality: Focuses on essential workflows and system startup.
Relationship to smoke testing: BVT is often considered a type of smoke test performed after every build.
Real World Example
A regulated product team is preparing a release where Build verification test appears in reviews, test design conversations, or defect triage rather than as an isolated glossary word.
The risk is that the team treats Build verification test as interchangeable with nearby ISTQB terms. That makes test scope blurry and can lead to weak evidence for the release decision.
The tester anchors the discussion in the official definition, asks where the concept appears in the product, and designs examples that show the difference between Build verification test and similar ideas.
The page becomes useful in practice because Build verification test is connected to a specific testing decision, not memorized as a detached definition.
Practice Questions
Question 1
Which suite BEST represents a BVT?
Question 2
A BVT fails intermittently on login. What is the BEST action?
Test your knowledge with real ISTQB-style questions
You’ve learned Build Verification Test. Test your understanding with topic-specific questions in our Mock Exams.