0% found this document useful (0 votes)
50 views1 page

Difference Between Smoke and Sanity Testing

Smoke testing involves briefly testing all major features of a software application to check for any failures, while sanity testing focuses on testing a small section or specific functionality in more depth after a minor change. Smoke testing is scripted, shallow, and wide, while sanity testing is usually unscripted, narrow, and deep. Both smoke and sanity testing are forms of initial testing used to check for any major defects before further testing.

Uploaded by

venukotari
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
50 views1 page

Difference Between Smoke and Sanity Testing

Smoke testing involves briefly testing all major features of a software application to check for any failures, while sanity testing focuses on testing a small section or specific functionality in more depth after a minor change. Smoke testing is scripted, shallow, and wide, while sanity testing is usually unscripted, narrow, and deep. Both smoke and sanity testing are forms of initial testing used to check for any major defects before further testing.

Uploaded by

venukotari
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 1

Difference between Smoke and Sanity 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 is shallow and wide. Smoke testing will be conducted to ensure whether the most crucial functions of a program work, 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. 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.

You might also like