i thik its regression testing....if i am wrong ,plz correct 
me

It is sanity testing

Build Verification Testing is SMOKE TESTING.

Here we should check the application's stability like 
whether it is working without any hangouts.

Build varification Testing is nothing but Sanity
Testing/level-0 testing/build verification testing etc.,
because this test is the first test which we are conducting
as soon as we get the build from development team. here we
are checking/verifing wether the build is operatable,
understandable,or not and wether the build is stable.
 Mainly we are concentrating on wether the build is working
or not and operatable or not etc., means verifying the build.

Hi Neelavathi,u r right,but small mistake,that
build verification testing is nothing but smoke testing 
which means,testing the build which was come first from the 
development team,is working or not for futher testing.
eg.check the build whether it is giving any crashes,or any 
run time errors while executing the build friquently.this 
is called as bvt.

Build Verification Testing is nothing but Sanity Testing...

BVT is a smoke testing.

Please be clear wht the difference between sanity n smoke 
testing. that will help u a lot :)

Build verificartion testing is sanity testing.Sanity 
testing is intial level of testing.after Getting a build we 
check all the major functionalities are working properly. 
in my company we called this as a sanity testing.

After the unit testing is completed the code will be 
realsed to the  build team for deploying in the testing 
environment. Build team is setup the environment and 
validates the basic functionalities like, all the logins 
are setup, testers has appropriately user permission to the 
database and application launching etc.. This testing is 
called build verification testing.

smoke testing is the testing in which we will test the 
major functionality.(Ex:whether the links are working or 
not....suppose we have a banking application inorder to 
transfer money from the account first the user has to 
login...If the user tries to login the application may show 
you an error page ...so you cant test the functionality of 
transfering the money)
Here we have to make sure that the application is testable 
or not.

In Sanity testing we have to test whether the application 
is crashing your operating system files or database is 
corrupted because of running the application.

In both the cases we are going to get the stable build

when ever the build is released in to the testing 
department they check the build whether it is ready for 
detail testing or not, i.e called as B.V.T. some companies 
called it as smoke testing and sanity testing.

Build Verification Test (BVT) is also known as Build 
Acceptance Test, is a set of tests run on each new build of 
a product to verify that the build is testable before the 
build is released into the hands of the test team. The 
build acceptance test is generally a short set of tests, 
which exercises the mainstream functionality of the 
application software. Any build that fails the build 
verification test is rejected, and testing continues on the 
previous build

Build means-once developer Fixed the bug and given for
retesting that particular functionality we will be saying
build1 if again the bug is reponed and given to developer
for bug fixing and this cycle says bulid2 this is know as Build

In BVT, basically we have two parts.

1.Smoke Testing: Testing whether all the files are copied properly or not in to the corresponding folders.

2. Sanity Testing: Testing the basic functionality of the appln.