Talk:Sanity testing

From Wikipedia, the free encyclopedia

I think spending half the article on comparison with smoke-testing and an instance of sanity checks very specific to software QA is a mistake of focus. Sanity checks are not specific to any particular field, but spending the bulk of the article discussing the finer semantics of the meaning within one particular field certainly gives that impression.

—Preceding unsigned comment added by 87.72.95.45 (talk) 06:21, 23 February 2008 (UTC)
Many do not consider sanity test to be synonymous with smoke test, and in my 14 years as a software tester I have not seen much consistent usage. (The example script that someone submitted on the discussion page looks like an example of a smoke test). I'd agree that a sanity test confirms any attribute or quality whose failure implies that something is crazy to continue, but whereas a smoke test has come to mean explicitly a software basic-functionality test, a sanity test could test for anything . e.g. I've used sanity Test (since at least 1994) to mean suitability-to-release for everything except the correct functioning of the software itself...
I agreed this need more general discussion on sanity testing. The distinction between smoke testing and sanity testing does not appear to be listed in any of the academic literature where they are lumped together. Smoke testing was originally a hardware term (i.e. does the smoke come out when you turn it on?) where as sanity testing is primarily about logic. I'd before including the statement that they are conflated, but removing the explanation of the distinction on the grounds that this is original research (until proven otherwise via a reliable source). Perhaps it should be moved to the talk page until such time as a source is written and published. Oboler (talk) 14:30, 18 May 2008 (UTC)

Once the Basic Test is complete and Basic Test Record is Available. The module will be delivered for Sanity test. Purpose of the Sanity Test is to verify that the product is in a state where Function test cases can be executed. Duration of this test is ONE DAY. Scope of this test.Sanity test is nothing but weather the developed build is able for conducting complete testing or not.


1. Installation Instruction, SAG and CD are available.
2.      Inspection of BT record.
3.      Module can be installed
4.      Start and Stop can be performed
5.      All the relevant processes are up and running

Based on success/Failure of the Sanity Test considering the above mentioned five points, the Modules goes either to the State FT Drop1 or back to the Design team

Removed from the article:


*Edit*
There are some errors in the calculations shown here.

7382 equals 544,644 NOT 53,874

also

918 x 155 equals 142290 NOT 142135
*End Edit*

Yes, these calculations are indeed wrong. They are illustrations of the sort of error that can be caught be simple sanity-tests of the sort described in the article. -- Karada 23:49, 4 Aug 2004 (UTC)

I fully agree and will remove the equivalence of santity testing to smoke testing. This equivalence seems to be most common in India. --Walter Görlitz 06:54, 13 October 2006 (UTC)

can any body tell where i can get testing tools —Preceding unsigned comment added by 58.68.28.178 (talk) 14:50, 31 August 2007 (UTC)