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.

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

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

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.

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.

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

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

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

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.

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

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.

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..)

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.

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
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.

* Smoke testing is main funcitonality oriented.

* Sanity testing is overal functionality oriented.

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.
May I know what is negative perception and positive perception here in this context?

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 Regression testing.

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.

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

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).

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

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.

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.

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

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.

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.

I have gathered a few points about the difference between smoke and sanity testing
from the responses of two software testing groups. I have added the points below.

However, my experience of executing the Smoke and Sanity testing has been the
following:

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.

Smoke Sanity
Smoke testing originated in the hardwareA sanity test is a narrow regression test
1 testing practice of turning on a new piece ofthat focuses on one or a few areas of
hardware for the first time and considering itfunctionality. Sanity testing is usually
a success if it does not catch fire andnarrow and deep.
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.
2 A smoke test is scripted--either using aA sanity test is usually unscripted.
written set of tests or an automated test
3 A Smoke test is designed to touch every partA Sanity test is used to determine a small
of the application in a cursory way. It's is section of the application is still working
shallow and wide. after a minor change.
4 Smoke testing will be conducted to ensureSanity testing is a cursory testing; it is
whether the most crucial functions of aperformed whenever a cursory testing is
program work, but not bothering with finersufficient to prove the application is
details. (Such as build verification). functioning according to specifications.
This level of testing is a subset of
regression testing.
5 Smoke testing is normal health check up to asanity testing is to verify whether
build of an application before taking it torequirements are met or not,
testing in depth. checking all features breadth-first.

One of Right definition in whole search/help site.

subset of regression testing ??

After regression testing there is no need of sanity testing

it is only done to avoid regression testing at the final stages
of Build received, it is assumed that build is working fine
just for tester satisfaction and short time available, going through whole build we follow those test cases only
where
bugs were found in previous build, it is assumed that while fixing the bug the developer has not disturbed
any other part of code/build.

Thanks for proper definition, I am including accordingly in my test plan.

Sanity testing is not subset of regression testing its a next testing strategy, ofcourse defined by testers
themselves for there satisfaction, testers are always after deadline and they have to follow this stage instead
of going for a regression testing again.
sanity is a different test strategy to Regression all together, but by "Subset" of regression testing, I meant
generally the test cases that are executed for sanity are selected from Regression test cases only. As the
test cases are derived from Regression (in most cases), its thus a subset of regression.

I second that sanity is done instead of a regression in general.

Test cases for sanity are predefined, u can't say that u will not follow those test cases which r not yet
executed in Regression testing.

Selection of test cases for Sanity can't be dependent on Regression testing, aim of Sanity is only to test
whole module with minimum number of testcases and if we are aware of important portion of module where
severity of bugs can be high we include those test cases also.

Yes, the test cases are always predefined and sanity is planned beforehand, am referring to slection of test
cases here. Usually the test cases are derived from the already written test cases (my experience). Thus,
sanity has no dependency to regression, but the test cases are generally same as regression, with they are
only a choosen few affecting the areas/modules to be covered. But I dont rule out that separate test cases
can also be written alltogether aiming sanity testing only. That depends on the practice and strategy.

Both of u r are arguing on same similar experiences,

ur words are same.
But generally we don't write separate test cases for any of the testing, its written once and for all, adding test
cases is again new strategy of testing called TEST METRICS.

smoke is done on build version and sanity is done on release version. do you agree friends? 10/9/2004 5:05
PM |Narayana reddy, DKDS Naidu

___________________________________________

Can we say that smoke test is the preliminary testing step before the actual testing start? if yes then smoke
test is a Light way of testing the software.

Thanks for the

Nice definition for smoke test and sanity testing. 10/26/2004 11:05 AM | Ali Anfal Mohammed

Hi all,

Can any anybody tell me

What is piolet testing ?

Thanks & Regards

Ramappa Nashi 11/9/2004 8:12 AM | Ramappa

____________________________________________ ____________________
________________________

Hi all,

It is always the B.A. involved for both smoke/sanity testing especially in a RUP based environment.

What if a tester is told out of blue to smoke an AUT without having no idea about the functionality of that
AUT. In such cases what input documents should be available to him ??

Can any body give me an approach?

Appreciate your understanding,
Thanks,
Pranay D. 11/29/2004 4:11 PM | Pranay Dalal
Hi All,

The topic erases any doubts about sanity and smoke testing.

When it comes to Selection of test cases.It is always to pick from the existing testcases written(but updated
as needed), which seem to be more appropriate for section of software to test. At times we will not need to
run all the testcases written for the section.

Thanks & Regards

RaviReddy 12/7/2004 9:16 AM | Ravi Kumar Reddy N

____________________________________________ ____________________
________________________

Is there any diffrence between Functional and Sanity Testing?????????? 12/11/2004 10:15 AM
| Narasimha Rao.P

____________________________________________ ____________________
________________________

As per my knowledge ,

Smoke is to test the Basic Functionality of the Application,i.e prior to Indeapth testing.

Sanity Testing is to ensure that the bugs which are found during the Previous build are resolved. 12/11/2004
9:22 AM |Narasimha Rao.P

____________________________________________ ____________________
________________________

Thanks for the

Nice definition for smoke test and sanity testing 12/13/2004 7:46 AM | Suman

____________________________________________ testcase vs test script

thanks for the clarification between smoke and sanity testing

3/5/2005 7:47 PM | madhu

____________________________________________ ____________________
________________________

Hi all,
Smoke testing is the first testing to be performed on the build before tester take it for further testing.
So it is done on build level n it is used to check the basic functionality of the product.

Sanity testing on the other hand is done at later stage. It is done at module level. Sanity is done to check the
depth functionality of the product after modification.

So don't get confused with sanity n regression. 4/7/2005 9:03 AM | vikas kumar gupta

____________________________________________ ____________________
________________________

what are the points we consider in smoke testing..and what in sanity 4/16/2005 3:40 PM | suresh

____________________________________________ ____________________
________________________

Sanity testing u can do it if product is in development phase ,if software is in market n clients r using the
software then u have to use smoke testing so that to reduce the risk analysis 4/22/2005 10:55 AM | Rahul

____________________________________________ ____________________
________________________

Hi
what are the points we consider in smoke testing..and what in sanity

Thanks
satyendra 4/22/2005 6:45 PM | satyendra

____________________________________________ ____________________
________________________

Hi
i think after regration testing no need sanity testing.
becacuse regration testing is compleate the all testing application. 4/22/2005 6:47 PM | satyendra

____________________________________________ ____________________
________________________

All of the people are not compromising about one defination.this is bad. 6/15/2005 2:22 PM | sridhar taduri

____________________________________________ ____________________
________________________

Smoke and Sanity are similar test which are done at two different stages and bith have same importance.
Smoke test is done while giving internal release to QC for fullfledge testing and sanity is done as part of
regression testing at last stages at the time of Release to UAT 11/2/2005 6:51 AM | Kishore Malladi

____________________________________________ ____________________
________________________
Hi - Above discussion seems giving rich information. Let me also explain my knowledge.

Smoke Testing term has come from electronic industry. It is a rudimentary form of testing applied to
electronic equipment following repair or reconfiguration, in which power is applied and the tester checks for
sparks, smoke, or other dramatic signs of fundamental failure.
2. By extension, the first run of a piece of software after construction or a critical change.

People give different names to such testing activity in different industries. Sanity testing is the term used in
Software which is very much similar to Smoke testing. after going through the above discussion and Smoke
testing definition we can say

Smoke Testing - At build level when the software is just built and came for testing

Sanity Testing: At release level when software is ready to be shipped to client and QA just want to finally
chekc if evthing is fine

Best Regards,
Piyush Sharma
11/24/2005 3:03 AM | Piyush Sharma - Pune

____________________________________________ ____________________
________________________

Smoke test is actually concept came from the Electronic industry.In the software Testing, Smoke testing is
done by opening all the pages or modules for checking whether they are opening or not after build is
installed.

Sanity is similar to the Smoke Testing but, in depth testing is done for the impact areas (Changes or
modifications) in the New build 12/14/2005 7:09 AM | Preetham Boosnur

____________________________________________ ____________________
________________________

Hi Devankur,

Such a great defn. thankyou

have a lovely day! 1/24/2006 1:14 AM | Manivel Khanna R

____________________________________________ ____________________
________________________

Hi Devankur,

Please can you provide scenarios and examples of Smoke and Sanity testing.

Thanks and Regards,

Mangalmurti 2/8/2006 3:51 AM | Mangalmurti - Hyd
____________________________________________ ____________________
________________________

Hi devankur,
Can you please tekll me that if we conduct sanity testing as substitute to regression testing.we are keeping
some space for bugs in software. 2/21/2006 9:50 AM | Abhijit -Mumbai

____________________________________________ data base test

How to test runtime database check point using winrunner.

If anybody can do favor by answering the querry , it would be great full to me 3/2/2006 7:50 AM | hemanth

____________________________________________ What r the six points of

web testing?

Hi All,

Plz describe above Que......... 3/7/2006 5:30 AM | Prashant Singh

____________________________________________ ____________________
________________________

Sanity is a first level of testing when an application is given to QC(Testing) where they check first round
functional testing then they go for ful fledge of testing.if they are not happy with sanity test ,will send back to
development.
Smoke Test is done as last level of testing in QC(Testing) i.e. done at a time of release of an
application.Thanks....3/18/2006 12:25 PM | Kishore Malladi

____________________________________________ ____________________
________________________

Can anyone provide me a correct definition of stress testing.................? 3/18/2006 12:28 PM | Malladi

____________________________________________ ____________________
________________________

Hi,
Thanks for explaining. I understood somewhat both, but still not clear. That is confusion about on what basis
we have to make choice them i.e. When to use what?. Is there any dependancy between them? By
observing above I found that everyone explained by their view. That's ok.
Could sombody explain both of testing types (and regression also) with short example so that everyone get
the clear view.

Regards
Pravin.

3/21/2006 3:59 AM | Pravin Savant- Pune

____________________________________________ SMOKE Vs SANITY

Are they Similar or Different ? Then What is Compliance Testing, Mutation Testing And Localization
Testing ? 3/28/2006 3:22 PM | Rupayan

____________________________________________ ____________________
________________________

Hi
I am extremely glad to get the differences between the both.I have been looking out for the differences for a
long time,finally I have got the required answer.

Thank you
Daly 4/11/2006 3:53 AM | Daly Sunil

____________________________________________ ____________________
________________________

may i know the difference between compatibility and configuration testing?

4/24/2006 5:44 AM | sadiq

____________________________________________ ____________________
________________________

Hi Piyush,

Yes you are absolutely right. Smoke testing shoud be done in initial stages of build, but it should be formal. I
mean test cases for conducting smoke testing should be consistant, where as incase of sanity its happens at
release stage with informal. Means, basic steps which ensure the major flow of the application. Focus
should be at critical areas.

Thanks
Niranjan 4/30/2006 5:36 AM | Niranjan Veluru

____________________________________________ ____________________
________________________

thanx for giving such a valueble definition. 5/8/2006 3:47 AM | somesh chitta

____________________________________________ ____________________
________________________

Hi all,This has now became a lot confusion. 5/10/2006 3:35 AM | vikas

____________________________________________ ____________________
________________________
Vikas, I agree with you. This thread has indeed become confusing. As confusing as most of the concepts in
the arena of software testing. Most of the definitions are tailored or doctored to suit individual or
organisational needs. We still need a body to set de facto testing standards in the software
industry. 5/10/2006 11:15 AM | Hemant

____________________________________________ ____________________
________________________

Difference between smoke and sanity testing:

Sanity testing refers to a set of tests that validate a build's stability, and the availability of major components
of the product. The tests will be run on every build used by QA, are automated, and are generally run on a
daily basis. Each major new feature defined within the project PRD must be represented by one or more test
cases in the Sanity Test.

If a project is driven based on Pass I, Pass II and Pass III where Pass II will be called as comprehensive
pass and Pass III will be called as Sanity Pass. In the Sanity (Final) Pass only the bugs got fixed after the
comprehensive pass will be tested and a formal regression will be done with respect to the bug fix. Apart
from this, testing would be performed on the major functionalities of the product to confirm that the final code
has not broken any other functionalities which where working before.

AND

Smoke testing refers to a set of tests that validates basic functionality across a feature set. Often referred to
as CRUD tests (Create, Read, Update and Delete), these tests are intended to validate most basic "go-
paths" within the code. Smoke tests should cover core or legacy functionality as well new features for the
project. Smoke tests are generally run following Sanity Tests and are more thorough in scope.
5/15/2006 1:54 AM | Kumar Nagireddi

____________________________________________ ____________________
________________________

hi
Smoke testing is done when our project is at build level to test only major functionality.

sanity testing is done when ur project at releasing level to test software after some changes to test if that has
any effect on other component of software. It is part of regression testing. 5/25/2006 9:54 AM | vikram

____________________________________________ ____________________
________________________

thanks for definition for easy undersating words used 6/6/2006 3:24 PM | d.senthil kumaran

____________________________________________ ____________________
________________________

Hi Devankur,

Your Difference for SMOKE Vs SANITY is PERFECT. NO DOUBT. All points can clearly differentiate both
the things. Nothing is missing in your difference.

Thanks for provinding such a nice information.

Thanks and Regards,

Atul Hendre 8/1/2006 8:42 AM | Atul Hendre

____________________________________________ ____________________
________________________

Smoke testing is cursory testing of the major functionalities of the program.whereas sanity testing is in depth
testing module wise to ascertain that the module is fuctioning properly after resolving the bugs. 8/27/2006
4:52 AM | Sandeep Bhattacharya

____________________________________________ Bench mark and

Baseline

what is the difference between bench mark and base line in the quality. 8/29/2006 9:55 AM | Sandhya Rani

____________________________________________ ____________________
________________________

Hello,

This one –

“Sanity testing is to verify whether requirements are met or not, checking all features breadth-first. ”

is true for smoke testing…right? Since sanity is “narrow and deep” it cannot happen “breadth-first” or “all”.

Also ____________________________________________4 says –

“Smoke testing will be conducted to ensure whether the most crucial functions of a program work, but not
bothering with finer details”

if smoke testing is “shallow and wide”, how is this applicable for “most crucial functions”.

I might be wrong in my understanding. Please clarify further.

Indrajit Ghatak
Manager – Testing & Support
Web Spiders
http://www.webspiders.com
9/6/2006 5:44 PM | Indrajit Ghatak

____________________________________________ ____________________
________________________
Smoke test : It is a basic test (application stability) is to be conducted whenever a new build is received for
testing. We can call it as build verification test. If it passes, then we go for further level of indepth testing.

Sanity Testing : This test is conducted at the final release of the software before delevered to the customet
for UAT testing.This ensures that the flow of the application and major or critical functionality is working as
expected. 9/22/2006 12:57 PM | Peter

____________________________________________ ____________________
________________________

hi!
i don know what r u all giving about sanity and smoke testing. see my views and comment on it.
smoke test: why? bcoz we have to test a bulid that should meet its basic functionalities specified on functinal
specification document.let we have a new build for testing with 12 basic functionalities given on doc but
when u start testing the sixth or any functionality given in doc is not supported or working then u can say
smoke test failed otherwise ur build pass smoke and u can do further testing on it.eg. if y give user name
and password to yahoo login and it do nothing but in ur FS doc it is mentioned that it will open next window
or allow access withthat data than ur smoke test is fail and u have to send your build back.
Sanity: Where as sanity testing is a cursory testing means u have test whole build for once to show that its
working as per give specification.we can say sanity is on pass testing. 9/24/2006 3:50 PM | rampy

____________________________________________ ____________________
________________________

(As per experience and knoledge so comments welcome)

Smoke testing:
Once the application biuld intially we go for smoke testing how the application behaves with different
hadware settup (weather working in different environments).if the system crash happens while testing the
smoke test test casaes then the smoke test fails else pass.

Sanity testing:
once the module finishes we going for sanity testing .i.e in deapth with all the functionalities.so here sanity
testing will be regression testing but regression testing wont be sanity testing.

Note: sanity testing is nessasary to confirm the module build in right way. 10/13/2006 8:43 PM | Thanasingh

____________________________________________ ____________________
________________________

what leve of testing regression testimng can be applied 10/28/2006 4:36 AM | sangamesh

____________________________________________ ____________________
________________________

Benchmarking:
Comparing your company’s products, services, or processes against best
practices, or competitive practices, to help define superior performance of a
product, service, or support process.

Baseline:
A quantitative measure of the current level of performance.

Thanks and Regards

Kumar Nagireddi

11/14/2006 9:35 AM | Kumar Nagireddi

____________________________________________ ____________________
________________________

smoke testing is perform to check all functionality is working before testing the test case 12/6/2006 10:57
AM | ankur tyagi

____________________________________________ ____________________
________________________

can any body tell me difference b/w retesting and regression testing?
Mail id-
tyagi_anki@yahoo.co.in 12/6/2006 11:00 AM | ankur tyagi

____________________________________________ ____________________
________________________

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

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.
3/5/2007 12:14 PM | soubhagya

____________________________________________ ____________________
________________________

thanks for clarifying the differencebetween smoke and sanity testing..

while smoke testing is a build verification test to check the stability of the build and it is conducted when a
build is released to the QC for testing, sanity testing is a part of the regression testing to check a or few
functionality of the applicaton are functioning according to the requirements or not after bug fixing and it is
conducted at the time of final release to the customer 4/29/2007 12:49 PM | swathi

____________________________________________ ____________________
________________________

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.

5/9/2007 1:13 AM | sandeep patil

____________________________________________ ____________________
________________________
Smoke testing is also know as non-exhaustive testing. This originated in the fire-fighting industry as a test to
see whether firemen could breathe in new equipment when there was a fire and smoke. 5/22/2007 3:33 PM
| Turbografx

____________________________________________ ____________________
________________________

Sanity Test : Initial test for every build to test its basic functionality.
Smoke Testing : Testing done at the end of every module to test the functionality of the current build to older
one.5/27/2007 9:06 AM | sonali

____________________________________________ ____________________
________________________

Smoke Testing:

Testing done to ascertain that s/w build is stable prior to normal testing life cycle.

Eg. While testing an application, showstopper bug arises developers fix that & releases a new build of
that application for testers to retest. So, testers normally will run a scenario ( called as health check scenario
) to check whether all intermediate components are working fine

Sanity Testing:

Testing done only after smoke testing. Its not an exhaustive testing. Its a regression testing done to
ascertain specific task of a functionality in an application
5/30/2007 3:51 AM | Mohideen

____________________________________________ ____________________
________________________

Hi,
Smoke Testing:
Build is properly installed on one or more system for further testing.

Sanity Testing:
Testing of database connectivity with application, connectivity with server and open each module of the
applicaiton for further testing. 6/25/2007 7:38 AM | Deep

____________________________________________ ____________________
________________________

Hi,

Smoke testing is conducted in positive perception and where as Sanity testing is conducted in negative
perception.
6/29/2007 5:16 AM | Suresh
____________________________________________ ____________________
________________________

Now i understood abt smoke Vs Sanity....can any body tell me .. what is difference between exploratory and
adhoc testing? 7/5/2007 5:28 AM | Suji

____________________________________________ ____________________
________________________

I thank you for explaining the basic concepts of sanity testing and smoke testing. I was facing problems at
interviews.
my mailid is rajivlochanpanda@gmail.com. I am from Rajiv Panda 7/10/2007 9:33 AM | rajiv lochan panda

____________________________________________ Define Alpha Beta

Testing with Eg

Plz. Define Alpha beta testing precise and in simple words 7/23/2007 3:20 AM | Pravin Kadam

____________________________________________ re: alpha / beta

Alpha testing is done basically at the developers site. Where in developers look over shoulders of the users
to find out the problems faced by the users of the product.

Whereas beta testing is done at the customers end or the client end where the clients record all the
problems faced by them and later send the copies to the developer of the product for rectification.
7/26/2007 1:14 AM | matt

____________________________________________ ____________________
________________________

Hi Every Body,

Smoke Testing can be done in view of Environment- whether the environment is stable after installing or
running the new build on any environment for majar testing effort.

Once the build is working fine with the specified environment then we can say Smoke test is pass and we
can go for further testing.

Sanity Testing can be done in view of application- Whether the build is stable with any environment and we
will have an understanding of the flow of Build with major functionalities.

So both Testing are very similar and we can say these both are cousins.

Diffrent companies calls as Smoke or Sanity or BVT. But all are same.

Sobhan Jaliparthi. 7/27/2007 9:13 PM | Sobhan J

____________________________________________ ____________________
________________________

smoke: It covers the all major functionality of the application without bothering with the finer detail.
Sanity: If any buld is receive from the developement them we will check the build is stable for entire
application as well as it will be ready for further testng. 7/30/2007 5:01 AM | Mudit

____________________________________________ Stress Testing

Hi All

I understad for the Stress means just to check the Peak value of the application .

that it 7/31/2007 4:19 AM | Lokesh Thakre

____________________________________________ ____________________
________________________

In the above where u explained smoke and sanity,there u explained smoke is the first level of testing then
we do sanity

But in the feedback section it is explained like sanity is the first level of testing then we do smoke,

So all this is soo confusing...

PLZ explain whether smoke iis first level os sanity 8/7/2007 6:34 AM | Manisha bazaz

____________________________________________ ____________________
________________________

thank you 8/7/2007 10:57 AM | murugan.pm

____________________________________________ ____________________
________________________

Now i understood abt smoke Vs Sanity 8/9/2007 7:26 AM | Ashok

____________________________________________ ____________________
________________________

looks good and helpful.Thanks for taking time and presenting your points in-detailed. 8/14/2007 6:52 PM
| Reddy

____________________________________________ ____________________
________________________

can u give me an example cleary to differenciate smoke and sanity testing. 8/21/2007 3:45 AM | shanthi
____________________________________________ ____________________
________________________

This is agreat piece of explanation. 8/22/2007 4:53 AM | Solomon

____________________________________________ ____________________
________________________

Thankz a lot

Very brief and to the point.

Good to understand and chewable too.
8/27/2007 4:16 AM | Prashant Tyagi

____________________________________________ ____________________
________________________

SomkeTesting:It is main Functionality oriented.

Build is properly installed on one or more system for further testing.

SanityTesting:It is Overall Functionality oriented.Weather intial ceck for covered all the functions or
not 10/30/2007 7:57 AM | prabakaran jeyamtechnologies

____________________________________________ ____________________
________________________

Hi Devankur,
That was really very good information. 11/21/2007 3:44 AM | Niraj

____________________________________________ ____________________
________________________

Hi all,

can any body tell me the difference between functional testing and Coverage testing?

11/30/2007 5:37 AM | Yogini

____________________________________________ Functional testing &

Coverage Testing

Hi all,

can any body tell me the difference between functional testing and Coverage testing? 11/30/2007 5:39 AM
| Yogini

____________________________________________ ____________________
________________________
Can you pls tell me when to perform sanity testing ang when smoke?
becoz some of you are saying that smoke is release time testing and some are saying sanity is release time
testing.
ths is creating a lot of confusion.
Regards
Vikas 12/12/2007 2:09 PM | vikas

____________________________________________ ____________________
________________________

can cany one please explain do we need to write seperate test cases for smoke and sanity
testing? 12/26/2007 11:55 PM | Sathish M

____________________________________________ ____________________
________________________

very nice.thank you. 12/27/2007 1:49 AM | ramana

____________________________________________ ____________________
________________________

Hi friends,

Can anybody give an answer to my question -

Is Smoke and Sanity testing are same, there is not any difference inbetween these two?

Thanks and Regards

Ashwin 1/2/2008 6:15 AM | Ashwin

____________________________________________ ____________________
________________________

Hi All,
Thanks to all of you for sharing so many views about SMOKE and SANITY testing terms.

Let me try to explain it in very Lehman terms here.

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 major functionalities
work fine or not is tested , to proceed for further overall testing. This is done for a new build.

Eg. You have a flight booking application to test. Here, the smoke tests can include the tests such as:

Are you able to go to the booking screen?

Are you able to search a flight?
Are you able to enter the flight information successfully?
Are you able to transact successfully?
Is the flight really booked or the application just shows the success message?

If these tests do not pass, meaning its not worth applying time and cost in testing further finer details and the
build is sent back and reported as unstable.

Sanity testing:
This is also a test to check whether all the functionaliteis are available are not.But this testing is conducted
with positive perception.
Sanity means, the quality or condition of being sane/healthy.
I do not deny the fact that it is a subset of regression. Also, these tests are executed before the
application/build is actually released.

Please let me know in case of any confusions.

Regards,
Ankit Vaish 1/11/2008 7:30 AM | Ankit

____________________________________________ ____________________
________________________

Hi all

I think mr Ankit is absulately right.+ve perception and -ve perception are only difference between smoke and
sanity testing, otherwise both are same

regards
Sunilkumar 1/13/2008 11:57 PM | Sunilkumar A H

____________________________________________ ____________________
________________________

Folks,
Lot of people are asking difference between Smoke and Sanity testing. And the more info you get, more
confused are you becoming.

Let’s make it simple …

Difference between Smoke and Sanity –

Smoke testing is done to verify that the build (to be tested) is done properly. (The build is a new / updated
version of software). The motive is to check that the application build is working fine and does not crash.

For example – say an application has following features – (say each feature has a page, so in this case
there are 10 features; so its 10 pages)
Login, Logout, Enter info, delete info, update info, Change address, search records, retire records, print
form, generate reports etc…

Here’s how you will Smoke Test it -

Check that each of the pages is displayed properly and there are no broken links between pages.
Check that the buttons on the pages are clickable (not disabled or hidden).
Check that you can traverse back and forth between pages.
Check that you can see the help section pages, legal and disclaimer section on the pages (outgoing links on
the pages)
Check the look and feel of the pages (fonts and user text boxes displayed properly and no broken images or
cluttered text or font scramble) – this is optional check unless you see something that is unreadable
Check that you are able to enter info into input boxes (no need to do any transactions; just check whether
you are able to input text on the pages or not).

Note that you are not required to do any transactions in Smoke test. In other words you are not testing the
functionality of the application but the application build itself.

Sanity Testing – is done to verify whether the new / updated build is functioning properly. (Note the
difference – smoke checks the application build; sanity checks the build functionality at higher level.)

Take the above example again – say an application has following features –
Login, Logout, Enter info, delete info, update info, Change address, search records, retire records, print
form, generate reports etc…

Here’s how you will Sanity Test it -

Check that the customer critical functionality is working by performing at least one transaction for each of the
major features.

Your depth of sanity testing depends on the functionality of the application. Say there are 5 major features of
that application. So you need to perform only one transaction for each of the feature (to verify that all the
major features are working properly).

(Sanity test concentrates on testing major features. A feature is said to be major if it is accessed by
customer frequently or daily and its working is important to the business. )

Now say the login, logout, enter info, delete info and generate records are the 5 main features on the
application.

Sanity test -
Check that you are able to login
Check the you are able to logout
Check the you are able to enter the info and save record for new user.
Check that you are able to delete data of existing user.
Check that you can generate report for current date.

You don’t need to test rest of the features. Nor do you require to run other exhaustive test cases for each of
these major features.

Note that you just have to check that the basic functioning of the major features is working. Don’t run end to
end and multiple operation test cases in sanity.
Just ran the Basic test case for which that feature is designed.

Hope that now everyone has got clear understanding of Smoke and Sanity testing. And the Difference as
Well.
Lets make it Simple…

Cheers,
Sameer K.

1/19/2008 9:13 AM | sameer kadam

____________________________________________ ____________________
________________________

Hi thanks

from just i clarified doubt about sanity and smoke testing difference. 1/29/2008 6:38 AM | Suresh

____________________________________________ ____________________
________________________

SANITY TESTING:

This is before testing. Application is stable or not, we want to write test cases for product whether
development team released build is able to conduct complete testing or not ?

SMOKE TESTING:

After testing major & medium or critical functions are closed or not
1/31/2008 4:34 AM | Murthy.Y.N

____________________________________________ ____________________
________________________

1)Smoke testing:done by developers,To ensure thet build is ready for release to the testing team.

Sanity testing:Done by QA/testers,to ensure if it's stable enough to continue further testing.

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.

2/4/2008 1:08 AM | Bibek Khatiwara

____________________________________________ ____________________
________________________
We will conduct Smoke Testing when you get a build from the developer; we will check whether all the major
functionality is working fine. Also we will check the hardware is supporting and the database connection. In
one sentence, we will check the environment for conduct testing.

During Sanity Testing we will check the Major functionality of the build/application. Not only the major
functionality, we can check the medium ware functions also.
In one sentence, we will check whether the high level requirements are satisfied during this release or not.
2/13/2008 2:31 AM | Vindhya Sajay Menni

____________________________________________ ____________________
________________________

Hats Off to your definition along with the differentional points. it was indeed very useful for me 2/15/2008
12:08 AM |archana

____________________________________________ ____________________
________________________

Difference between smoke and sanity testing:

Smoke Testing:
It is an initial type of testing, once testing team gets a build, needs to do the BVT or Smoke Testing for
verifying the major functional component of the build. This has to be done based on the requirement.

After that, the testing team would be executed the functional/Integration/System test cases.

Sanity testing:
It is also initial type of testing, once testing team gets a build, needs to do the sanity testing for verifying the
Hardware/network discrepancies on that. This will ensure that build is functioning correctly according the
business requirement without Hardware/Network Issues.

Ex: while user working on the build, every 5 minutes system gets restarted, the testing team would not
proceed the further testing. This kind of issue will be found in the sanity testing

2/27/2008 3:32 AM | Latcham Appasamy

____________________________________________ ____________________
________________________

Difference between smoke and sanity testing:

Smoke Testing:
It is an initial type of testing, once testing team gets a build, needs to do the BVT or Smoke Testing for
verifying the major functional component of the build. This has to be done based on the requirement.

After that, the testing team would be executed the functional/Integration/System test cases.
Sanity testing:
It is also initial type of testing, once testing team gets a build, needs to do the sanity testing for verifying the
Hardware/network discrepancies on that. This will ensure that build is functioning correctly according the
business requirement without Hardware/Network Issues.

Ex: while user working on the build, every 5 minutes system gets restarted, the testing team would not
proceed the further testing. This kind of issue will be found in the sanity testing
2/27/2008 3:35 AM | Latcham Appasamy

____________________________________________ ____________________
________________________

Very fantastic way explain the difference of Sanity & Smoke Testing by sameer kadam & Latcham
Appasamy 3/11/2008 5:51 AM | Pravin Fulzele, Mumbai

____________________________________________ ____________________
________________________

It is a good article. Thanks to all!! 3/17/2008 12:00 AM | Ravi

____________________________________________ ____________________
________________________

Pravin Fulzele If u dont know the difference please be patient,Dont send others hospital;and think twice
before writing any article! 4/2/2008 8:19 AM | Deviltester

____________________________________________ ____________________
________________________

"PRAVIN FUZELE,DIRTY TESTER HAVING FAKE EXPERIENCE......IF YOU DO'NT KNOW EVEN BVT
THEN HOW CAN U SAY THAT U R A TESTER ...IT'S A SAME FOR TESTING DEPARTMENT.,....JUST
GO TO HELL.." 4/2/2008 8:24 AM |MEENA KUMARI,BANGLORE

____________________________________________ ____________________
________________________

"PRAVIN FUZELE,DIRTY TESTER HAVING FAKE EXPERIENCE......!

IF YOU DO'NT KNOW EVEN BVT THEN HOW CAN U SAY THAT U R A TESTER ...IT'S A SAME FOR
TESTING COMMUNITY.,....JUST GO TO HELL.." 4/2/2008 8:27 AM | meena kumari,banglore

____________________________________________ ____________________
________________________

HEY PRAVIN.....Dont get confused....we all came to know that your are really a foolish person in this testing
community...Stay away dfrom your job.
I m not scolding you but suggesting....i won't tolerate any person having soo much patient.....! 4/2/2008 8:31
AM |rajeswari,Delhi
____________________________________________ ____________________
________________________

PRAVIN ...COOL DUDE;

YOU know what do you mean by testing.....?

Better luck next time....

First
1) read
2)Understand
3)write
4)mug up
5)think TWICE
AND THEN ONLY DISCUSS.....okay 4/2/2008 8:36 AM | archana,mumbai

____________________________________________ ____________________
________________________

Nice Devankur ..
but these are so long defination

Sort and sweet defination for SANITY TESTING is :-

Sanity testing is the minimum no. of test cases required to be passed before testing any
application :) 4/3/2008 2:48 AM | Kamlesh Shama

____________________________________________ Testing Methodologies

Objectives
Look at the various methodologies for testing software.
Learn about test-driven development.
Overview
There are numerous methodologies available for developing and testing software. The methodology you
choose depends on factors such as the nature of project, the project schedule, and resource availability.
Although most software development projects involve periodic testing, some methodologies focus on getting
the input from testing early in the cycle rather than waiting for input when a working model of the system is
ready. Those methodologies that require early test involvement have several advantages, but also involve
tradeoffs in terms of project management, schedule, customer interaction, budget, and communication
among team members. This chapter discusses how testing fits into the various software development life
cycles and then discusses the test-driven development practice in detail.

The Configuration Management Application Block (CMAB) is used to illustrate concepts in this chapter. The
requirements for the CMAB are as follows:

It provides the functionality to read and store configuration information transparently in persistent storage
media. The storage media are the Microsoft® SQL Server™ database system, the registry, and XML files.
It provides a configurable option to store the information in encrypted form and in plain text using XML
notation.
It can be used with desktop applications and with Web applications that are deployed in a Web farm.
It caches configuration information in memory to reduce cross-process communication such as reading from
any persistent medium. This caching reduces the response time of the request for configuration information.
The expiration and scavenging mechanism for the data cached in memory is similar to the cron algorithm in
UNIX.
Software Development Methodologies and Testing
Various generic software development life cycle methodologies are available for executing software
development projects. Although each methodology is designed for a specific purpose and has its own
advantages and disadvantages, most methodologies divide the life cycle into phases and share tasks across
these phases. This section briefly summarizes common methodologies used for software development and
describes their relationship to testing.

Waterfall Model
The waterfall model is one of the earliest structured models for software development. It consists of the
following sequential phases through which the development life cycle progresses:

System feasibility. In this phase, you consider the various aspects of the targeted business process, find out
which aspects are worth incorporating into a system, and evaluate various approaches to building the
required software.
Requirement analysis. In this phase, you capture software requirements in such a way that they can be
translated into actual use cases for the system. The requirements can derive from use cases, performance
goals, target deployment, and so on.
System design. In this phase, you identify the interacting components that make up the system. You define
the exposed interfaces, the communication between the interfaces, key algorithms used, and the sequence
of interaction. An architecture and design review is conducted at the end of this phase to ensure that the
design conforms to the previously defined requirements.
Coding and unit testing. In this phase, you write code for the modules that make up the system. You also
review the code and individually test the functionality of each module.
Integration and system testing. In this phase, you integrate all of the modules in the system and test them as
a single system for all of the use cases, making sure that the modules meet the requirements.
4/18/2008 8:57 AM | prabakaran

____________________________________________ ____________________
________________________

This is really very good and imporatant article Thanks To All of You 4/21/2008 5:30 AM | Falguni

____________________________________________ ____________________
________________________

SMOKE TESTING versus SANITY TESTING:

I am a Test Manager and was recently preparing a document for new starters in my company.
When I came across this article I thought that I might share a few lines from my document with you, to
ensure a clearer understanding of the differences.

¬ Smoke Testing
Smoke testing is usually done at a ‘build level’ to test its stability. It is also hence called as BVT (Build
Verification Test).

It is usually done by the developers before the build is released or by the testers before accepting a build for
further testing.

This is usually done via a set of test cases that are executed to make sure that all major functionality works
and that there are no issues with either software or hardware and that testing can officially kick off. These
test cases are usually documented

¬ Sanity Testing

Sanity testing is done at ‘release level’ when software is ready for UAT.

Sanity testing may sometimes be subset of regression testing where a group of test cases that are related to
the changes made to the application (either due to defects fixes or change requests) are executed once
again.
This is usually the case, when the software has not undergone a rigorous phase of testing cycles.

In cases where the software has undergone a rigorous testing phase, Sanity testing may be avoided or kept
to a bare minimum where all or some of the major functionality is quickly checked to ensure that it is ready
for release.

Test cases for Sanity testing do not need to be documented

5/13/2008 12:01 AM | Lata - Australia

____________________________________________ ____________________
________________________

Hi all,
offcourse I am 50% clear.but still wnt some clear clarification .can u give it 5/15/2008 2:02 AM | Anitha

____________________________________________ ____________________
________________________

Hi,
What u have written is clear. But still in some cofusion.Just now I started my career in testing.So I want it
more clear.5/15/2008 2:25 AM | Sanny

____________________________________________ ____________________
________________________

am very happy with your answers Lata

please give some more things in Testing 5/19/2008 5:22 AM | Ashwin
____________________________________________ ____________________
________________________

hey can anybody explain how to estimate testing time and man power? 5/21/2008 4:08 AM | kalyan

____________________________________________ ____________________
________________________

Hi Ashwin,

I am not sure as to where to start!!!

There is so much to it in terms of the theory aspect to testing, like the SDLC methodolgies,White box, balck
box, Functional testing, Non Functional testing etc....

My document for my team was 74 slides of .ppt or roughly 50 pages of .doc.

My suggestipon to you would be to get free online books on testing, or probably to gather the topics that you
want(maybe from the online book) and look up on Google.

Again, this is just the theory aspect..when it comes to putting this knowledge into practice, thats where the
challenge is....you find it quite different!!!
But soon, one day down the line you will get there!! As someone once said "PRACTICE MAKES MAN
PERFECT."

Good Luck Ashwin.

5/26/2008 12:04 AM | Lata - Australia

____________________________________________ ____________________
________________________

I m very clear on that sanity and smoke testing

thank u very much mr.Lata - Australia 6/1/2008 10:08 AM | latha

____________________________________________ ____________________
________________________

""""""Guys excuse me i think i found one of my very old friend in this blog so sending her message to contact
her """"""

Hi seetha J

while going through this column i found your name

are you the same person were living in pammal annanagar SBI colony friend of prasana .if yes then about
me
I am sundar was staying in pammal studied in MCC my email id is sundar_0305@hotmail.com

reply l

cheers
sundar
6/17/2008 6:44 AM | sundar from pammal

____________________________________________ ____________________
________________________

this discussion is creating confusion. can anyone give it in a properway.

Thanks,
Ayasha 9/22/2008 9:17 AM | ayasha

____________________________________________ ____________________
________________________

smoke testing: When Build is received to check for the basic features

Sanity Testing : If some minor discripencies are seen in the build during smoke, it is sent for a fresh build.
on receiving the fresh build sanity is to check for that smoke features that have come up with fixes 9/30/2008
8:08 AM |nagendrakumar

____________________________________________ ____________________
________________________

perfect difference 11/19/2008 9:57 PM | chetana

____________________________________________ ____________________
________________________

Sanity testing: We will check the complete functionality of the application.

Smoke Testing: We will check the basic functionality of the application. 2/4/2009 1:13 AM | Dipak Bidwai

____________________________________________ ____________________
________________________

Sanity testing: We will check the complete functionality of the application.

Smoke Testing: We will check the basic functionality of the application. 2/4/2009 1:15 AM | Dipak Bidwai
Bangalore

____________________________________________ ____________________
________________________
Smoke Testing : After getting the build from development team, to check the stability of the build for further
testing,i.e. smoke testing.

Sanity Testing : To conduct testing on build after some changes and checking the application once again,is
Sanity testing
2/8/2009 7:32 PM | Rabi,Bangalore

____________________________________________ ____________________
________________________

This caching reduces the response time of the request for configuration information. The expiration and
scavenging mechanism for the data cached in memory is similar to the cron algorithm in UNIX. 3/14/2009
2:52 AM | dll

____________________________________________ ____________________
________________________

Sanity:- We check the measure functionality is working and has no effect. Thus we can ensure major
functionality is working. This may includes test cases from Regression.
Sanity testing should be performed in lesser time.
Main purpose is to ensure functionality working and includes positive test cases.
4/13/2009 12:59 AM | Mayur K, Pune

____________________________________________ ____________________
________________________

Please corrcet me if i am mistake

Smoke teting : Smoke testing is the first phase of testing and it will run once the bulid is prepared and Just to
check weather the build is stable ans can go for further testing or not
Smoke testing can be performed for the bulid just released
Sanity testing : It will be performed when a new bulid is released,to check the major functionalities are
working properly, and check because of this fix then other functionalites has not broeken and not introducing
any other bugs.
It will be perforemed instead of regression testing to the particular bulid at deadline 4/16/2009 4:57 AM
| Sandhya

____________________________________________ ____________________
________________________

Thank You Devankur for giving good definitions for smoke and sanity testing. 6/17/2009 8:15 AM | Ajay
Bharadwaj

____________________________________________ ____________________
________________________

Hi,
There is no such basic difference between the "Smoke" and "Sanity" testing. But her i tried to make some
differences.
Smoke Testing- 1. It's a informal testing. 2. We are doing the smoke testing to test the build stability,
whether we can proceed further for testing or not. 3. Not testing the application so deeply. 4. Just giving the
cursory look on the major functionality of the application.

Sanity Testing- 1. Once the build is pass in the smoke testing, then only we will go for sanity testing. 2. Here
we are testing the application deeply as compared to smoke testing. 3. it's a formal testing. 4. Sometime
when we are getting a patch build, then instead of doing regression testing, we will go for sanity
testing. 6/26/2009 12:15 AM | Sunil Kumar Behera

____________________________________________ What is the difference

between Smoke and Sanity testing?

This is a good discussion indeed. For more information on software testing visit www.ajoysingha.info
8/5/2009 6:13 AM | Ajoy Kumar Singha

____________________________________________ ____________________
________________________

smoke vs sanity testing is found upto some extent a bit similar ,but main difference is that in smoke testing
after checking first few details if any bug found without testing rest the build is rejected,whereas in sanity the
build is checked when it is backed from the first pass and then because of bug fixed by the developer is
working is properly now or not is checked. 8/12/2009 9:24 AM | andrew hudson

____________________________________________ ____________________
________________________

Nice explanation 8/28/2009 8:17 AM | vidya

____________________________________________ ____________________
________________________

Nice explanation very useful 8/28/2009 8:17 AM | vidya

____________________________________________ ____________________
________________________

Lata, Test Manager - Australia

It is very useful.
I would like to thank you behalf of all...:-) 10/24/2009 11:59 AM | Harish

____________________________________________ ____________________
________________________

Wt the hell, u gys r trying to clarify. If u don't know exactly the difference or if u would not know It meanse or
u not a good tester or u cannot test application. Instead of being theoritical get the practical
knowledge. 4/16/2010 12:58 AM | sushma

____________________________________________ ____________________
________________________
Its a really nice definition and argument section... Which indeed clear all doubts... 7/1/2010 12:06 AM
| Prasant

____________________________________________ ____________________
________________________

Automotive Diagnostic Tools & Equipment

sinosells, the best place for online shopping from China.

sinosells selling big brands of auto parts: auto auto diagnostic tool, ECU Tools, Locksmith Tools, Auto
Accessories, Digital Products, odometer correction, diagnostic scanner, auto scanner, immo code reader,
airbag reset, transponder key, key blank.
Please visit our website :http://www.sinosells.com for more details.
sionsells "faith-based, customer first, service first", sinosells price will be more robust steps, boarded the
update stage.
9/19/2010 4:44 AM | sinosells

____________________________________________ ____________________
________________________

Thank you for your discussion, I found the perfect answer, thank you very much..
9/19/2010 4:45 AM | Amy

____________________________________________ ____________________
________________________

For my knowledge, am giving the definotions for SMOKE & SANITY testing.
SMOKE TESTING:Review the coding modifications using white box techniques is called as SMOKE testing.
SANITY TESTING:It is also called as TESTER ACCEPTANCE TESTING. Tester runs some testcases to
know whether initial build working in test environment or not ? 10/11/2010 2:35 AM | Rajani

____________________________________________ ____________________
________________________

Its a really nice definition and argument section... Which indeed clear all doubts 10/13/2010 6:30 AM
| mnaish rai

____________________________________________ ____________________
________________________

Its a really nice definition and argument section... Which indeed clear all doubt 10/13/2010 6:30 AM | mnaish
rai

____________________________________________ ____________________
________________________

We use Smoke when a product is new and sanity for releases but Smoke is used when the changes in the
product have greater impact on its functionality.
http://soft-engineering.blogspot.com 12/24/2010 6:35 AM | bipin

____________________________________________ ____________________
________________________

Hi,
To my knowledge both testings are same .smoketesting is nothing but piolet testing.(BVT testing) 2/9/2011
3:45 AM |Rajani