Why We Test - To Know How It Performs Or Might Fail

Richard H. Spencer

doi:10.1117/12.943272

19 October 1987 Why We Test - To Know How It Performs Or Might Fail

Richard H. Spencer

Proceedings Volume 0857, IECON'87:Automated Design and Manufacturing; (1987) https://doi.org/10.1117/12.943272
Event: IECON, Cambridge, 1987, Cambridge, MA, United States

Abstract

Designers and developers set out to create something, a hardware product, a computer program, an automated manufacturing application, or a piece of documentation. Their premise is that when developed and debugged, this creation will be good .... and that is as it should be. That premise fails to ask the question, "Under what conditions will this creation fail to perform as I have created it to do?" Too often there is an assumption that debug equates to testing. They are not the same. A well designed test should determine under what reasonable conditions the product will fail to perform as intended.

Citation Download Citation

Richard H. Spencer "Why We Test - To Know How It Performs Or Might Fail", Proc. SPIE 0857, IECON'87:Automated Design and Manufacturing, (19 October 1987); https://doi.org/10.1117/12.943272

ACCESS THE FULL ARTICLE

INSTITUTIONAL
Select your institution to access the SPIE Digital Library.

SELECT YOUR INSTITUTION

PERSONAL
Sign in with your SPIE account to access your personal subscriptions or to use specific features such as save to my library, sign up for alerts, save searches, etc.

PERSONAL SIGN IN

No SPIE Account? Create one

PURCHASE THIS CONTENT

SUBSCRIBE TO DIGITAL LIBRARY

50 downloads per 1-year subscription

Members: $195

Non-members: $335 ADD TO CART

25 downloads per 1 - year subscription

Members: $145

Non-members: $250 ADD TO CART

PURCHASE SINGLE ARTICLE

Includes PDF, HTML & Video, when available