A test result that returns True when in fact the result should be False.

A FalsePositive test result indicates a fault with the test procedure rather than a fault with the product under test.

''Or it may occur when a test is only capable of statistical prediction.  Most medical diagnostics are of this sort; it doesn't mean the test is broken; is just means that we aren't capable of complete accuracy using the current state of the art.''

Tests are designed to identify product faults.  Sometimes a test will indicate a fault even though there is nothing wrong with the product.  This is called a FalsePositive.  Usually this means something is wrong with the test procedure or something was wrong with how the test was carried out.  To eliminate FalsePositive results, improve your test procedure.

It is wrong to assume that FalsePositive results are "OK" because being over cautious is not a bad thing.  This is a naive notion.  Your test results become so cluttered with FalsePositive results, you can't find the real problems.  It's like TheBoyWhoCriedWolf.

* False positive results can also be damaging in their own right, and not just as clutter. For example, a false positive on a medical test could cause someone to undergo a dangerous operation.

''I am reminded of a Navy contract to detect faults in torpedoes.  The requirements stated that any number of false positives were acceptable as long as 100% of faults were always detected.  The solution was to build a simple device that just always reported a fault.  "Here, hook it up to this brick and it will find the faults."  "But that's not even a torpedo."  "It doesn't matter!"'' -- WilliamFrantz
----
Remember statistics class? Did you ever confuse Type I and Type II errors? Still can't remember which is which?

----
Often, it is a strategy to allow for false positives. If a test cannot be perfect, but its error is skewable, shifting it so that false positives are more frequent lowers the risk of FalseNegative''''''s. In turn, this insures that any negative result is trustworthy, at the expense of making the positive result non-trustworthy.

Example: if you have a simple, inaccurate test that searches for a deadly disease, skewing the test towards false positives is a good thing. Anyone who gets a negative on the test is guaranteed clean. Anyone who gets a positive on the test is likely to be infected, and you can spend the extra money doing the full spectrum of expensive tests on them. If the disease is in 3% of the population, and there is a 7% chance of false positives, this means that you only need to run the expensive suite over 10% of the population, saving 90% of the test costs.

-- RobMandeville