Better Software - December 2008 - (Page 47)

The Last Word The Abolition of Ignorance by Alan Page I’ve been a software tester for more than fifteen years, but I still remember when I realized I didn’t really know anything about testing. It’s not that I was a bad tester. I found a ton of bugs, I used automation and other test tools appropriately (most of the time), and I received great feedback from management. Despite these signs of success, three or so years into my testing career, I decided I would like to study testing. Since I was getting to a point where I thought testing may actually become a career for me, I decided I wanted to learn more about the hows and whys of testing and build a formal base of knowledge. I started by reading a book on testing that a colleague recommended. In many ways it opened my eyes. I felt that the knowledge I gained from this book, combined with my experience, would make me some sort of “super-tester” (it didn’t). A few weeks later, flushed with success, I read another book on testing. I enjoyed reading the second one, too, but it stressed different practices and even contradicted the first book in places. Now, I was confused. By the time I completed a third book on testing, two things happened. The first was that I realized not every book on testing was very good at teaching testing. The second was that I began to form my own opinions on what works and what doesn’t when testing software. I’ve read dozens of books and thousands of articles since then on testing and on software engineering, and all I’ve figured out from all this reading is that I’ve barely scratched the surface of what there is to know about testing. I question much of what I read now— not necessarily as a skeptic who thinks that none of this stuff really works in practice but as a learner who wonders how the ideas might apply to situations I have experienced or could imagine. Theory isn’t enough when you’re trying to make a career out of testing software. So I try things. I experiment. The more I learn through reading it-all kind of way but in a and practice the more Theory isn’t enough way that relies only on the I realize how much knowledge they have today there is still to learn in order to test each new and how many undiswhen you’re trying to piece of software that comes covered paths remain their way. The state of the art for me to explore. in test has not kept up with make a career out of Phillip Armour first advances in product design wrote about the five and implementation because orders of ignorance testing software. too many testers have stayed (5OI) in 2000 [1]. The inside their 0OI comfort 0th order of ignorance zone when their true place in (the orders are 0 based, of course, be- the food chain is 3OI. Too many testers cause Armour is a programmer) is lack think that they “get” testing or that they of ignorance. You have 0OI when you know “enough” to do the right thing. know something (“I know how to speak If you think you have testing all figured English”). The 1st order of ignorance is out, you are part of the problem! lack of knowledge. You have 1OI when The 3OI processes, of course, conyou know you don’t know something tribute new knowledge to software en(“I know that I can’t speak Chinese”). gineering, but the consummate 3OI proThe 2nd order of ignorance is lack of cess is the critical thinking of intelligent awareness. You have 2OI when you are and experienced testers. Testers who can unaware of what you don’t know. The navigate the unknowns of 3OI will el3rd order of ignorance is lack of process. evate the science and craft of testing to You have 3OI when you don’t even have a level it deserves but too often does not a way to figure out what you don’t know. enjoy. The greatest testers I know realize The final level of ignorance—meta igno- there is much more to learn about testing rance (4OI)—is when you don’t know than they know today. They know that about the levels of ignorance (a level of there are questions they haven’t thought ignorance that readers of this article can of yet and know that there will always cross off now). be new means to discover these quesWhen I first heard of the five levels of tions. They never assume that they know ignorance, I realized that testing lives at “enough” about testing to always make 3OI and 2OI. Our job in examining soft- the best choices. Obviously, if you are ware is to figure out what questions to reading this article, you have some inask about the software and then to de- terest in learning more about testing, but termine what the answers are. Chances how often do you challenge yourself to are that the programmers with whom discover something new about testing? you work don’t write your test cases for Do you have a vision of what software you or suggest, for example, that you testing can become and strive toward “try a really big number in this field.” that vision? Or do you think that merely Instead, we testers examine the software, repeating and refining what you’re alhoping to learn enough about it to ask ready doing is enough? that question, and subsequently, find the A passion for learning drives the answer. Our job as testers isn’t to find work of every great tester I know. What bugs; it’s to find knowledge! drives you? {end} The more I think about this, the more reFerenceS: concerned I get about testers who live Armour, Phillip G. “The Five Orders of Ignoentirely at 0OI and think they know all rance.” Communications of the ACM, October the answers—not in a snobby, know2000/Vol. 43, No. 10. www.StickyMinds.com DECEMBER 2008 BETTER SOFTWARE 47 http://www.StickyMinds.com

Table of Contents Feed for the Digital Edition of Better Software - December 2008

Better Software - December 2008 Contents Mark Your Calendar Contributors eLightenment Technically Speaking Code Craft Test Connection Management Chronicles What's a Manager to Do? Six Thinking Hats for Testers The Key to Good Interviewing 2008 Salary Survey Product Announcements 10 Things You Might Not Know About … The Last Word Ad Index

Better Software - December 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.