Smoke Test Sanity Test

7/24/2019 Smoke Test Sanity Test

1/7

http://www.softwaretestingmentor.com/articles/difference-between-smoke-and-sanity-testingity-testing/

Smoke testing is done to check the normal health of the build and make sure if it is possibleto continue testing. It is done in the beginning of the software testing cycle.

A subset of most basic and important test cases is selected and run to make sure that mostbasic and crucial functions of the software are working ne.

In some organizations smoke testing is also known as Build Veri cation Test BVT! as thisensures that the new build is not broken before starting the actual testing phase.

http"##www.guru$$.com#smoke%sanity%testing.html

Smoke Testing is performed after software build to ascertain that the criticalfunctionalities of the program is working fine .It is executed "before" any detailedfunctional or regression tests are executed on the software build.The purpose is toreject a badly broken application , so that the QA team does not waste time installingand testing the software application.

In Smoke Testing, the test cases chosen cover the most important functionality orcomponent of the system. The objecti e is not to perform exhausti e testing, but to

erify that the critical functionalities of the system is working fine.

http"##www.softwaretestinghelp.com#smoke%testing%and%sanity%testing%di&erence#

A Smoke test is designed to touch every part of the application in a cursory way. Its shallow andwide.

Smoke testing is conducted to ensure whether the most crucial functions of a program are working,

but not bothering with ner details. (Such as build veri cation . Smoke testing is normal health check up to a build of an application before taking it to testing in

depth.

http"##testingbasicinter'iew(uestions.blogspot.ro#)*+)#*+#what%is%smoke%testing%e,plain%it%with.html-more

Smoke testing is the surface le'el testing to certify that build pro'ided by de'elopment to Ais ready to accept for further testing.

What is Smoke Testing?Smoke testing is non-extensive software testing, which makes sure that the most crucial functions of aprogram work, but not bothering with finer details because in smoke testing we only checks the

Object 1
http://www.softwaretestingmentor.com/articles/difference-between-smoke-and-sanity-testingity-testing/http://www.guru99.com/smoke-sanity-testing.htmlhttp://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/http://testingbasicinterviewquestions.blogspot.ro/2012/01/what-is-smoke-testing-explain-it-with.html#morehttp://testingbasicinterviewquestions.blogspot.ro/2012/01/what-is-smoke-testing-explain-it-with.html#morehttp://www.softwaretestingmentor.com/articles/difference-between-smoke-and-sanity-testingity-testing/http://www.guru99.com/smoke-sanity-testing.htmlhttp://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/http://testingbasicinterviewquestions.blogspot.ro/2012/01/what-is-smoke-testing-explain-it-with.html#morehttp://testingbasicinterviewquestions.blogspot.ro/2012/01/what-is-smoke-testing-explain-it-with.html#morehttp://www.softwaretestingmentor.com/articles/difference-between-smoke-and-sanity-testingity-testing/


2/7

major functionality of the software.

Smoke testing is performed by developers before releasing the build to the testing team and afterreleasing the build to the testing team it is performed by testers whether to accept the build for furthertesting or not.

http"##softwaretestingfundamentals.com#smoke%testing#

ELABORATION

Smoke testing covers most of the ma!or functions of the software but none of them in depth.

"he result of this test is used to decide whether to proceed with further testing. If the smoke

test passes, go ahead with further testing. If it fails, halt further tests and ask for a new build

with the re#uired $es. If an application is badly broken, detailed testing might be a waste of

time and e%ort.

Smoke test helps in e$posing integration and ma!or problems early in the cycle. It can be

conducted on both newly created software and enhanced software. Smoke test is performed

manually or with the help of automation tools&scripts. If builds are prepared fre#uently, it is

best to automate smoke testing.

As and when an application becomes mature, with addition of more functionalities etc, the

smoke test needs to be made more e$pansive. Sometimes, it takes !ust one incorrect

character in the code to render an entire application useless.

ADVANTAGES

It e$poses integration issues. It uncovers problems early.

It provides some level of con dence that changes to the software have not adversely

a%ected ma!or areas (the areas covered by smoke testing, of course

http"##www.softwaretestingclass.com#smoke%testing#

Smoke testing is the initial testing process e$ercised to check whether the software under test is ready&stablefor further testing. ' See more at http &&www.softwaretestingclass.com&smoke'testing&)sthash.ii*v+ -".dpuf

rior to start Smoke testing few test cases need to created once to use for smoke testing. "hese test casesare e$ecuted prior to start actual testing to check critical functionalities of the program is working ne. "hisset of test cases written such a way that all functionality is veri ed but not in deep. "he ob!ective is not toperform e$haustive testing, the tester need check the navigations / adding simple things ' See more athttp &&www.softwaretestingclass.com&smoke'testing&)sthash.ii*v+ -".dpuf
http://softwaretestingfundamentals.com/smoke-testing/http://www.softwaretestingclass.com/smoke-testing/http://www.softwaretestingclass.com/smoke-testing/#sthash.iizv0LWT.dpufhttp://www.softwaretestingclass.com/smoke-testing/#sthash.iizv0LWT.dpufhttp://www.softwaretestingclass.com/smoke-testing/#sthash.iizv0LWT.dpufhttp://softwaretestingfundamentals.com/smoke-testing/http://www.softwaretestingclass.com/smoke-testing/http://www.softwaretestingclass.com/smoke-testing/#sthash.iizv0LWT.dpufhttp://www.softwaretestingclass.com/smoke-testing/#sthash.iizv0LWT.dpuf


3/7

"he test cases can be e$ecuted manually or automated0 this depends upon the pro!ect re#uirements. In thistypes of testing mainly focus on the important functionality of application, tester do not care about detailedtesting of each software component, this can be cover in the further testing of application.

"he Smoke testing is typically e$ecuted by testers after every build is received for checking the build is intestable condition. "his type of testing is applicable in the Integration "esting, System "esting and Acceptance

"esting levels.

Advantages of Smoke testing:

It helps to nd issues introduced in integration of modules.

It helps to nd issues in the early phase of testing.

It helps to get con dence to tester that $es in the previous builds not breaking ma!or features (o% course, only features e$ercised by smoke testing .

' See more at http &&www.softwaretestingclass.com&smoke'testing&)sthash.ii*v+ -".dpuf

Sanity test

After receiving a Software build with the minor issues $es in code or functionality, Sanity testing is carry outto check whether the bugs reported in previous build are $ed / there is regression introduced due to these

$es i.e. not breaking any previously working functionality. "he main aim of Sanity testing to check theplanned functionality is working as e$pected. Instead of doing whole regression testing the Sanity testing isperform.

Sanity tests helps to avoid wasting time and cost involved in testing if the build is failed. "ester should re!ectthe build upon build failure

Sanity testing is narrow / deep approach of testing, it needs to concentrate limited / main features of testingin detailed.

1ere are the few consolidated points of Sanity testing

Sanity testing follows narrow and deep approach with detailed testing of some limited features.

Sanity testing is typically non'scripted.

Sanity testing is a sub'set of regression testing.

Sanity testing is cursory testing to prove software application is working as mention in thespeci cation documents / meets the user needs.

Sanity testing is used to verify the re#uirements of end users are meeting or not.

Sanity testing to check the after minor $es the small section of code or functionality is working ase$pected / not breaking related functionality.


4/7

http &&www.softwaretestingmentor.com&articles&di%erence'between'smoke'and'sanity'testingity'testing&

Sanity "esting

+./hen there are some minor issues with software and a new build is obtained after

,ing the issues then instead of doing complete regression testing a sanity is performedon that build. 0ou can say that sanity testing is a subset of regression testing.).Sanity testing is done after thorough regression testing is o'er1 it is done to make surethat any defect ,es or changes after regression testing does not break the corefunctionality of the product. It is done towards the end of the product release phase.2.Sanity testing follows narrow and deep approach with detailed testing of some limitedfeatures.3.Sanity testing is like doing some specialized testing which is used to nd problems inparticular functionality.4.Sanity testing is done with an intent to 'erify that end user re(uirements are met onnot.5.Sanity tests are mostly non scripted.

http:// !g"#"$$!%om/smoke&sanit'&testing!htm(

After recei ing a software build, with minor changes in code, or functionality,Sanity testing is performed to ascertain that the bugs have been fixed and nofurther issues are introduced due to these changes .The goal is to determine thatthe proposed functionality works roughly as expected. If sanity test fails, the build isrejected to save the time and costs involved in a more rigorous testing .

The objective is "not" to verify thoroughly the new functionality , but to determinethat the de eloper has applied some rationality !sanity" while producing the software.

http://www.softwaretestingstuff.com/ !!"/# /difference-between-smoke-sanity-testing.html Sanity testing: After receiving a build with minor changes in the code or functionality, a subset of regression testcases are executed that to check whether it rectified the software bugs or issues and no other software bug isintroduced by the changes. Sometimes, when multiple cycles of regression testing are executed, sanity testing ofthe software can be done at later cycles after through regression test cycles. If we are moving a build from staging /testing server to production server, sanity testing of the software application can be done to check that whether thebuild is sane enough to move to further at production server or not.

http://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/ SA2I"3 "4S"I25

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 su6cient to prove
http://www.softwaretestingmentor.com/articles/difference-between-smoke-and-sanity-testingity-testing/http://www.guru99.com/smoke-sanity-testing.htmlhttp://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.htmlhttp://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/http://www.softwaretestingmentor.com/articles/difference-between-smoke-and-sanity-testingity-testing/http://www.guru99.com/smoke-sanity-testing.htmlhttp://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.htmlhttp://www.softwaretestinghelp.com/smoke-testing-and-sanity-testing-difference/


5/7

the application is functioning according to speci cations. "his level of testing is a subset ofregression testing. Sanity testing is to verify whether re#uirements are met or not, checking all features breadth' rst.

http://testingbasicinterview$uestions.blogspot.ro/search/label/Sanity% !&esting% !'xample .Sanity &esting is the subset of (egression &esting and it is performed when we do not have enough

time for doing testing.

Sanity testing is the surface level testing where )* engineer verifies that all the menus, functions,commands available in the product and project are working fine.

http://www.guru"".com/smoke-sanity-testing.html Smoke Vs Sanity Testing - Introduction and Differences

The key differences between Smoke and Sanity Testing can be learned with the help offollowing diagram #

http://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.html ifference between Smoke ! Sanity Software "esting:

Smoke testing is a wide approach where all areas of the software application are tested without getting into toodeep. However, a sanity software testing is a narrow regression testing with a focus on one or a small set of areasof functionality of the software application. he test cases for smoke testing of the software can be either manual or automated. However, a sanity test is
http://testingbasicinterviewquestions.blogspot.ro/search/label/Sanity%20Testing%20Examplehttp://www.guru99.com/smoke-sanity-testing.htmlhttp://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.htmlhttp://cdn.guru99.com/images/stories/Sanity_Smoke_Testing.pnghttp://testingbasicinterviewquestions.blogspot.ro/search/label/Sanity%20Testing%20Examplehttp://www.guru99.com/smoke-sanity-testing.htmlhttp://www.softwaretestingstuff.com/2009/12/difference-between-smoke-sanity-testing.html


6/7

generally without test scripts or test cases. Smoke testing is done to ensure whether the main functions of the software application are working or not. !uringsmoke testing of the software, we do not go into finer details. However, sanity testing is a cursory software testingtype. It is done whenever a "uick round of software testing can prove that the software application is functioningaccording to business / functional re"uirements. Smoke testing of the software application is done to check whether the build can be accepted for through softwaretesting. Sanity testing of the software is to ensure whether the re"uirements are met or not.

Smoke Testing Vs Sanity Testing !eyifferences

Smoke Testing Sanity Testing

Smoke &esting is performed to ascertain that thecritical functionalities of the program is workingfine

Sanity &esting is done to check the newfunctionality / bugs have been fixed

&he objective of this testing is to verify the+stability+ of the system in order to proceed withmore rigorous testing

&he objective of the testing is to verify the+rationality+ of the system in order to proceed withmore rigorous testing

&his testing is performed by the developers ortesters

Sanity testing is usually performed by testers

Smoke testing is usually documented or scriptedSanity testing is usually not documented and is

unscriptedSmoke testing is a subset of (egression testing Sanity testing is a subset of *cceptance testing

Smoke testing exercises the entire system from endto end

Sanity testing exercises only the particularcomponent of the entire system

Smoke testing is like eneral ealth heck p Sanity &esting is like speciali0ed health check up

#oints to note$ $oth sanity tests and smoke tests are ways to a oid wasting time and effort by%uickly determining whether an application is too flawed to merit any rigoroustesting. Sanity Testing is also called tester acceptance testing . Smoke testing performed on a particular build is also known as a buildverification test . &ne of the best industry practice is to conduct a 'aily build and smoke test in


7/7

software projects. $oth smoke and sanity tests can be executed manually or using an automationtool . (hen automated tools are used, the tests are often initiated by the sameprocess that generates the build itself. %s per the needs of testing, you may have to execute both Sanity and SmokeTests on the software build$ In such cases you will first execute Smoke testsand then go ahead with Sanity Testing$ In industry, test cases for SanityTesting are commonly combined with that for smoke tests, to speed up testexecution$ &ence it's a common that the terms are often confused and usedinterchangeably

http://testingbasicinterview$uestions.blogspot.ro/ !#1/! /sanity-testing-vs-regression-testing.html

6i&erence between Sanity and 7egression Testing

Distinction between Sanity and Regression Testing Sanity "esting 7egression "esting8. Sanity testing is a surface level testingwhere 9A engineer veri es that all themenus, functions and commandsavailable&presented in the product areworking ne.

8. 7egression testing is not a surface leveltesting.

:. Sanity testing is considered as a subsetof regression testing.

:. 7egression testing is not considered as asubset of any.

;. "his testing is performed&e$ecuted whentesters have not much&enough time fordoing testing.

;. "his testing is performed&e$ecuted whentesters have enough time for testing.

Documents

Smoke Test Sanity Test