Build verification Testing

Build verification Testing[BVT]:

• Build verification testing is also called as smoke testing. 
• Build verification is a set of tests run on new build to verify that whether the build is testable for further testing. 
• It is done priorly by test team before build pass to testing team for further testing. 
• This testing is mainly done for build validation and build acceptance. 
• This test contains pre-defined Test Cases which focus on the core functionality of software application to make sure that build is stable or not to start with actual testing. 
• This test is done for each new build if any of tests got failed that build is rejected by testing team. 
• If BVT fails, build gets assigned to developer for fix and testing continues on the previous build 

     So build acceptance tests are a type of regression testing that is done every time a new build is taken. Build acceptance tests are important because they let developers know right away if there is a serious problem with the build, and they save the test team wasted time and frustration.

BVT basics:

• It is a subset of tests that verify main functionalities. 
• The BVT’s are typically run on daily builds and if the BVT fails the build is rejected and a new build is released after the fixes are done. 
• The advantage of BVT is it saves the efforts of a test team to setup and test a build when major functionality is broken. 
• Design BVTs carefully enough to cover basic functionality. 
• Typically BVT should not run more than 30 minutes. 
• BVT is a type of regression testing, done on each and every new build. 
• BVT cases & process should not implemented in hurry. 
• Include only stable test cases, which have known expected results and don’t add unstable test cases. 

Check List in BVT:
BVT primarily checks for the project integrity and checks whether all the modules are integrated properly or not. Module integration testing is very important when different teams develop project modules. Check whether the Developed modules are affected or not

Real Time Process for Build verification testing:

• · The results are sent to TL / PM 
• · Results are analyzed by TL / PM 
• · The person who runs the tests and TL / PM diagnoses the cause of failure (if any) 
• · If there is any defect, the relevant information is sent to respective developers 
• · Developer fixes the bug 

Once the bug is fixed; BVT test suite is executed again. This process gets repeated for every new build.
Example:
BVTs for Notepad -
Test cases for writing something into text editor.
Test case for cut, copy and paste.
Test case for saving text file.

These are some sample test cases, which can be marked as ‘critical’ and for every minor or major changes in application these basic critical test cases should be executed. This task can be easily accomplished by BVT.