Teena Pappachan

• Feb 19th, 2006

 

Hi,

Smoke Testing: Smoke testing is non-exhaustive software testing, ascertaining that the most crucial functions of a program work, but does not bother with finer details.

Sanity Testing: 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.

Regards,

Teena.

Sasi

• Feb 23rd, 2006

 

HiIn Smoke testing we test the main functionality of the system instead of testing the whole systemIn Sanity testing we test that system is stable till the end of the testing and not get crashed.

Sirish

• Feb 27th, 2006

 

Hi,Smoke Testing: Is the first test that that will be conducted on a build. After receiving the initial build(application) from development, the testing team will test whether the build is working as per customer/client's expectation or not (that is the basic functionality of the application, the key functionality should work)Sanity Testing: Here the testing team will check whether all the menus,text fields,buttons (i,e the GUI) is working propery or not.Then the testing team will conduct TAT(Tester Acceptance Test). Here they will decided whether the build is accepatble for testing or not.These three tests will be conducted before starting the Blackbox testing

Nandini Kannan

• Apr 12th, 2006

 

Smoke Test is a dirty and quick test done as soon as a build is given to ensure that the system is reliable and does not crash

Sanity test is to test whether the build is sane enough or meets important requirements before we can proceed with a majot testing effort.

M.Ragothaman

• Apr 14th, 2006

 

smoke testing - To test whether the build is stable or not by doing some testing

Sanity testing - to test whether the build meets the requirements are not

Regards

Raghu

saravanan

• Jun 3rd, 2006

 

 

     Smoke testing _BVT(Build Verification testing)

     Sanity testing _BAT(Build Acceptance testing)

     BVT:- 10 to 15% is critical test cases.

     BAT:- 85 to 90% of test cases will be BAT.That is non crtitical test cases.

    BVT:-Once navigation tests are complete,execute the tests that are termed critical. That means, a set of test scenarios/cases must be identified as critial priority, such that, if these tests do not work, the product does not get acceptance from the test team. Usually, this will be 10% to 15% of the total test cases.

 

      BAT:- The next job is to go thru the rest of the 90% of test cases and the respective test steps one by one and then actually performing the steps on the software roduct.

Biswajit pani

• Jun 12th, 2006

 

Smoke Testing - Testing of critical features Done before Testing regours Testing of Application.

Sanity Testing - Testing of Critical Features done Before Regression testing..

Regards

Biswajit pani

ravi

• Jun 30th, 2006

 

Sanity Tersting : Testing Basic Functionality of application.

Smoke Testing: Testing Stability of the Application

sumit4u

• Jul 6th, 2006

 

smoke te..is testing major functionalites heavily minor functionalities r not tested.it is a nonexhaustive testing.(not done thoroughly).It can b done in any phase of stlc once after the module is ready.

Sanyty testing :it is a cursery or casual testing done in order to check wheather the sy si s ready to test or not ..especially done after a small change iis done .thats why it is called sub regression testing aswell. 

sudhakar

• Jul 30th, 2006

 

smoke testing: it is done to check the initial check up of the build

snanity testing: its is aslo garabage testing. it is done to

check extra functionality of build

prasad.gandra

• Aug 30th, 2006

 

smoke testing :  Possibilities of defects finding during basic functionality execution before start real testing .

Sanity testing:  To check whether our application is stable or not before start real testing ?

chandru

• Sep 5th, 2006

 

smoke testing:

Testing the behavior of application without any user input by randomly accessing all the functionality.

sanity testing:

Testing to understand flow application in which interacting with database ,network connectivity and other hardware.

Guest

• Oct 1st, 2006

 

 Smoke testing :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 :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.

 

 sudhakar kolla.

 

My Email:kollasudhakar2005@yahoo.co.in.

 

My Number:09819859346.

 

Sudhakar kolla

• Oct 3rd, 2006

 

Smoke testing :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 :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.

sudhakar kolla.
My Email:kollasudhakar2005@yahoo.co.in.
My Number:09819859346.

mermathon

 Profile Answers by mermathon 

• Oct 4th, 2006

 

Hi,

I think the better way to remember this is (read in some site)

Smoke testing is to check how the system works after integrating or is it stable till the end. It is basically derived from an electrical term... where when you plug the appliance does it smokes or works properly.

Sanity testing - is to from term sane.... testing what we require and so it is testing the basic functionality of the application.

Correct me if it is wrong

Thanks

anjan

• Oct 25th, 2006

 

please clarify my question

what is the procedure for smoke test?

Pradeep R

• Nov 13th, 2006

 

Smoke Testing : It is nothing but installing the applicaition in client machines in test Environment. In smoke testing we will note down that proper installing is happening or not. Database connections will also be verifed. Smoke test will be failed when we face any problems while installing the applcation or if it takes more time to install the application.

Sanity Testing : it is done after smoke testing. Without functionality , test cases and test data we will check for major functionality to ensure that we can continue with full / complete testing. (End to end flow,  major scenarios)

pradeep r

Rajasekhar

• Nov 14th, 2006

 

 Hi anjan,

            Here is the answer for your question.

         You must take all high priority testcases and must test them.This is the process for Smoketesting.Because you must consider all client requirements(as a tester it is a good habit).If the all high priority testcases are passed then the smoketest is passed successfully.Otherwise it is failed.

   Regards,

  Rajasekhar.

sambit

• Nov 23rd, 2006

 

what is cursory testing?

Saravanan

• Dec 12th, 2006

 

Generally, a smoke test is scripted (either using a written set of tests or an automated test), whereas a sanity test is usually unscripted.

krishna1tester

 Profile Answers by krishna1tester 

• Feb 7th, 2008

 

Smoke Testing:   We will check the basic functionality of the application

Sanity Testing: We will check the complete functionality of the application



Regards,
Krishna.
-The Undertaking of New Action brings New Strength--

anand.bijwe

 Profile Answers by anand.bijwe 

• Apr 8th, 2008

 

Smoke Testing :-See when new Built come.the Tester check the main functionality of the application to ensure that whether that built stable acceptable or not( means built is not properly deployed)


Sanity Testing:- After Few round of regression testing is done we found application is quite stable.No errors we do sanity testing on fixes issue or major functionality

vk1978

 Profile Answers by vk1978 Questions by vk1978

• Feb 18th, 2009

 

Different Between Smoke Testing and Sanity Testing

Smoke Testing : An initial testing in which we check whether the basic
functionality of the application is working fine or not with the help of few
checklist. Once we get the new build we will execute those checklist. On
execution if those checklist as passed we will accept the build and go further
to do detailed testing on each and every functionality, if any of the checklist
fails we will reject the build.

Sanity Testing : An initial testing conducted on an application in
order to make sure that total functionality is proper

srinivasulub1981

 Profile Answers by srinivasulub1981 Questions by srinivasulub1981

• May 6th, 2009

 

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.

Srinivas