After the coding is completed the development team conducts 
the n-unit testing by executing the N-unit test cases.If 
all the test cases were passed they will give build to the 
testing team through mail.

As soon as testing team gets the build tester conducts the 
SMOKE TESTING.i.e conducting the testing whether the build 
is ready for the further levels of testing.If the smoke 
testing passes testing team will conduct the functionality 
testing of performance testing based on the test plan.

If the Smoke testing fails testing team rejects the build 
by mentioning that smoke testing was failed.

You need to educate yourself Ranjith, answer using right 
terminologies of software testing so that you leave no room 
for further question:

Lead or Feature set lead or Module lead or Project lead 
will provide the Build release team (BRT)  with the files 
to be used for making a build. The BRT makes the build and 
gives it back to Development team, the builds goes through 
several rounds of alpha testing (which includes unit 
testing) based on the Test cases (they are influenced by 
the TC's of Quality Testing team). Once the build passes 
the alpha testing (n rounds) then the build files are 
provided back to BRT with fixes and then the BRT creates a 
new Beta build to be forwarded to the Testing team along 
with the release build notes (which carries information on 
the bug fixes/patches/quick fixes/product components 
version numbers etc). Testing team performs the 
Smoke/Sanity test on the Beta build and verifies whether 
the major functionalities are working or not so that they 
can send the build approval mail saying that "the build is 
accepted/rejected due to X bugs (with priorit/severity)". 
If the build is approved for further testing then the bugs 
mentioned in the release build notes are validated and 
finally after the testing completion (this includes test 
strategy as per test plan, for e.g, Functional, regression, 
adhoc testing etc..) the testing completion report of the 
Beta build is sent.