QA City

Most Popular

What is Build Verification Testing?

By SiliconIndia   |  
Print Email

Bangalore: Before a developer can give out his software, he gets it checked by a testing team. And before sending the software for testing, he needs to ensure that it is testable because if the software is not compliant with the testing, it will definitely be rejected. So in order to save the time and effort of the testing team, prior to handing over the software for testing, the developer verifies his software with BVT. Build Verification Test are a series of tests that validate the core functionality of the software.  Normally BVT is a fully automated process and to clear it the software needs to be steady and accessible for testing in detail.

Key Points about BVT:

1. BVT is one of tests that authenticate mainstream functionalities.

2. It is needless to say that BVTs need to be designed in a way that they are able to test every aspect of basic functionality.

3. Normally, the BVT’s are used for daily builds of software and they mainly check 2 things build validation and build acceptance.

4. Usually BVT do not take more than half an hour to run.

5. When the daily build does not clear the BVT, the developer needs to work on a new build that he has to again submit to BVT.

6. The main reason for using BVT is to prevent wasting the energy and time of a test team to setup tests for a daily build that lacks stability.

7. BVT also called as SMOKE TESTING is a sort of Regression Analysis that is done on each and every new build.

Normally a company allots various modules of a single project to different teams. In such cases the integration of all these modules is critical. Inappropriate compilation of modules can lead to application failure. BVT mainly tests the integrity of the project so that no completed project is scraped out only due to the disintegration of its modules.

What happens after a BVT is run?

Suppose if the developer has a new build and it is checked with automated Build Verification Test

1. The result of BVT will be emailed to everyone related with that project.

2. The person responsible for running and maintaining the BVT will examine the results.

3. In case the build does not pass the BVT then the person testing it with BVT will analyze the cause of its failure.

4. If the reason for failing BVT is a flaw in the build, all the necessary data including the failure logs will be sent to its developer.

5. The developer scrutinizes the cause of failure and reports it to the BVT team. He examines whether that is a problem of bug or not. In case of a bug, the developer needs to report how he will fix this bug.

6. Once the bug is fixed, the build is once again run through BVT. After it clears the BVT, it is passed to the testing team for further testing and analysis in detail.

Don't Miss
Experts on QA
Swaid Qadir Bhat
Sr System Architect
Virtusa Corporation
Subhash  Motwani
Prasad Rao Pasam
Ayaskanta  Mohanty
Managing Director
TATWA Technologies
Rajesh  Dagar
Software Architect
Connect Icon Pvt Ltd
Yasar  Khuthub
Software QA Manager
Azure IT Solutions
Sunil  Bhat
Project Management
HCL Infosystems Limi
Sharad  Agarwal
Team Lead
Write your comment now
This report is the result of the largest public-private sector rese...
For those not familiar with the Coverity Scan™ service, i...