Whittaker, J.A., 2000, ‘What Is Software Testing? And Why Is It So Hard?’, IEEE Software, vol. 17, no. 1, pp. 70-79
For example, to check for structural completeness, testers might ask these questions:
Have I tested for common programming errors?
Have I exercised all of the source code?
Have I forced all the internal data to be initialized and used?
Have I found all seeded errors?To check for functional completeness, testers might ask these questions:
Have I thought through the ways in which the software can fail and selected tests that show it doesn’t?
Have I applied all the inputs?
Have I completely explored the state space of the software?
Have I run all the scenarios that I expect a user to execute?
프로그램 소스코드를 testable 하게 개발하는 것도 쉽지는 않겠지??
참고.
Roland Untch’s Storm Site
Bret Pettichord’s Software Testing Hotlist
Brian Marick’s Testing Foundations
