19 October 1987 Why We Test - To Know How It Performs Or Might Fail
Author Affiliations +
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.
© (1987) COPYRIGHT Society of Photo-Optical Instrumentation Engineers (SPIE). Downloading of the abstract is permitted for personal use only.
Richard H. Spencer, 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); doi: 10.1117/12.943272; https://doi.org/10.1117/12.943272
PROCEEDINGS
20 PAGES


SHARE
RELATED CONTENT


Back to Top