Vika

• May 8th, 2006

 

hi

when an application come for testing, first of all we will do the sanity testing and after that we go for the further testing. if our appliction's maimn functionality is working fine then we can go for further testings otherwise no need to go ahead.

Vikas gupta

• May 8th, 2006

 

hi

when an application come for testing then first of all we will do sanity testing. if our application's main functionality is running fine then we will move on further testing.

R.Jayakumar

• May 8th, 2006

 

When the application is given first it is done for sanity,it is done to check each and every functionality of the application before going into indepth testing.This is performed by developers before putting the file into testing enviroment.After that we need to check for smoke testing,system testing,end to end testing.

Hema

• May 9th, 2006

 

Hi. When the build comes for the testing, first we are conducting the smoke or sanity testing. This is to test the basic functionality of the build. The build is returned to the developer if the smoke or sanity testing fails. We should not report to the bug tracking tool, if a bug is found in smoke testing, rather the build is rejected.

kalyani

• May 16th, 2006

 

when test engineers  recieve application from developers first  they conduct sanity testing for finding stability of the build.if any mismatches are found they send back to the development team. After recieveing stable build from developers they start remaining levels of testing.

Sujatars

 Profile Answers by Sujatars 

• Aug 15th, 2007

 

First we do is the sanity testing (build acceptance testing) whether the major functionality is working & not causing any crashes so that further detailed?testing can be performed.

nkamuni_mca

 Profile Answers by nkamuni_mca Questions by nkamuni_mca

• Jan 14th, 2009

 

The following is the series of tests which an application goes through...
1. Unit testing (Develpers/ programers)
2.Smoke testing
3. GUI testing
4. Functional testing
5. Regression testing
6. Enviornment testing
7. Performance testing
8. User acceptability testing

Regards,
Narin Kamuni

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Mar 2nd, 2009

 

Once a new build is released, testing team needs to accept the build, for the same test team will verify whether the basic functionality is working fine or not so that they can do further testing, this type of testing is nothing but smoke testing, as a part of smoke testing, Test team will prepare a checklist and while executing smoke testing all the checklist should be passed then only testing team will accept the build and then go further for doing detailed testing.

few example check list's for any email account:

is the site opening with the given URL
am i able to Log on with the valid values
am i able to view the emails
am i able to add single or multiple email addresses to send an email
am i able to write the content
am i able to attach a file
am i able to send a mail
am i able to delete an email
am i able to signout from mail account

sunnyRock

 Profile Answers by sunnyRock 

• Sep 30th, 2009

 

When an application come for testing, Tester will do one round of sanity (Top to Bottom). If there are no SHOW stoppers, Tester will procced with Functional Testing, GUI Testing.
Before giving build to Testing Team, Build Taker will do smoke Test.