The Collage of Devankur Thakur

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.

100% Perfect Differences.

Mr. Devankur,
Nitendra Kumar is also correct, sanity testing is not subset of regression testing its a next testing strategy, ofcourse defined by testers themselfs for there satisfaction, testers are always after deadline and they have to follow this stage instead of going for a regression testing again.

S. J.

Hi Nitendra/Seetha,

Okay, I agree 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.

Thanks.

Hello Mr. Devankur Thakur,
Good Morning,

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.

Regards,
Nitendra

Nitendra,

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.

Best Regards,
-Devankur

Devankur/Nitendra,

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.

All the BEST to both of u,

With Love
Seetha J.
fr Chennai.

smoke is done on build version and sanity is done on release version. do you agree friends?

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.

Hi all,

Can any anybody tell me
What is piolet testing ?

Thanks & Regards
Ramappa Nashi

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.

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

Is there any diffrence between Functional and Sanity Testing??????????

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.

Thanks for the
Nice definition for smoke test and sanity testing

thanks for the clarification between smoke and sanity testing

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.

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

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

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

Thanks
satyendra

Hi
i think after regration testing no need sanity testing.
becacuse regration testing is compleate the all testing application.

All of the people are not compromising about one defination.this is bad.

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

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

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

Hi Devankur,

Such a great defn. thankyou
have a lovely day!

Hi Devankur,

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

Thanks and Regards,
Mangalmurti

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.

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

Hi ,
this is kumar with a querry!

what is piolet work,when it is conducted,for what purpose piolet work is conducted.

hi,
this is hriday

what is sanitaton in testing

Hi All,

Plz describe above Que.........

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

Can anyone provide me a correct definition of stress testing.................?

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.

Are they Similar or Different ? Then What is Compliance Testing, Mutation Testing And Localization Testing ?

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

may i know the difference between compatibility and configuration testing?

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

thanx for giving such a valueble definition.

Hi all,This has now became a lot confusion.

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.

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.

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.

thanks for definition for easy undersating words used

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

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.

what is the difference between bench mark and base line in the quality.

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

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.

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.

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

what leve of testing regression testimng can be applied

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

smoke testing is perform to check all functionality is working before testing the test case

can any body tell me difference b/w retesting and regression testing?
Mail id-
tyagi_anki@yahoo.co.in

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.

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

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

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.

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

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.

Hi,

Smoke testing is conducted in positive perception and where as Sanity testing is conducted in negative perception.

Now i understood abt smoke Vs Sanity....can any body tell me .. what is difference between exploratory and adhoc testing?

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

Plz. Define Alpha beta testing precise and in simple words

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.

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.

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.

Hi All

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

that it

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

thank you

http://geekswithblogs.net/dthakur/archive/2004/08/24/10144.aspx

Now i understood abt smoke Vs Sanity

looks good and helpful.Thanks for taking time and presenting your points in-detailed.

can u give me an example cleary to differenciate smoke and sanity testing.

This is agreat piece of explanation.

Thankz a lot

Very brief and to the point.
Good to understand and chewable too.

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

Hi Devankur,
That was really very good information.

Hi all,

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

Hi all,

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

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

can cany one please explain do we need to write seperate test cases for smoke and sanity testing?

very nice.thank you.

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

Hi
am read the differance in that am not clear pls give some examples.

Thanks
Thirumal.K

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

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

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.

Hi thanks

from just i clarified doubt about sanity and smoke testing difference.