dusari

 Profile Answers by dusari Questions by dusari

• Jan 30th, 2006

 

Sanity Testing:  Teswt Engineer cover basic functionality of the buld to validate " whether the build is stable for complete testing or not"

Smoke Testing: It is an extra shakeup in sanity process.

In this tesing, testing team rejects build with specific reasons where that build is not working

Prasad Meduri

• Feb 14th, 2006

 

sanity testing is an Initial effort to check whether the application can be tested further without any interruption. Basic gui functionality,connectivity to database are concentrated here.

Smoke Testing:Its confusing question and answer too.

It covers most crucial functions of the application..

testing carried out check whether most crucial functions of the application work fine or not? dont bother about the in-depth coverage of each testset. 

what are most crucial functions in the build, you should know it before coming to testing phase. or your manager will write a seperate high-level testcase for that.

got it

if you are not clear, kindly let me know

Anitha

• Feb 21st, 2006

 

Sanity Testing:-Tester conducts the Sanity test to ensure the stability of the application build.Tester finds weather the application build is stable for complete application or not.

Smoke Testing:-It covers the major functionality of the application without bothering with finer details.

kiran kumar Racherla

• Feb 21st, 2006

 

Conceptually Smoke testing and sanity testing both are same,but perceptionally these are different.Smoke testing:Smoke testing is conducted with negative perception,it is the testing in which all the functionaliteis are avaliable are not is tested , to proceed for further overall testing.Sanity testing: This is also test for to check whether all the functionaliteis are available are not.But this testing is conducted with positive perception.

sabitha

• Mar 16th, 2006

 

After receiving initial build test engineers concentrate on basic functionality of that build to estimate stability for complete testing, in sanity testing T.E tries to execute all Po test cases to cover basis functionality.if functionality is not working/missing testing team rejects that build.if tester decided stability then they concentrate on test execution of all test cases to detect defects.

suresh k

• Jul 7th, 2006

 

Technical jargon might differ among the software organizations. But, the aim of the two methodologies is same i.e., to verify a build with limited no. of test cases.

lavanya

• Oct 10th, 2006

 

	Smoke	Sanity
1	Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke.  In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.	A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
2	A smoke test is scripted--either using a written set of tests or an automated test	A sanity test is usually unscripted.
3	A Smoke test is designed to touch every part of the application in a cursory way. It's is shallow and wide.	A Sanity test is used to determine a small section of the application is still working after a minor change.
4	Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not bothering with finer details. (Such as build verification).	Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
5	Smoke testing is normal health check up to a build of an application before taking it to testing in depth.	sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

stella

• Nov 10th, 2006

 

I dont understand the correct answer of this question. Kindly explain me with some example. then send me some example for testcase for unit testing, integration testing and system testing.

Then tell me for what are types of testing we write test cases

valan

• Dec 4th, 2006

 

Smoke Testing:

    Check the basic functionalities to ensure the stabily of the product for

further level of testing(new build).

Sanity Testing:

   Its a part of regression testing.Check the old build to ensure that all the

issues were fixed in the bug fix stage and there were no new issues raised

because of the bug fix.Its basically deep level of testing on particular

functioanlity.

srinivasracha

 Profile Answers by srinivasracha 

• Jan 19th, 2007

 

Sanity testing or Build verification test(BVT):- Whenever we receive abuild from development team the basic features of the application is tested to verify the stability of the appication for further testing.

SMoke testing:- It is Similar like sanity test, this test is conducted to verify, are there any issues in Software, before releasing to the Test Team.

Sanity testing is done by Test engineer.

Smoke testing is done by Developer or White box engineers.

Srinivas racha

sridharan

• Mar 8th, 2007

 

Once the piece of software is developed the developers will release the new build, Tester has to do the smoke testing by checking whether all major functionalities (let's say major fuctionality A ,B, C) are working fine.This is called smoke testing.

In Sanity testing it's bit more detail testing  (let's say functionalities of A->A1, A-> A2, B->B1,C->C1 also working fine) to verify whetehr the application is developed without missing any features and developed completely. We can call it as subset of regression testing.

And for Unit testing there is no specific testcase available. It's normaly done by developers by checking all the branches, conditions and statements are working. It's similar to debuging the software.

And for Integration testing, testcases will be written based on the relationship the module has with other module.
For example a testcase TC-1  for deleting a customer will impact 2 areas in the application. Deleting customer name in module A will affect the Module C's customer details. So this testcase TC-1 can be a common test case for module A and C. I feel in this way we can write Integration testcases.

System Testing is testing the application with all combined modules.This is called by over all application testing. (Here all kind of testing will be done like Integration, functional, security, performance and etc..)

Sunkara Raju

• Apr 5th, 2007

 

Smoke Test: When a build is received, a smoke test is run to ascertain
if the build is stable and it can be considered for further testing. Smoke
testing can be done for testing the stability of any interim build. Smoke
testing can be executed for platform qualification tests.  

Sanity Testing: Once a new build is obtained with minor revisions,
instead of doing a through regression, a sanity is performed so as to ascertain
the build has indeed rectified the issues and no further issue has been
introduced by the fixes. Its generally a subset of regression testing and a
group of test cases are executed that are related with the changes made to the
app. Generally, when multiple cycles of testing are executed, sanity testing may
be done during the later cycles after through regression cycles.

cbr_666

• Apr 11th, 2007

 

smoke testing:- in smoke testing before relesing build we performe smoke testing all the functionality is working or not.

sanity testing:-after relesing setup.exe file from development team we will performe (bvt) build verification test in this majorfunctionality is working or not

sand_indigeek

• May 31st, 2007

 

Hi steela,
actually Sanity testing is done by the testing department ,to check that "is the build is in this condition to take for testing or not?"

-----
In Smoke testing the Objective is same but the difference is that This type of testing done by the RET or Developer department. mean the developing department has to check that Is our developed build is in this condition that we can deliver it to testing department or not.

hariprasad

• Jul 10th, 2007

 

* Smoke testing is main funcitonality oriented.

* Sanity testing is overal functionality oriented.

Gaurav Upadhyay

• Aug 11th, 2007

 

Can u please explain the difference with an example. Say we are testing MS Outlook. What will be the test cases related to Smoke test and which ones would be for Sanity.

siddharth

• Sep 12th, 2007

 

May I know what is negative perception and positive perception here in this context?

sudeepth

 Profile Answers by sudeepth Questions by sudeepth

• Sep 24th, 2007

 

I have a confusion on this SMOKE TESTING exactly when to do this..

nautyvenkat

 Profile Answers by nautyvenkat 

• Oct 9th, 2007

 

Can u please tell me some of the crucial functionalities that comes under smoke testing?

Shilu

• Nov 27th, 2007

 

Smoke Testing and Sanity testing is almost same testing,

Smoke Testing is done at first when a build come for testing, by just going through all the forms etc ascertain that build is ready for furthur testing.

Sanity Testing is done at last when a build going to release to client, to identify all the major functionality is working fine & its a subset of Reggression testing.

g_g226

 Profile Answers by g_g226 

• May 16th, 2008

 

Negative testing is smoke testing positive testing is Sanity - Am i Right?

Smita_das

 Profile Answers by Smita_das 

• May 19th, 2008

 

A software smoke test determines whether the program launches and whether its interfaces are accessible and responsible (for example, the responsiveness of a web page or an input button). If the smoke test fails, it is impossible to conduct a sanity test.
The sanity test exercises the smallest subset of application functions needed to determine whether the application logic is generally functional and correct (for example, an interest rate calculation for a financial application).

sarithapv

 Profile Answers by sarithapv 

• Apr 12th, 2010

 

Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. 

A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep

abhishekjha

 Profile Answers by abhishekjha 

• Apr 13th, 2010

 

Smoke testing is the basic testability of the software wher in it is checked to know if the software is testable or not. The basic functionalities that the software should possess and the are working properly. For example, Any web application does have a "Login" or a "Home" page link, to check if they are working properly is known as smoke testing.

Sanity testing is a kind of "Regression testing" for smoke testing results, i.e. If there are any defects found in smoke test and if the particular module is modified than it goes for Sanity testing to check if there are any side effects due to changes in that module.

ankushgupta85

 Profile Answers by ankushgupta85 

• May 31st, 2010

 

Smoke & Sanity testing are same just to check basic functionality of application. They are used to verify the stability of new build or application, build can be accepted for further testing or not.

Smoke is done before the FT (functional testing),

Sanity is done before Regression testing.

Please correct me if I am wrong.

smiriyala

 Profile Answers by smiriyala 

• Aug 5th, 2010

 

As per my understanding, smoke test will be done by developer before they release the build to QA, its a kind of unit testing and sanity testing is to ensure that the primary test case for which the fix provided is not broken and is done by QA

shreethakur

 Profile Answers by shreethakur 

• Aug 6th, 2010

 

Developer does the BVT ie build verification testing but tester does the smoke testing. The test acses in both are quite simillar but BVT has lesser test access as compared to SMOKE test.

krsidhartha

 Profile Answers by krsidhartha 

• Sep 18th, 2010

 

Smoke Testing: The testing process where on overall system is tested for its major functionality as well as its initial starting prcess of the system that whether it is in testable condition or not. Smoke testing is also done in negative sense for the whole equipments major functionality.

Sanity Testing: The testing process in which the all functionality of  entire system is tested in positive sense that whether the all requirements are meeting.

fabhijeet1980

 Profile Answers by fabhijeet1980 

• Jun 25th, 2011

 

Hi Friend,

I am enlisting some differences between Smoke testing & Sanity Testing.

1.We do Smoke testing to confirm that recently deployed build is ready for further testing or not. This is a wider approach in which tester touches all areas of software without getting into deep.

1. We do Sanity testing to confirm that build with minor changes is working fine or not. For this tester need not to touch all areas of software but needs to be Focus on Small area of function under build where changes have done. For this tester needs to do Narrow Regression testing to find out impact of minor changes in build.

2. Smoke testing can be done by Manual or automated Test Scripts/Cases.

2. Sanity Testing is usually done without Test Scripts/Cases.

3. Smoke testing is done to ensure that most crucial function of application working fine but it does not bother about minor changes.

3. Sanity testing is done to ensure application is working in accordance to specification after minor changes are done in build. It is subset of regression testing.

karthik

• Jul 15th, 2011

 

Smoke testing is a testing,which is mainly doing for whether the application will be working or not but the Sanity

testing is little but different,it is checking entire part of the application given by SRS.....

karthik

• Jul 15th, 2011

 

Smoke testing is a testing,which is mainly doing for whether the application will be working or not but the Sanity.
testing is little but different,it is checking entire part of the application given by SRS.

Masthan

• Jul 23rd, 2011

 

Hi,
Your concept is not correct.....
As Per my knowledge
Smoke Test:
When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing. Smoke testing can be done for testing the stability of any interim build.Smoke testing can be executed for platform qualification tests.

Sanity testing:
Once a new build is obtained with minor revisions, instead of doing a through regression, a sanity is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a subset of regression testing and a group of test cases are executed that are related with the changes made to the app.

sivananda.uppaluri

• Dec 15th, 2011

 

SMOKE TESTING:

* Smoke testing originated in the hardware testing practice of turning on a new piece of hardware for the first time and considering it a success if it does not catch fire and smoke. In software industry, smoke testing is a shallow and wide approach whereby all areas of the application without getting into too deep, is tested.
* A smoke test is scripted, either using a written set of tests or an automated test
* A Smoke test is designed to touch every part of the application in a cursory way. It’s shallow and wide.
* Smoke testing is conducted to ensure whether the most crucial functions of a program are working, but not bothering with finer details. (Such as build verification).
* Smoke testing is normal health check up to a build of an application before taking it to testing in depth.

SANITY TESTING:

* A sanity test is a narrow regression test that focuses on one or a few areas of functionality. Sanity testing is usually narrow and deep.
* A sanity test is usually unscripted.
* A Sanity test is used to determine a small section of the application is still working after a minor change.
* Sanity testing is a cursory testing, it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing.
* Sanity testing is to verify whether requirements are met or not, checking all features breadth-first.

vidhya

• Jan 25th, 2012

 

Smoke testing is the random testing, it is done to check the important scenario in the project

anand kiran

• Mar 11th, 2012

 

Smoke testing:it is using developers before release defect fixed note to testing team.Once check him/her self defect fixing correctly or not any side effects will come this is called smoke testing

Sanity testing:it is using testing team before applying or conducting real testing to check or verify weather initial build testable or not.We have to test main functionality this process operate test lead along with selected testers in one cabin this is called sanity testing.

mfsi_satyakamm

 Profile Answers by mfsi_satyakamm 

• Mar 26th, 2012

 

Smoke Test:
When any build is recieved, a smoke testing is first done to ensure that the build is stable or not.
If the build is stable then it is further tested else there is no point of testing.

Sanity Testing:
Once we get a new build or new version of a build, it is first checked that whether the bugs in the previous build are fixed in this new build or not, and whether due to fixing of certain issues any new issues are introduced into the build or not ? It is a subset of regression testing.

Dillip Palai

• Apr 19th, 2012

 

Smoke Test:

When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing.

Smoke testing can be done for testing the stability of any interim build.

Smoke testing can be executed for platform qualification tests.

Sanity testing:

Once a new build is obtained with minor revisions, instead of doing a through regression, a sanity is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a subset of regression testing and a group of test cases are executed that are related with the changes made to the app.

pavan kumar jvs

• Apr 20th, 2012

 

Sanity testing means developer to finish developing the software tester to test the software whether it can properly developed or not.it is called sanity testing.

smoke testing means:-before send the build to maintenance team finely to test the positive testing that is called smoke testing.

Ramasubbu

• Aug 2nd, 2014

 

Smoke testing: Testing the critical functionality of the application using high level test cases and check whether the application is ready for further testing(General health checkup)

Sanity Testing: Before release of an application test the major functionality without test cases and also check whether new functionality added to the application affect any other functionality(specialized health checkup)

Anonymous

• Dec 14th, 2014

 

Please make sure you know what actually it is.. Don't misguide.. sanity testing is like a narrow regression testing, usually done after a builds are deployed (After bug fixes) to make sure functionality is still correct.