The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.06 - Nov.-Dec. (2012 vol.29)
pp: 70-77
ABSTRACT
The lowly test plan is perhaps the least appreciated of all supporting (read: noncode) software development artifacts. All projects need one, but few engineers appreciate their existence. So it's important to spend no more time than is absolutely necessary in the creation, care, and feeding of the test plan. Ten minutes, to be precise.
INDEX TERMS
Software testing, software testing
CITATION
James A. Whittaker, "The 10-Minute Test Plan", IEEE Software, vol.29, no. 6, pp. 70-77, Nov.-Dec. 2012, doi:10.1109/MS.2012.25
REFERENCES
1. IEEE Std. 829: Software Test Documentation, IEEE, 1998.
2. K. Beck, Extreme Programming Explained, 2nd ed., Addison-Wesley Professional, 2004.
3. A. Cockburn, Writing Effective Use Cases, Addison-Wesley Professional, 2000.
4. J. Winsor, "Crowdsourcing: What It Means for Innovation," Business Week,15 June 2009, http://innovbfa.viabloga.com/filesBusinessWeek_Crowdsourcing_What_it_means_for_Innovation_june_2009.pdf.
5. J. Whittaker, How to Break Software: A Practical Guide to Testing, Addison-Wesley, 2002.
6. J. Whittaker, , Exploratory Software Testing: Tips, Tricks, Tours, and Techniques to Guide Test Design, Addison-Wesley Professional, 2009.
7. W. Harrison, "Eating Your Own Dog Food," IEEE Software, vol. 23, no. 3, 2006, pp. 5–7.
707 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool