omkarqa

 Profile Answers by omkarqa Questions by omkarqa

• Oct 13th, 2005

 

sanity test is called as Test Acceptence test and it will be done to check whether the application coming for testing is full filling basic functionality which it supposed to have....

Smoke test is conducted after sanity test , the purpose is whether there is any danger or smoke if we accept the application for test... Sanity test is done in Positive percerption and smoke is done in terms of negative perception...

junejacz

 Profile Answers by junejacz Questions by junejacz

• Oct 21st, 2005

 

Hey Omkar,

Can you explain the difference in a bit more detail. I am kind of confused. As far as I heard they both are the same type of testings.

Thanks

Chetan

priya

• Oct 26th, 2005

 

SMoke testing: this testing is done in post production stage when the application is migrated from QA environment to production environment to check whether its working fine and nothing is broken

Sanity testing: Checking the basic flow of the system like checking all the pages are displayed , all the links are properly working.  

sanity testing is done after the installation testing  

ramu

• Nov 9th, 2005

 

Hi

Sanity testing: Whether a development team released build is stable for complete testing or not?  is called sanity testing.(if it is not run it will send back to devolepment)

Smoke testing: It is an extra shakeup in sanity testing. In this level testing team reject a build with reason when that build is not working to be applied for complete testing.

process:- 

 Recieve build from developers -> sanity/smoke test -> functional & system tests -> UAT

jyothirmayi

• Nov 11th, 2005

 

conceptually, practically both are same. somke tesign and sanity testing hence these two terms are used as synonims by various companies. the difference between smoke testing and sanity testing, somke testing rather associated with -ve perception while sanity testing is rather associated with +ve perception.

sunil

• Nov 14th, 2005

 

omkar Wrote:

sanity test is called as Test Acceptence test and it will be done to check whether the application coming for testing is full filling basic functionality which it supposed to have....

Smoke test is conducted after sanity test , the purpose is whether there is any danger or smoke if we accept the application for test... Sanity test is done in Positive percerption and smoke is done in terms of negative perception...

fullish giving answer. give correct answer, n tell in which company u r working and ur designation pls. hope u will reply to my ansqwer.

venu

• Nov 18th, 2005

 

smoke testing is conducted by development people according to the clients requirements.the first test conducted by testing people when build is received is called sanity testing.in sanity testing testing people check the basic functionality i.e whether all buttons are working or not etc

bgl_brain

• Nov 28th, 2005

 

 hi

    that statement which u gave to as is wrong ..

smoke :Before start testing intialy tester chk major functionality wrking properly r not that is smoke testing it is done by tester only not developer

all testing activity r done by tester .exclude unit testing

thx,

Bgl_brain

Sripal

• Dec 16th, 2005

 

SMOKE Tetsing : Its a integration Testing approach, In which process the all units/components are coupled to get the stable build.

SANITY Testing : Typically belongs to System Testing, To ensure that the given build is stable for the entire testing or not!

Kranthi Kumar Reddi

• Jan 30th, 2006

 

Hi Friends,

      Here little bit confusing,

      After Completion of Unit and Integration Test, The Build comes to the picture.  To check the build by using Build Verificaiton Testing is called "Smoke Testing"

      Smoke Testing: To check the Build for further Testing is possible or Not  either Hardware or Software Specifications are called Smoke Test.

      If the Build Verificaiton Testing is succesfully, then go for further Testing.  Otherwise Build Verification Test Failed, reported to QA People.

      Sanity Testing: Initial Testing Effort  is done through Inspections,Review and Walkthroughs to check major functionalities on this testing.

Thanks and Regards,

 Kranthi Kumar Reddi,

 

Shraddha

• Mar 24th, 2006

 

If it was wrong answer then Write the correct answer for other person.

karth!k

• Jun 15th, 2006

 

Reading all the above I?m fully confused. I forget everything what I know in previous. Please any explain clearly with correct proof. That would help me more.

anil

• Jul 11th, 2006

 

sanity testing-

wetherdevelopment team released build is stable for complete test or not

this  type f primary testing of build is called sanity testing r acceptance testing.

smoke testing

smoke testing it is small shake up in sanity,testing processfor this test testengineer reject the built with the reason when that built is not working.

pavanswapna

 Profile Answers by pavanswapna 

• Sep 15th, 2006

 

Sanity Test:

It is the Initial Testing which is done to check whether the application is ready for testing

Smoke Testing:

It is done after the Sanity Test. It is done to check whether the major functionalities of the applicaion is working fine and ready for test?

Susanta Behera

• Sep 30th, 2006

 

Sanity Testing:--before starting the testing processes check for avalabilty of Functionality, and Determine that which Functionality is ready fot test (Tester acceptable) it is done on +ve PerceptionSmoke testing:-before starting the testing processes check for non avalabilty of Functionality, and Determine that which Functionality is not ready fot test (Tester Reject the build due to some resion) it is done on -ve Perception

Vadiraj

• Dec 21st, 2006

 

Smoke tests get their name from the electronics industry. The circuits are
laid out on a bread board and power is applied. If anything starts smoking,
there is a problem. In the software industry, smoke testing is a shallow and
wide approach to the application. You test all areas of the application
without getting too deep. This is also known as a Build Verification test or
BVT.

In comparison, sanity testing is usually narrow and deep. That is they look
at only a few areas but all aspects of that part of the application. A smoke
test is scripted--either using a written set of tests or an automated
test--whereas a sanity test is usually unscripted.

nirmmal

 Profile 

• Feb 11th, 2007

 

A smoke test is a series of test cases that are run prior to commencing with full-scale testing of an application. The idea is to test the high-level features of the application to ensure that the essential features work. If they do not work, there is no need to continue testing details of the application, so the testing team will refuse to do any additional testing until all smoke test cases pass. This puts pressure on the development team to ensure that the testing team does not waste valuable testing time with code that is not ready to be tested.Once smoke tests are implemented as part of your software development life cycle, you will see the overall quality of the product improve and the sensitivity to producing high quality software increased.

Raja

• Jun 12th, 2007

 

Sanity test - This test is performed to find out whether the software is stable enough to accept it for major testing.

Smoke test - This test is performed to find out whether the system contains critical failures that has high probablity of throwing the software release behind schedule. If smoke test passes, it helps build confidence to managment about the software.

Rahul Agrwal

• Jun 25th, 2007

 

hi, rahul

Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but not bothering with finer details

Sanity testing is a cursory testing; it is performed whenever a cursory testing is sufficient to prove the application is functioning according to specifications. This level of testing is a subset of regression testing. It normally includes a set of core tests of basic GUI functionality to demonstrate connectivity to the database, application servers, printers, etc.

Azmat

• Jul 30th, 2007

 

Smoke Test: When a build is received, a smoke test is run to ascertain if the build is stable and it can be considered for further testing. Smoke testing can be done for testing the stability of any interim build. Smoke testing can be executed for platform qualification tests. Sanity testing: Once a new build is obtained with minor revisions, instead of doing a through regression, a sanity is performed so as to ascertain the build has indeed rectified the issues and no further issue has been introduced by the fixes. Its generally a subset of regression testing and a group of test cases are executed that are related with the changes made to the app. Generally, when multiple cycles of testing are executed, sanity testing may be done during the later cycles after through regression cycles.

Azmat

• Jul 30th, 2007

 

Smoke Test:

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

Sanity testing:

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

azmat

• Jul 30th, 2007

 

I Just want to clarify more here: a sanity test is not the same as a Smoke Test or a
Build Verification test. The former is to determine a small section of the
application is still working after a minor change (which is not a good
policy, btw--you should do a regression test instead) and a Smoke or Build
Verification Test (BVT) is designed to touch every part of the application
in a cursory way. It's is shallow and wide. A Sanity test tends to be
unscripted, but you could (or should!) use a sub-set of your existing test
cases to verify a small part of your application. This is not quite a
regression test, where all areas of the application are tested using a
subset of the test cases.

A regression test is a more complete Smoke Test or BVT. A sanity test is a narrow regression test that focuses on a one or a few areas of functionality.

I hope it will clear all the confusion
 thanks and regards
Azmat

Pavani Patchipulusu

• Oct 22nd, 2007

 

Smoke Testing:
 After the developer completes his developing of the project ,the project is assigned to tester for testing.This is the first type of the testing the tester performs.Here , the tester ckecks the basic functionality of the application whether it is working correctly or not.(whether it is free from errors or not).
Sanity Testing:
    Every new version of the application delivered by the developer after making modificataion is tested to check whether the modified version is working better than the earlier version.
Let me know if this is a good ans or not.
Thanks,
pavani.

srikanth

• Oct 29th, 2007

 

smoke testing:All areas are covered ,but not in detail.
This test is used to check whether it is working fine or not and can be pushed forward or not.


sanity test:It is a subset of regression testing,which will test only those areas which needs to concentrated more.
It is done with test cases.

asha.kapalavai

 Profile Answers by asha.kapalavai 

• Dec 6th, 2007

 

smoke testing: 

taking build(final code) from developers and installing it on a system for testing it is called smoke testing. database build engineer is responsible for doing this...

sanity testing: 

it is the replacement to regression testing when the situation is like below.

if we fing bugs in particular area of the application always....concentrating in depth on that particular area which is having bugs all the time is called sanity testing.

lakshmi09

 Profile Answers by lakshmi09 

• Dec 27th, 2007

 

actually both smoke testing and sanity testing are same in the sense.

but before the build is released by the development department they will perform overall  testing of the application to check whether it is ready for detailed testing or not.this is called as smoke testing.

but in some companies once the build is released to testing department,testers will perform overall testing to check whether application is ready for detailed testing or not.this is sanity testing or smoke testing.

depending on company they will call either it as smoke or sanity but both are one and the same.
 

mohan056

 Profile Answers by mohan056 

• Jan 10th, 2008

 

smoke testing: it means testing the basic and critical features of the application before doing rigorous testing. And it will make sures that wether the application is testable are not.


Sanity Testing: retesting the same old smoke test cases again is called sanity testing

silpavajja

 Profile Answers by silpavajja 

• Mar 22nd, 2011

 

Here are the differences you can see:

SMOKE TESTING:

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

SANITY TESTING:

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

Hope these points will help you to clearly understand the Smoke and sanity tests and will help to remove any confusion.

paramjeet singh

• Jul 29th, 2011

 

In smoke testing and sanity testing we try to find that application is testable or not . we try to find any blocker bug. It means smoke & sanity testing are same

Divya HS

• Oct 15th, 2011

 

Smoke Testing is done by developers where as Sanity Testing is conducted by Test Engineers.

Both are conducted for same purpose ie to check basic functionalities of a program or module.