It now astounds me that
some individuals can spend years in a testing role and never read a
single book on the subject. I say 'now' because when I first started in
software testing I hadn't read a book on the subject either. In
fact, it wasn't until I had to start teaching software testing to new
testers at Microsoft that I began reading books on the subject in ernest
instead of just skimming through chapters in Kaner's book, Testing Computer Software.
When I thought the purpose of testing was simply to find bugs, I didn't need books on software testing to help me find bugs. I was very good at finding errors in Microsoft products (it really isn't that hard). But, as I matured in this profession, books on software testing provided me new perspectives on the application of time-proven techniques to help me become more effective and more efficient in my testing endeavors. Books on software testing presented diverse insight into various methodologies and approaches to solve problems improve processes. Books on software testing portrayed a breadth of information from a myriad of outlooks that enabled me to draw logical conclusions based on a wealth of industry experiences rather than from a limited (Microsoft-ish) view of testing based on personal trail and error in large market computer software.
Now, I read a lot of books on software testing. Some books are less than I'd expect, most are as dry as English humor, and there are a mere handful I'd consider great treatises on the subject of software testing. But, the important point is that I learn something from each new book I read. The good news is that today there is a plethora of books on software testing. (This is great compared to 10 years ago when there were but a few books that broached the subject.) But, for the folks who have chosen to enter into the professional discipline of software testing it is sometimes hard to know where to begin. To complicate matters a bit more, the books I recommend differ according to one's primary role in the organization. But, since most new testers (including those with CS degrees) receive very little formal education in software testing, I think it is important for all new testers (and developers) to become familiar with the basic techniques used in the practice of software testing.
This list of software testing books was compiled based on input from Test Managers and Test Architects at Microsoft as recommended reading for new testers at the company, and are books I constantly reference in our internal training.
1. A Practitioner's Guide to Software Test Design, Lee Copeland, 2003
2. The Art of Software Testing, 2nd edition, Glenford Myers, et. el., 2004
3. Software Testing Techniques, 2nd edition, Boris Beizer, 1990
4. How to Break Software: A Practical Guide to Testing, James Whittaker, 2002
5. Testing Object-Oriented Systems: Models, Patterns, and Tools, Robert V. Binder, 1999
http://blogs.msdn.com/b/imtesty/archive/2006/05/02/588125.aspx
When I thought the purpose of testing was simply to find bugs, I didn't need books on software testing to help me find bugs. I was very good at finding errors in Microsoft products (it really isn't that hard). But, as I matured in this profession, books on software testing provided me new perspectives on the application of time-proven techniques to help me become more effective and more efficient in my testing endeavors. Books on software testing presented diverse insight into various methodologies and approaches to solve problems improve processes. Books on software testing portrayed a breadth of information from a myriad of outlooks that enabled me to draw logical conclusions based on a wealth of industry experiences rather than from a limited (Microsoft-ish) view of testing based on personal trail and error in large market computer software.
Now, I read a lot of books on software testing. Some books are less than I'd expect, most are as dry as English humor, and there are a mere handful I'd consider great treatises on the subject of software testing. But, the important point is that I learn something from each new book I read. The good news is that today there is a plethora of books on software testing. (This is great compared to 10 years ago when there were but a few books that broached the subject.) But, for the folks who have chosen to enter into the professional discipline of software testing it is sometimes hard to know where to begin. To complicate matters a bit more, the books I recommend differ according to one's primary role in the organization. But, since most new testers (including those with CS degrees) receive very little formal education in software testing, I think it is important for all new testers (and developers) to become familiar with the basic techniques used in the practice of software testing.
This list of software testing books was compiled based on input from Test Managers and Test Architects at Microsoft as recommended reading for new testers at the company, and are books I constantly reference in our internal training.
1. A Practitioner's Guide to Software Test Design, Lee Copeland, 2003
2. The Art of Software Testing, 2nd edition, Glenford Myers, et. el., 2004
3. Software Testing Techniques, 2nd edition, Boris Beizer, 1990
4. How to Break Software: A Practical Guide to Testing, James Whittaker, 2002
5. Testing Object-Oriented Systems: Models, Patterns, and Tools, Robert V. Binder, 1999
http://blogs.msdn.com/b/imtesty/archive/2006/05/02/588125.aspx
No hay comentarios.:
Publicar un comentario