Build Verification Test

April 26, 2019

What is meant by the Build Verification Test?

Build or Software build is an initial workable version of a software product, developed by integrating the source codes into software artifact. This build may or may not need improvement depending upon its stability to go through further process of testing.

Build Verification Test (BVT) is a set of tests which is executed on every new software build to assess and verify its readiness to face off & undergo through more thorough & rigorous testing procedures. This type of test examines the primary functionalities of the build and accordingly declares the status of the build in terms of acceptance or rejection for further testing activities.

Build Test

As BVT certifies the stability of the build and simultaneously ensures the acceptance of the build, this testing is also known by the name of Build Acceptance Testing. Here, it is pertinent to mention that BVT is just the other name of smoke testing. Build verification test, build acceptance test and smoke test are three different names of one testing methodology.

Build verification test

Why Build Verification Test ?

It may not be guaranteed that whether the newly developed software build is sufficiently stable to go for further testing or not. Testing team puts lots of efforts and time in determining, preparing and executing the test plans and cases on software build so as to improve its quality. However, all this hard work of the testing team goes into astray when at later stage, the build is found to be incapable to sustain further rigorous testing process as it lacks the stability along with the essential functionalities.

build acceptance and rejection

BVT verifies and validates the stability of the build and ensures the acceptability of the build for further testing. This avoids the wastage of precious time and sincere efforts of the test team to work on relatively unstable build.

How Build Verification Test is Performed ?

BVT consists of small set of test cases so as to execute them in no longer time in order to evaluate the mainstream and core functionalities of the build. It starts as soon as a new build is received. The step-wise process of performing the Build Verification test is detailed as under:

Once the build is received BVT cases are prepared on the basis of given core functionalities of the software application.
Developed built verification test cases are executed on the build.
If build passes the BVT, it is considered ready for the further testing activities.
If build fails in BVT, then it gets rejected and considered for further improvement.
Results of BVT are reported to Team Lead or Project Manager.

build acceptance and rejection

These results get evaluated by the Team Lead or Project Manager to trace the main reason (if any) behind the failure of the build.
On locating the defects, the build is passed over to developer along with the reporting of the defects and the issues.
Developer needs to resolve these defects or issues as soon as possible.
On bug-fixation, the new changed build is ready to go again for the BVT.

The BVT is a continuous process and needs to be iterated again and again, until it validates the build's stability to go for the further testing process.

Key Points about Build Verification Test:

Some of the notable features of BVT are

It is also known by the name of Build acceptance test and smoke test.
Executed on every new build.
Software build is not handed over to test team for further testing activities, until it passes the BVT.
Either developer or tester executes BVT.
Sufficient amount of time, needs to be dedicated to write stable test cases, as unstable test cases would not work better in this test.
Automation is preferred to execute BVT cases.
Test cases are of shorter duration and can be estimated in minutes instead hour. Usually, most of the cases are of duration near about 30-45 minutes.
Apart from defects in the build, the other likely reasons for the failure could be the infrastructure issues or the hardware failures.

Build verification test is one of the earliest tests executed on a software application which not only verifies and validates the core and essential functionalities of the application but also prevent testers and saves their valuable time and efforts in testing the unstable build, which may break down at later stages during the course of testing.

You may also like to read our next article on BVT Check-list to explore productive steps and essential points to carry out efficient build verification test.