TrainingConferencesAbout UsContact UsAdvertiseSQE.comRSS Feed

StickyMinds.com: brain food for building better software

Log In
 Clarify Your Search Criteria

Tips on Using Our Search Feature(s)
 
StickyMinds.com Home
ResourcesTopicsCommunityPowerPassBlogs
Home  >  Detail: How Do You Think?



A StickyMinds.com Original
Article Picture
How Do You Think?

By Fiona Charles

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

Summary: What are the attributes of a good tester--of a great tester? As every test manager knows, identifying the right people for a test team can be a struggle. In this week's column, Fiona Charles describes the qualities of mind she looks for in testers, and the interview questions she asks candidates so that she can evaluate how they think.


Jama Software
When I am staffing a test team, I look for testers with genuine skills—both testing skills and soft skills. Neither of these are straightforward or easy to find or evaluate, especially within the time constraints of an interview.

Beyond skills, I look for people with the right qualities of mind. For me, these include:
  • Real enthusiasm for testing
  • Judgment
  • Analytical ability
  • Creativity and problem-solving skills
  • Critical intelligence: curiosity and skepticism
Paper qualifications—whether tester certification, post-secondary education, or testing courses—don't tell me anything about a candidate's possession of these qualities. I could learn something by asking the person to solve a puzzle, or to demonstrate how she would test a given piece of software, but I'm wary of a one-size-fits-all approach to evaluating people. We all need to be aware that different kinds of intelligence manifest in different ways.

So I try to engage candidates in conversations that make them think. I work to move people away from their prepared answers to a conversational territory where they will reveal not only how they think, but also the qualities they truly value in doing the tester's job.

Gauge a Candidate's Feelings
I start with a couple of simple questions: Do you like testing? What do you like about it?

Every candidate will claim to like testing, but the answers tell me whether or not it's worth going on with an interview. Some people light up when I ask those questions. Others don't show any spark at all.

There is no one right answer. A passionate concern for users is valuable, even more so when it is coupled with glee in finding bugs and pursuing difficult clues. Good candidates display enthusiasm, searching curiosity, and a sense of joy Some people don't even seem to like software, let alone testing.

I also look for judgment in evaluating risk. I want testers who care about more than whether the software matches the written requirements. A tester needs to know that some requirements might matter more than others, and that half of the real requirements might never have been written down. If a candidate talks about risk-based testing, then she'd better go beyond the buzzwords and demonstrate a real understanding of what it is and how to accomplish it.

Delve into Work and School Experiences
Evaluating analytical skills or problem-solving abilities is not easy. I try to do this by asking testers how they approach problems. I pose a hypothetical problem and ask the candidate to suggest ways to solve it. I also ask for a specific example of a difficult testing problem the candidate has solved and the method she used. Again, there are no right answers. I'm looking for a sense of method, but also for creativity and the flexibility to adapt an approach to different circumstances. I'm especially interested in people who know what a model is, and why it might be a useful tool in analyzing and solving problems. I'm even more interested in candidates who understand that models have limitations.

Candidates must also possess critical intelligence. One indicator of critical intelligence is a candidate's description and assessment of the various sources of project information. I ask interviewees to give examples of the sources they've dealt with and others they know of. What issues did they encounter in getting and evaluating information? Were all sources equally credible? If not, what did they do about that? How might they cross-check different sources?

Finally, knowing what a candidate has studied or done in a former life can help guide interview questions that show her qualities of mind.

Take formal education. Academic studies at any advanced level require problem solving, at least in principle. I expect people with academic credentials to be able to talk about their studies, not only in terms of how the work might have prepared them to test software but also in terms that show me how—or if—they think and how they generally approach problems. Their answers will also tell me the qualities and skills they believe to be valuable for a tester.

A good tester should be able to provide an interesting analysis, even if it has never occurred to her to think this way before.

If someone were to ask me how my university studies in English language and literature helped equip me to be a tester, I would say that it's the passionate study of literature that's of interest, and the development of skills to pursue that study. A poem or a work of fiction is both a system and a model, just like a software system. Natural language is a symbolic system, used within various formal constraints to construct literature.

Studying both language and literature require analytical thinking and conceptual modeling. You need the ability to dig out sources of information and think critically about their reliability, and to construct and test hypotheses. You must have the imaginative reach to get inside someone else's view of reality and also to understand the historical context of a different period.

I expect candidates to be able to talk about the testing they've done in a similar way. Whatever we talk about, I want to see a zest for thinking and problem solving. I want candidates to display the ability to know what a metaphor is and why it might be useful and important to a tester. I want to see tenacity and healthy skepticism in that person as well.

The question that drives the entire interview is "How do you think?"

It's the conversation that really makes the difference. Because I work to get candidates to think and to talk enthusiastically, it's hard for them not to reveal what I want to know.

All of this makes for an enjoyable interview process. And when I do finally meet the successful candidate, the interview helps establish a foundation of trust and understanding for the future working relationship.


About the Author
Fiona Charles is an independent test project manager and consultant, based in Toronto. With over twenty-five years of experience in systems development and integration projects, she specializes in managing large-scale systems integration tests, and in test management at the program level on multi-project integrations. Fiona is on the board of the Toronto Association of Systems and Software Quality and co-founder and host of the annual Toronto Workshop on Software Testing (TWST). She is a regular contributor to StickyMinds.com and Better Software Magazine. Contact Fiona at fccharles@sympatico.ca.

Back to Top
 

StickyMinds.com Weekly Column From 3/26/2007 

Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Charles Taylor 7/6/2007

I agree with the 'how do you think' concept. I have two other comments, coming from managing a pretty large (50 testers) group for many years:

1. I found a mix of people most effective, allowing me to assign people to tasks they were suited for: the detail people, the intuitive people, the developer people, etc. Sometimes you need a system engineer, sometimes a geek, sometimes you just need a person who is really good at communicating with both developers and managers.

2. Often musicians make excellent testers.

Author's Response:
7/8/2007    
I too like to have a mix of skills and backgrounds on my teams, whether they're large or small teams. Your comment about musicians is really interesting! (I've worked with a number of musicians, and found that they often make excellent developers as well.) Why do you think musicianship might especially fit a person to be a good tester?

 
 
Comment:    
by jaideep khanduja 7/4/2007

hi,
i being head of quality assurance in a software company fully agree with the qualities you mentioned. one more quality i would like to add is "intuitive". i have seen many excellent developers having zero percent flair or capability for testing and vice versa i.e. excellent testers, techincally sound too but not a good developer.
jaideep

Author's Response:
7/8/2007    
I agree that the right kind of intuition is a wonderful skill for a tester, and a really good tester will develop his/her intuition with experience of different kinds of bugs. I'd be interested in hearing the kinds of questions you would ask in an interview to evaluate a tester's intuition.

 
 
Comment:    
by Dharmesh Kumar Mehta 6/12/2007

It is a very interesting article.I just started my carrer as Qaulity Analyst,when i was interviewed similar question were asked.I believe that qualities as u discribe in your article is necessary to be a very good tester.

 
 
Comment:    
by Sanat Sharma 5/9/2007

Good article about how to hire a good tester or infact a great tester. But I think these are the theoritical concepts of interviews. What I believe is that interview is totally a runtime sync activity between the interviewer and the interviewee. Its not necessary that the interviewer is more intelligent than the interviewee. The only thing that should be taken care by the interviewe is to satify the interviewer at any cost. The interviewee should try to keep the discussion according to his knowledge or understanding.

I agree with the author's view about all the attributes that one should look for while hiring some person for...Read On

Author's Response:
7/8/2007    
A live interview is fundamentally unpredictable, just like any genuine human interaction. But I find it useful to have a theoretical framework in mind, so that I at least get the kind of information and impressions I'm looking for.

 
 
Comment:    
by Srinivasan Desikan 4/2/2007

It is a very good article. Not taking any credit away, I would like to add my comments disagreeing to few statements by the author and other readers. Having development skills for testing is desirable and in some cases it is a MUST. There are some good testers who do not have development skills, and that is fine, but "testing team should not become a dumping place for people rejected by development". Testing is an engineering discipline and development skill is one of the basic skills in software engineering. The people in testing teams should understand that they are equal to developers and they should work towards creating credibility for...Read On

Author's Response:
4/5/2007    
I'm not sure you're disagreeing so much as extending the comments we've made. I think you're absolutely right in saying that testers need development skills for certain kinds of testing.

I would say though, that while we don't want anyone's "rejects" per se, it's important to note that people who may not have been suited to one job or role (for a variety of reasons) could shine in another, and develop all the right skills as a consequence of doing something that makes them happy.

 
 
Comment:    
by Susan Thompson 3/27/2007

I think that a grasp of epistimology comes into it (how you know what you know), regardless of whether the candidate knows the word. I think that that is more important than experience as a developer or a tester. I have seen novices with a grasp of epistomology test rings around people with a plodding "following orders" mentality.

Author's Response:
3/27/2007    
Save us from the plodders!

 
 
Comment:    
by Sidney Snook 3/27/2007

I agree with your insight into what makes a good tester. However, there is one additional aspect you have not mentioned that I consider critical. It is my experience that to be a "good" tester of software the tester MUST have had some experience actually developing software...the stuff they are going to TEST! I view my experience as an accumulation of the mistakes I have made... and in 40+ years as a software developer and test engineer the list is long. There is no substitute for first-hand knowledge of creating "bugs" during development.

Beyond this the most important thing for a tester is attitude...I was a software...Read On

Author's Response:
3/27/2007    
I agree that development experience can be very valuable in a tester who also has the right qualities and skills. But great testers can also have non-development backgrounds. I started as a technical writer, and I've hired many terrific testers who'd never written code. I find that the best teams usually have people with varied experience.

 
 
Comment:    
by Natarajan Ramanathan 3/27/2007

This article and the 1st comment that came after the article are bang on target. Like my eyes lighted up when I read the article and comments.

I have done lots of interviews my self in a domain area and can vouch for few things : (a) Demonstrative applied knowledge of the domain to the extent that the role requires - at the minimum. Theoretical answers are ok, but applied knowledge is what I look for ; (b) How does a person react when a particular complex or tricky question is asked - that is why telephonic interviews sometimes can throw up wrong 'uns; (c) Aptitude and Attitude - are the keys. When interviewers compromise due...Read On

Author's Response:
3/27/2007    
I had a couple of disastrous hires before I learned not to compromise.

 
 
Comment:    
by Robert Rose-Coutre 3/26/2007

This may be controversial or unorthodox, but my experience says the content of the questions asked is not as imporant as the complexity of the questions -- questions that require the interviewee to think. The interviewee's answers will reveal aptitude (high or low) for understanding and formulating complex concepts. That is the first quality I want to verify.

Secondly, you want some experience or education relevant to the job responsibilities, but this is only a secondary consideration. I wouldn't hire anyone with tons of experience who can't formulate or grasp complex concepts! That would leave me with someone who won't be as...Read On

Author's Response:
3/26/2007    
Thanks for your comments Robert. My experience is very similar to yours. I too have had far better success hiring on the basis of intelligence over experience or paper qualifications. Re the content of questions, I find questions that are unexpected or outside a candidate's direct work experience are those most likely to stimulate thinking.

 
Back to Top



 
Ads By Google
What's This?
 
 



Home   |   Resources   |   Topics   |   Community   |   PowerPass



© 2010 StickyMinds.com. All rights reserved.
StickyMinds.com is a division of Software Quality Engineering.
Privacy Policy    Terms & Conditions    Link to StickyMinds.com    Feedback


HP Software

Infosys




STAREAST 2010 


Better Software Conference