Proceedings Paper
Why We Test - To Know How It Performs Or Might Fail| Format | Member Price | Non-Member Price |
|---|---|---|
| $17.00 | $21.00 |
Paper 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.
Paper Details
Date Published: 19 October 1987
PDF: 20 pages
Proc. SPIE 0857, IECON'87:Automated Design and Manufacturing, (19 October 1987); doi: 10.1117/12.943272
Published in SPIE Proceedings Vol. 0857:
IECON'87:Automated Design and Manufacturing
Victor K.L. Huang, Editor(s)
PDF: 20 pages
Proc. SPIE 0857, IECON'87:Automated Design and Manufacturing, (19 October 1987); doi: 10.1117/12.943272
Show Author Affiliations
Richard H. Spencer, IBM Corporation (United States)
Published in SPIE Proceedings Vol. 0857:
IECON'87:Automated Design and Manufacturing
Victor K.L. Huang, Editor(s)
© SPIE. Terms of Use
