Smoke testing (software)

In computer programming and software testing, smoke testing (also confidence testing, sanity testing[1]) is preliminary testing to reveal simple failures severe enough to reject a prospective software release. A subset of test cases that cover the most important functionality of a component or system is selected and run, to ascertain if crucial functions of a program correctly work.[2][1]:37 When used to determine if a computer program should be subjected to further, more fine-grained testing, a smoke test may be called an intake test.[1]:25

For example, a smoke test may ask basic questions like "Does the program run?", "Does it open a window?", or "Does clicking the main button do anything?" The process aims to determine whether the application is so badly broken as to make further immediate testing unnecessary. As the book Lessons Learned in Software Testing [3] puts it, "smoke tests broadly cover product features in a limited time ... if key features don't work or if key bugs haven't yet been fixed, your team won't waste further time installing or testing".[4]

A frequent characteristic of a smoke test is that it runs quickly, often in the order of a few minutes and thus provides much quicker feedback and faster turnaround than the running of full test suites which can take hours or even days.

Smoke testing performed on a particular build is also known as a build verification test.[4][2][5]

A daily build and smoke test is among industry best practices.[6] Smoke testing is also done by testers before accepting a build for further testing. Microsoft claims that after code reviews, "smoke testing is the most cost-effective method for identifying and fixing defects in software".[7]

One can perform smoke tests either manually or using an automated tool. In the case of automated tools, the tests are often initiated by the same process that generates the build itself.

Smoke tests can be broadly categorized as functional tests or unit tests. Functional tests exercise the complete program with various inputs. Unit tests exercise individual functions, subroutines, or object methods. Functional tests may comprise a scripted series of program inputs, possibly even with an automated mechanism for controlling mouse movements. Unit tests can be implemented either as separate functions within the code itself, or else as a driver layer that links to the code without altering the code being tested.

See also

References

  1. ↑ 1.0 1.1 1.2 Standard Glossary of Terms used in Software Testing, Version 2.4 (Report). International Software Testing Qualifications Board. 2014.
  2. ↑ 2.0 2.1 Dustin, Rashka, Paul. "Automated Software Testing -Introduction, Management, and Performance". Addison-Wesley 1999, p. 43-44. ISBN 0-201-43287-0.
  3. ↑ Cem Kaner, James Bach, Bret Pettichord, Lessons learned in software testing: a context-driven approach. Wiley, 2001
  4. ↑ 4.0 4.1 Kaner, Bach, and Pettichord. "Lessons Learned in Software Testing". Wiley Computer Publishing, 2002, p. 95. ISBN 0-471-08112-4
  5. ↑ "How to: Configure and Run Build Verification Tests (BVTs)". MSDN Library for Visual Studio 2005. Retrieved 2010-11-20.
  6. ↑ McConnell, Steve. "Rapid Development". Microsoft Press, p. 405
  7. ↑ "Guidelines for Smoke Testing". MSDN Library for Visual Studio 2005. Retrieved 2010-11-20.

External links