TrainingConferencesAbout UsContact UsAdvertiseSQE.com

StickyMinds.com: brain food for building better software

Join

Join

Clarify Your Search Criteria
Tips on Using Our Search Feature(s)
StickyMinds.com Home
ResourcesEventsTopicsPowerPassJobs
Software Testing & QA Online Community  >  Detail: Becoming a Testing Expert



A StickyMinds.com Original
Article Picture
Becoming a Testing Expert

By James Bach

Send This Content to a FriendGet a Short Link to This ContentPrint This ContentSee User Comments About This Content

Summary: Achieving expertise as a tester is a progressive journey. It helps to have a vision to guide your efforts. James Bach, a well-known name in software testing, shares his vision of expertise and provides a testing challenge for those aspiring toward expert status.


Tricentis
One of the paradoxes of hiring good entry-level testers is that some of the very people who are good at finding fault, find so much fault with themselves that they assume they are unqualified to be testers. We never see their resumes.

What we’re left with, a lot of times, are candidates who are overconfident in their ability to find good bugs. The same holds true for conference speakers. I’ve met dozens of interesting people at conferences who have helpful advice and interesting experiences. But when I encourage them to get up and speak or to write an article, most of them say, “Well, I’m not an expert. I don’t know the right answers. I haven’t read all the books.” Valuable insight thus remains bottled up inside the self-skeptical minds of many excellent testers, while too many people who do speak and write could stand to put their ideas through a little more testing.

I fancy myself a good tester. I could be wrong about that. Ask me in another fifteen years. What I know as the truth is that I am working toward expertise. How do I keep myself moving along that path? A vision helps. For all of us who aspire to expert status, we need a vision of expertise that stirs our hearts and sets a high standard, yet seems achievable in one lifetime.

A Personal Vision
I can test anything, under any conditions, in any time frame…

This may be a nice start. The problem is that it’s not achievable. For instance, if people don’t like me, or have a different view of what good testing means, then I will not be able to perform well on that project. If I don’t understand enough about the technology I’m testing, my test design will be weak. If I don’t try very hard, I will do mediocre work. So, this vision needs a few qualifiers.

Let’s add:

…to a degree relative to…

  • my standing in the local process culture
  • my knowledge of the relevant technology
  • how much I want to succeed
That goes a little way toward making the vision more realistic, but it still seems overreaching. Where is the quality standard? After all, I can do anything, as long as I’m allowed to do it badly. How could you be true to this vision, and test well, if someone asked you to test a nuclear power plant in five minutes? To deal with that problem, let’s add some more specific assertions about expertise:

…such that…

  • I perform at least as well as another expert would
  • I deliver useful results in a usable form
  • I choose methods that fit the situation
  • I make appropriate use of available tools and resources
  • I collaborate effectively with the project team
  • I can explain and defend my work
  • I can advise clients about the risks and limitations of my work
  • I can advise clients about how my work could be even better
  • I faithfully and ethically serve my clients
  • I become more expert over time
Now the vision is within the realm of possibility, even though it’s quite a challenge.

In this view of expertise, “I can test” really means “I can perform well as a tester.” This is measured by a human standard: the behavior of the best experts we can find. With that standard in mind, how would experts react to the problem of testing a nuclear power plant in five minutes? Answer: the people I most respect would begin by invoking one of the great tools of testing—questioning the constraints of the problem. The best five minutes of tester behavior, I think, would be to ask “What’s going on here?” or some question like that. Or in this particular case, perhaps, “Are you out of your mind?” which highlights the absurdity of the constraints.

Practically speaking, embracing a vision of the best standards is to make a habit of looking at any product and wondering “How would I test that? What if I had to test it without a spec? What if I had to test it in half the time?”

With that in mind, here’s a testing challenge for you. Six years ago, I wrote a little Windows program for use as an exercise in my testing class. I still use the program today. I give students fifteen minutes to test it. If I gave you only three minutes to evaluate it and tell me if it’s good enough, what would you do? I can think of four different answers that an expert tester might provide…

Think about it. If you want my answer, see http://www.satisfice.com/answer1.htm.

About the Author
James Bach is the founder of Satisfice, Inc., a test training and consulting company. A pioneer in the emerging disciplines of Good Enough quality and exploratory testing, James specializes in expert testing under chaotic conditions. James is coauthor (with Cem Kaner and Bret Pettichord) of Lessons Learned in Software Testing. He can be reached at james@satisfice.com.

Back to Top
 

StickyMinds.com Weekly Column From 1/21/02 


Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Rajdeep Singh 8/6/2012

Hi James,

I have read all the articles on your website "www.satisfice.com'
I really appreciate the knowledge that you have shared on that site. It is really useful to people who wants to adopt RST in their firms

 
 
Comment:    
by rahul rohitashwar 6/26/2011

Hi
I am a beginner in testing field.So for exploring my knowledge i need some help from u.Can u suggest some book to get better knowledge


With Best Regard
Rahul Rohitashwar

 
 
Comment:    
by Adeel Shoukat 6/16/2011

Hi James you are doing a good job in testing can you please tell uss a little bit about automation testing and its basic concepts.As i am new in automation testing and need some expert guidance.

Thanks
Adeel


 
 
Comment:    
by Kavitha Parameshwaran 11/25/2009

Hi James,

thanks for giving an excellent article. to tell about myself, i hold four years of experience in testing and would like to know from you how can i mould myself for the future levels..

 
 
Comment:    
by Hongxin Zhang 1/25/2002

James, thank you very much for such an excellent article. I am working as a QA for up to one year. I did fine here but I always thought that I may not be able to do the testing work if I go to a different company to test some product which I know nothing about. I always believe that the most important thing for testing is the knowledge of the product you are testing. To create excellent use case is the essential fact for testing. If someone has a very good understanding of the product even if he does not know a lot of testing skills he can still do the work. But if someone know nothing about the product , even if he has a lot of testing...Read On

Author's Response:
1/28/2002    
When I am totally new to a project culture, or company, or technology, problem domain, my vision of what it means to be an expert compells me to find people who know more than I know about it and learn from them. I rate myself more highly as a testing expert the quicker I can swallow my own technical pride and become someone else's student when necessary. Part of being a testing expert, I think, is to be very good at rapid self-education. Good testers are always learning. So, the fact that you are aware that your expertise is contingent on your environment, and that a change in that environment reduces your expertise, is a good sign. See my brother's article "Playing the Expert Game" for more on this. It's posted at http://www.satisfice.com/articles/expert_game.pdf.

 
 
Comment:    
by Hain Joubert 1/25/2002

Hi James !, I am one of the entry level testers you talked about. Just started in our companies test department . I know you won't like to hear this but I moved from the development department purely because of my great interest in testing. I know the lingual that developers don't make good testers. I am a very critical person and and love to evaluate things objectively. What advice would you give any novice apart from setting a goal and establish a vision ? I know reading as much as you can is a must!

Author's Response:
1/25/2002    
I also began life as a programmer. Former programmers can make great testers. I eagerly switched to testing because I was never satisfied with my work, and I thought it was cool to be *paid* to be unsatisfied. For an entry level tester, the best thing is practice, and watching other people practice. As for reading, I really don't think there is a good testing book for novices, yet. But there are a lot of non-testing books that are great for novice testers: Exploring Requirements, by Weinberg, The Design of Everday Things, by Norman, Tools for Critical Thinking, by Levy, and Proofs and Refutations, by Lakatos. Also, of course, the more you learn about the technology you're testing, the better able you will be to predict likely failure modes and investigate bugs.

 
 
Comment:    
by Robert E. Lee 1/23/2002

I'd like to comment on Rob Pecor's question of TEAM expertise. If you have the advantage of a team of testers, I recommend holding test design [or test script] walk-throughs with 3-5 reviewers, a presenter and a moderator. Walk-throughs are an amazing vehicle for discovering and spreading Best Practices [or at least BETTER practices] and discovering and shunning bad practices that otherwise keep being reused. Everybody gets a chance to share their pride & joy with others having the same interest area. If you don't have a team, at least arrange to review cross-project with other testers. You'll be amazed how good ideas start to...Read On

Author's Response:
1/24/2002    
I once was suspicious of team learning. I shunned it, because I thought it meant we all had to learn the same lessons at the same time. A startling experience, several years ago, of learning from someone who knew far less than I did (at least in some dimensions of knowledge), showed me that I can learn from a team without being tethered to the team. I can learn in my own way and my own pace, and also be part of a group. Now, I'm eager to join in team reviews and team testing sessions.

 
 
Comment:    
by Sreeram Kishore Chavali 1/23/2002

Taking Kaner's definition of tester in one of his articles, I set myself a goal that 90% of defects I report should be fixed. By setting this goal I consciously improved my methods of testing, reporting defects and tried to improve. By taking away focus on 'number of defects' as my productivity, the above goal has helped me become a good tester. Despite my conscious efforts to reach the goal my current statistics show 67% of defects I report are closed. Thought I would share the same.

Author's Response:
1/24/2002    
Be careful with that metric. You could be an excellent tester, yet stuck in a bad project, and your fix metric would look very bad. Or if you only report "sure thing" bugs, your number will go up, and yet you might not report something that turned out later to be vital.

 
 
Comment:    
by cathy gault 1/23/2002

You might be an expert tester if: 1) your most satisfying moments as a kid were taking all those shiny new Christmas toys apart 2) the SUT becomes DOA after your done with it 3)you're both loved and loathed by the development staff 4) you've reached the testing zone — that Zen-like flow experienced only by experts 5) Joel Achenbach is one of your favorite authors 6) you realize all those degrees and certifications don't prove squat

Author's Response:
1/24/2002    
Speaking of authors, Cryptonomicon, by Neal Stephenson, is a great tester book.

 
 
Comment:    
by yogita sahoo 1/23/2002

Acquiring expertise (testing or in any other profession) is a progressive journey and also a non-ending one. I believe that - "Expert testers are born and not made". There are few characteristics common to all testing experts and surprisingly many of those are simple human qualities. A killer instinct, ability to criticize your own mistakes, rectify self, vision-driven, urge to excel etc. etc. I like your vision statement. A personal vision should always be something you believe in, simple and achievable. Interesting reading, James !!!

Author's Response:
1/24/2002    
Hi Yogita. There is a substantial talent component to good testing, and also a temperament component. My wife is good at many things, but anything remotely like testing drives her crazy. If I accidentally bring my skeptical and scowling tester mentality home from work, she stops speaking to me until I become friendly again.

 
 
Comment:    
by Jessy Muks 1/22/2002

Hi James, This is more of a question, to become a good tester, will you necessary say – A person has to be good at software and hardware testing or either? Also if ones testing skills is restricted to either structural or functional testing, can one necessary say that individual is an expert, even though there are good at one aspect of testing. Also if an environment offers only one aspect of testing in your view will you advice a tester to try and develop their skills by acquiring a wider range of testing techniques. I may be wrong here, but I find quiet a lot of environments concentrate mainly on functional testing. Also because of...Read On

Author's Response:
1/22/2002    
The section that starts "to a degree relative to" is there to remind you that expertise is contingent on the context. If I know a lot about databases, I will be a more expert tester of databases than of something I don't know, like protein modeling software. I am more an expert in some kinds of testing than others, but I also make general progress toward a broader expertise by studying different technologies, techniques, and process cultures, over time.

 
 
Comment:    
by Rob Pecor 1/22/2002

Great article as it pertains to the individual, however one cannot be great if acting alone. I would like to see a further thought on this, as to how to make a TEAM of testers become experts. Testers who constantly worry about themselves and their expertises only become experts as yes-men and narrow minded testing. Testers who naturally become experts because they want to ensure Quality, become the real experts. If you are concerned about Quality, and overall believe in your project and its outcome, becoming an expert is a side-effect. If you just go through the motions, and test what is tasked of you, you will never succeed as an...Read On

Author's Response:
1/22/2002    
Good point. I have found that team skills help me not only be a better tester on a given project, but I learn much faster by watching other people, even people who are not as "expert" as me.

 
 
Comment:    
by Diane Albert 1/22/2002

Excellent article James! I really hadn't predicted the outcome of your 'answer'. I expected solutions and was unprepared for the very tactful way you've placed the concern back to initial party; which in this case, really IS the solution. The attitude of 'yes I can do something on your behalf, HOWEVER...' is an eye-opener to those of us so new (I'm between 3-5 years experience) to the test profession. I have to remember that my squeaky-fresh test enthusiasm must sometimes be tempered by reality - or as you've stated Time, Conditions, and Understanding. At times it seems the uphill climb to that "expert" level will take forever; and then...Read On

Author's Response:
1/22/2002    
Sometimes the most important thing we can do as testers is make a tactful explanation of life's little realities.

 
 
Comment:    
by George Wilkinson 1/22/2002

Although an interesting article, I would add to the 1st goal that James has listed, i.e. “I perform at least as well as another expert would 'in my domain'.” Just to make the goal that bit more realistic. And picking up on the advising client goal...what's the definition of clients, external or internal? A tester also needs to advise internal clients as well as external. Essentially that's the main crux of the job, advising, as I see it. Especially as we are usually the first to properly execute the software on the target platform. All in all, I find it a little difficult to measure the job of a tester in terms of standards, since the...Read On

Author's Response:
1/22/2002    
I like your addition, though I'd prefer the wording "in the same situation." By client I mean anyone who is a consumer of testing services, whether internal or external. Since, as you say, testers are in an advisory job, they are essentially internal consultants to a variety of clients.

 
 
Comment:    
by Krishna Rajan 1/22/2002

from where i come, testing is done in at least two distinct stages - planning and execution. experience has led me to believe that the effort is almost equal. So if you are saying 1.5 minutes to plan and 1.5 minutes to test, i would say 'pass'.

Author's Response:
1/22/2002    
One of the most important practices of a true expert is saying "pass" at the right times.

 
 
Comment:    
by Paul Tsuda 1/21/2002

Hi James. I am a fan of your articles and books. I just got done with Lessons Learned in Software Testing, read it backwards and forwards, and it was worth every minute. The point you make in the article is a good one. We don't achieve at the highest levels unless we strive for it. Like an old mentor of mine once said, 'aim for the stars, and if you hit the lamppost at least you got that far.' In my company, where subscriber management/billing software is developed on a contract basis for cable television companies, becoming an expert has a heavy subject matter expertise element to it. I've noticed that some of the best testing is...Read On

Author's Response:
1/22/2002    
Hi Paul, thanks for the kind words! I didn't have the space in this article to go into the specific skill areas of testing (bug reporting, test design, test techniques, etc.). But I'm glad you pointed some out.

 
Back to Top



 
Ads By Google
What's This?
 
 



About Us   |   Contact Us   |   Terms & Conditions   |   Privacy Policy   |   RSS Feed



© 2013 StickyMinds.com. All rights reserved.
ASTQB

Tricentis



Agile Development Conference & Better Software Conference West