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
ResourcesTopicsCommunityPowerPass
Home  >  Detail: Join the Club



A StickyMinds.com Original
Article Picture
Join the Club

By Linda G. Hayes

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

Summary: Test automation tools promise big returns, but require a large, up-front investment. It takes a significant amount of work and time to implement a tool. In the same way that infomercials peddling exercise machines lure customers with the promise of a statuesque physique minus the long workout times, testers are lured to automation tools by the prospect of immediate gain without too much work. In this column, Linda Hayes offers her coaching skills to help you start utilizing all those automation tools you thought you'd never have time to use.


MKS, Inc.

Recently I was reminded--yet again--that buying a test automation tool is like joining a health club: The only weight you'll lose is in your wallet. Once the initial euphoria wears off, you realize you actually have to use the tool! At a health club, that means making the time to go there, learning the equipment, and then working out. And they don't call it work for nothing; you have to sweat it out, hour after hour and day after day. It takes time before you see results.

With test tools, you have to set aside time to learn the tool and expend the effort before you can enjoy the benefits. And, like treadmills gathering dust in the corners of our homes, test tool shelfware is abundant.

Set New Habits

What reminded me of this analogy was a customer who had made a substantial investment in test automation. Despite initial enthusiasm, he was struggling to roll it out. He explained that the issues weren't technical, but cultural. It was proving to be more challenging than he expected to persuade manual testers to take advantage of automation. Their work habits were so ingrained that, even though they intellectually believed in the benefits of automation, they could not seem to overcome their inertia.

In their defense, the manual testers were too busy to try something new. People don't buy test tools out of boredom, they buy them because they can't get their jobs done in the time they have. This creates a dilemma: How do you spend time to save time?

Get Motivated

The customer was asking for the equivalent of a personal trainer--a consultant who is an expert in automation to work with the team, side-by-side, to get them going. Not only could this expert teach them best practices for maximum results, her mere presence (and the implied meter running) would be a motivator to set aside time.

While this sounds attractive--for the same reason a personal trainer does--there is a caveat: Too often, test automation consultants end up actually doing the work because the customers are so busy. This may look like progress in the short term because tests are being automated, but in the long term the consultant won't be around and you'll be back where you started. It’s like having the personal trainer work out for you instead of showing you how; it’s easier, but you won't get in shape.

Is this happening to you? Do you have test automation tools on the shelf? Have you invested in consultants, only to train them on your application instead of getting yourself trained on automation? If so, here are some guidelines for working out your applications:

  • Never forget that a tool is only a tool. Someone has to use it for it to be useful. Don't just allocate budget to buy it; set aside the time to use it. If you're already busy, then either dedicate specific resources to automation or set aside certain days of the week or hours of the day to devote to automation.
  • Don't skimp on planning. You know the saying: If you don't have time to do it right, how will you find time to do it over? If you rush into automation just to show activity quickly, you will have plenty of time to regret it.
  • Use consultants wisely. Remember that they are there to train you, not the other way around. Have them work with you, not just for you. Insist on understanding everything they do.
  • Accept gradual progress. Anyone can tell you that long-term weight loss happens slowly and gradually, and the same is true of automation. Look for high-value test cases--usually those that are repetitive but not necessarily complex--and automate them first. Then reinvest the time saved into more automation.
  • Know when to say no. If your process is a mess and your team is under stress, wait until you can get your house in order and catch your breath before you tackle automation.

By observing these simple rules, you can get your automation tools off the shelf and whip your application into shape.



About the Author
Linda G. Hayes is the CTO of Worksoft, Inc., developer of next-generation test automation solutions. She is the founder of three software companies including AutoTester, the first PC-based test automation tool. Linda holds degrees in accounting, tax and law and is a frequent industry speaker and award-winning author on software quality. She has been named as one of Fortune Magazine's People to Watch and one of the Top 40 Under 40 by Dallas Business Journal. She is a regular columnist and contributor to StickyMinds.com and Better Software magazine, as well as a columnist for Computerworld and Datamation, author of the Automated Testing Handbook and co-editor of Dare to be Excellent with Alka Jarvis on best practices in the software industry. Her article "Quality is Everyone's Business" won a Most Significant Contribution award from the Quality Assurance Institute and was published as part of the Auerbach Systems Development Handbook. You can contact Linda at Linda@worksoft.com.

Back to Top
 

StickyMinds.com Weekly Column From 05/01/2006 

Member Comments
Add Your CommentExpand Comments
 
Comment:    
by Alan Reese 5/12/2006

Linda, excellent article. “Spot on” with respect to automated functional testing. Too many people, in their "uninformed optimism", think “test automation” is the silver bullet to solve their testing woes. Typically, nothing is farther from the truth. As you stated, automated functional testing can be an effective strategy in some cases, but the implementation effort should never be under-estimated. Automated test tools are quite challenging to implement successfully, thus their widespread reputation for becoming “shelfware”. Automated test tools and the associated implementation effort...Read On

Author's Response:
5/12/2006    
Thanks for your expansion on the theme, Alan. You are obviously experienced and educated with automation! I like your distinction between automated and automatic - I actually wrote a column about that once.

 
 
Comment:    
by Jiadong Zhu 5/5/2006

Linda, I like the “Accept gradual progress”. Manual QA most often would like to see results/benefit (find bugs) immediately while using the new Automation Tool. In China, we call this as “swallow dumpling”. Like you said, automation should be treated as a special dumpling and chewed gradually. Explore it step by step and maintain it period by period. Confidence may be helpful.

Author's Response:
5/5/2006    
Thanks Jiadong. Spoken like someone with experience! A corollary is "If you don't have time to do it right, how will you find time to do it over?".

 
 
Comment:    
by Danny Faught 5/4/2006

Linda, I love the personal trainer analogy. When I do short consulting gigs where test automation is involved, I make sure to set the proper expectations about how the testware will be maintained in the long term. In one case, after a few days of demonstrating different types of tools, the client realized that they weren't ready to use more than the most basic types of tooling. We stopped there, and saved the client a lot of money and frustration.

Author's Response:
5/5/2006    
Thanks, Danny. You are right to set expectations up front for what THEY are able to do because in the end they are the ones who have to do it.

 
 
Comment:    
by Bill Middlebrook 5/2/2006

I think your article really touched on what we all need to remind ourselves in the SQE arena from time-to-time--level setting expectations around an automation project is as important as covering the basics. After all, who wants to see implementations become overstressed on the treadmill and then die on the shelf? Proper stretching, warm-up, good coaching and steady effort will help avert such set backs no doubt.

Author's Response:
5/2/2006    
Love the warm-up analogy, Bill! Too often we rush in, only to injure ourselves. For automation that would include getting your process house in order first.

 
 
Comment:    
by Sharan Karekatte 5/2/2006

Hi Linda: Once again an excellent article with great analogies to a health club. Commitment from management and discipline on behalf of the testers is key in making test automation a success. When testers are empowered by management to make the decision on the test automation tool and implement an automation plan the probability of success goes up significantly. Subsequently, discipline plays a vital role in ensuring that automation is used as much as possible to make tedious tasks fast & easy.

Author's Response:
5/2/2006    
Thanks, Sharan. I agree testers need management support both for choosing the tool and - especially - for making the time to implement it.

 
 
Comment:    
by Jim Hazen 5/1/2006

One thing that should also be mentioned is that it is not the Tester's who buy the tool, it is the management. Thus you will need their support and understanding on the points made about getting going on automation. Without their support automation can still become shelfware. It is an education process of what the the tool can and cannot do, what the tool should and shouldn't be used for, and who should and shouldn't be implementing it. By educating management you can lessen the risk of 'Caveat Emptor', and the Snake Oil that the tools salesman tend to wield.

Author's Response:
5/1/2006    
Good point, Jim, although in my experience the testers are usually involved in the tool purchase. Either way you're right - you need their commitment to spend the time.

 
Back to Top


Marketplace

Web based bug tracking - AdminiTrack.com
AdminiTrack offers an effective web-based bug tracking system designed for professional software development teams.

BugSplat - Automatic Crash Analysis
Fast online exception analysis. Capture customer crash data online.

Census: Web-based Bug Tracking and Defect Tracking
Track software bugs, defects, enhancements, support calls, and more. Issue tracking software that is scaleable, fully customizable and integrated with VSS. Includes e-mail notifications, role-based workflow, change history, and Crystal reporting.

New Webcast: How to Profit with Remote Support.
Discover how REMOTE SUPPORT can fuel your IT business in ways you've never thought of before.

Need Agile Test Cases?
Create statistically complete test cases simply and quickly.

Get your product or service listed here.
Subscribe to Better Software Magazine
Subscribe to Better Software Magazine

First Name:

Last Name:

Email Address:


Home   |   Resources   |   Topics   |   Community   |   PowerPass



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


Software Quality Engineering

Borland



STARWEST 2008

 
Agile Development Conference 2008