# Sanity check

A **sanity test** or **sanity check** is a basic test to quickly evaluate whether a claim or the result of a calculation can possibly be true. It is a simple check to see if the produced material is rational (that the material’s creator was thinking rationally, applying ). The point of a sanity test is to rule out certain classes of obviously false results, not to catch every possible error. A may be checked to perform the test. The advantage of a sanity test, over performing a complete or rigorous test, is speed.

In arithmetic, for example, when multiplying by 9, using the for 9 to verify that the of the result is divisible by 9 is a sanity test—it will not catch *every* multiplication error, however it’s a quick and simple method to discover *many* possible errors.

In computer science, a *sanity test* is a very brief run-through of the functionality of a , system, calculation, or other analysis, to assure that part of the system or methodology works roughly as expected. This is often prior to a more exhaustive round of testing.

## Contents

## Mathematical

A sanity test can refer to various and other simple devices applied to cross-check . For example:

- If one were to attempt to 738 and calculated 54,464, a quick sanity check could show that this result cannot be true. Consider that 700 < 738, yet 700² = 7²×100² = 490,000 > 54,464. Since squaring positive integers preserves their , the result cannot be true, and so the calculated result is incorrect. The correct answer, 738² = 544,644, is more than 10 times higher than 54,464, and so the result had been off by an order of magnitude (it actually misses one digit).
- In multiplication, 918 × 155 is not 142,135 since 918 is divisible by three but 142,135 is not (digits add up to 16, not a ). Also, the product must end in the same digit as the product of end-digits 8×5=40, but 142,135 does not end in “0” like “40”, while the correct answer does: 918×155=142,290. An even quicker check is that the product of even and odd numbers is even, whereas 142,135 is odd.
- The output of a cannot be 700 , since that is a measure of , not power (energy per unit time). This is a basic application of .

## Software development

In software development, the sanity test (a form of which offers “quick, broad, and shallow testing”) determines whether it is possible and reasonable to proceed with further testing.

Software sanity tests are synonymous with . A sanity or smoke test determines whether it is *possible* and *reasonable* to continue testing. Sanity tests exercise a subset of application functions needed to determine whether the systems are accessible and the application logic is responsive. If the sanity test fails, it is not reasonable to attempt more rigorous testing. Sanity tests are ways to avoid wasting time and effort by quickly determining whether an application is too flawed to merit any rigorous testing. Many companies run sanity tests on an as part of their software development life cycle.

Sanity tests may be a used as an aid to software. Consider, an application or piece of software usually involves multiple subsystems between external input and output from the system. When the overall system is not performing as expected, a sanity test may be used to aid decisions of what to investigate next. If one subsystem is not giving an expected result, other subsystems might be eliminated from the further investigation.

A is often used as a sanity test for a development environment. If the program fails to compile or execute, the supporting environment likely has a configuration problem. If it works, any problem being diagnosed likely lies in the actual application in question.

Another, possibly more common usage of ‘sanity test’ is to denote checks which are performed *within* program code, usually on arguments to functions or returns therefrom, to see if the answers can be assumed to be correct. The more complicated the routine, the more important that its response be checked. The trivial case is checking to see that a file opened, written to, or closed, did not fail on these activities – which is a sanity check often ignored by programmers. But more complex items can also be sanity-checked for various reasons.

Examples of this include bank account management systems which check that withdrawals are sane in not requesting more than the account contains, and that deposits or purchases are sane in fitting in with patterns established by historical data – large deposits may be more closely scrutinized for accuracy, large purchase transactions may be double-checked with a card holder for validity against fraud, ATM withdrawals in foreign locations never before visited by the card holder might be cleared up with him, etc.; these are “runtime” sanity checks, as opposed to the “development” sanity checks mentioned above.