Things to keep in mind..!!

Software testing proves the existing of bugs, not their absence.

A quality tester deliver quality product to end-customer..!!

If you do not like testing your product,most likely your customer won't like to test it either.

Do not fix bugs later, fix them now..!!

Detecting and fixing bugs as early as poosible ensures to deliver quality product.

Showing posts with label smoke and sanity. Show all posts
Showing posts with label smoke and sanity. Show all posts

Friday 1 July 2016

Difference between Smoke Testing and Sanity Testing?

smoke vs sanity
Difference between Smoke and Sanity Testing?
Smoke Testing :- Smoke Testing is a wide and shallow approach. It means we (Developer) test an application in a cursory way without going into too deep. Smoke Testing is basically performs to test the health of builds before handed over to the testing team for deep testing. It is done by developer. Some times it is also done by testers too. Smoke testing is scripted i.e. either we use test cases or automation script to test an application.
Why Smoke Testing performed?
Basically smoke testing is performed or conducted to make sure whether the most crucial functionalities of an application are working fine or not.

Sanity Testing :- Sanity Testing is deep and narrow approach. It means tester test a specific module or unit of an application thoroughly. It is also a subset of Regression testing. It is use to determine whether a small section or a module is working fine after a minor changes or not. Sanity testing is unscripted.
Why Sanity Testing performed?
Basically sanity testing is performed when developer wants to know the quick and fast status of the application after they have made changes in the code.