Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.

  • Apple
  • Android
  • Windows Phone
  • Android

To get the free app, enter your mobile phone number.

Kindle Price: £17.57

Save £16.42 (48%)

includes VAT*
* Unlike print books, digital books are subject to VAT.

These promotions will be applied to this item:

Some promotions may be combined; others are not eligible to be combined with other offers. For details, please see the Terms & Conditions associated with these promotions.

Deliver to your Kindle or other device

Deliver to your Kindle or other device

Implementing Automated Software Testing: How to Save Time and Lower Costs While Raising Quality by [Dustin, Elfriede, Garrett, Thom, Gauf, Bernie]
Kindle App Ad

Implementing Automated Software Testing: How to Save Time and Lower Costs While Raising Quality 1st , Kindle Edition

2.5 out of 5 stars 2 customer reviews

See all 6 formats and editions Hide other formats and editions
Amazon Price
New from Used from
Kindle Edition
"Please retry"

Summer Sale
Choose from over 450 books on sale from 99p. Shop now
Get a £1 reward for movies or TV
Enjoy a £1.00 reward to spend on movies or TV on Amazon Video when you purchase any Amazon Kindle Book from the Kindle Store (excluding Kindle Unlimited, Periodicals and free Kindle Books) offered by Amazon.co.uk. A maximum of 1 reward per customer applies. UK customers only. Offer ends at 23:59 on Wednesday, September 27, 2017. Terms and conditions apply

Product description

From the Back Cover

“This book fills a huge gap in our knowledge of software testing. It does an excellent job describing how test automation differs from other test activities, and clearly lays out what kind of skills and knowledge are needed to automate tests. The book is essential reading for students of testing and a bible for practitioners.”
―Jeff Offutt, Professor of Software Engineering, George Mason University

“This new book naturally expands upon its predecessor, Automated Software Testing, and is the perfect reference for software practitioners applying automated software testing to their development efforts. Mandatory reading for software testing professionals!”
―Jeff Rashka, PMP, Coauthor of Automated Software Testing and Quality Web Systems

Testing accounts for an increasingly large percentage of the time and cost of new software development. Using automated software testing (AST), developers and software testers can optimize the software testing lifecycle and thus reduce cost. As technologies and development grow increasingly complex, AST becomes even more indispensable.  This book builds on some of the proven practices and the automated testing lifecycle methodology (ATLM) described in Automated Software Testing and provides a renewed practical, start-to-finish guide to implementing AST successfully.

InImplementing Automated Software Testing, three leading experts explain AST in detail, systematically reviewing its components, capabilities, and limitations. Drawing on their experience deploying AST in both defense and commercial industry, they walk you through the entire implementation process―identifying best practices, crucial success factors, and key pitfalls along with solutions for avoiding them. You will learn how to:
  •     Make a realistic business case for AST, and use it to drive your initiative
  •     Clarify your testing requirements and develop an automation strategy that reflects them
  •     Build efficient test environments and choose the right automation tools and techniques for your environment
  •     Use proven metrics to continuously track your progress and adjust accordingly
Whether you’re a test professional, QA specialist, project manager, or developer, this book can help you bring unprecedented efficiency to testing―and then use AST to improve your entire development lifecycle.

About the Author

Elfriede Dustin, Thom Garrett, and Bernie Gauf work together at Innovative Defense Technologies (www.idtus.com), which specializes in the design, development, and implementation of automated software testing solutions.

Elfriede Dustin has authored multiple software testing books and articles based on her many years of actual hands-on automated software testing experience. Elfriede leads IDT’s efforts in automated software testing research programs.

Thom Garrett has experience in planning, testing, and deployment of complex systems for DoD and commercial applications for companies such as Public Broadcasting Service (PBS), Digital System Resources (DSR), Inc., and America Online (AOL). Thom received a master’s degree from the University of San Francisco.

Bernie Gauf is the president of IDT. Bernie has been invited to participate in numerous DoD panels associated with the use of new technology, testing conferences, and as a guest speaker to share his insights on automated software testing.

Product details

  • Format: Kindle Edition
  • File Size: 4457 KB
  • Print Length: 368 pages
  • Page Numbers Source ISBN: 0321580516
  • Simultaneous Device Usage: Up to 5 simultaneous devices, per publisher limits
  • Publisher: Addison-Wesley Professional; 1 edition (4 Mar. 2009)
  • Sold by: Amazon Media EU S.à r.l.
  • Language: English
  • Text-to-Speech: Enabled
  • X-Ray:
  • Word Wise: Not Enabled
  • Screen Reader: Supported
  • Enhanced Typesetting: Enabled
  • Average Customer Review: 2.5 out of 5 stars 2 customer reviews
  • Amazon Bestsellers Rank: #1,277,190 Paid in Kindle Store (See Top 100 Paid in Kindle Store)
  • Would you like to tell us about a lower price?

Customer reviews

2.5 out of 5 stars
5 star
4 star
3 star
2 star
1 star
See both customer reviews
Share your thoughts with other customers

Top customer reviews

Format: Paperback
I am about to embark on an automated software testing project using TestComplete, so I needed some 'to-do and do-not's before we have built a huge framework.

This book has been a huge disappointment. A lot of wishy-washy business pitch. If you believe in their water-fall approach to software development, you may agree with some of what they say, but then you know this already. And it is all about planning, not about aspects of automated testing you may need to know about when you actually embark (or plan to embark) on a AST project.

I think following the suggestions of this book will keep you busy with planning and estimating and setting up and implementing, and it will possibly help you sell a test-automation project to your managers (if you need this type of help), but it will not bring you any closer to a functioning automated software testing system, as it has very little to say about how you actually do automated software testing.
Comment 3 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse
Format: Paperback
This book presents a comprehensive treatement of the domain of software testing automation. The first part defines and describes test automation, proposing a business case for automation and discussing the pitfalls that should be avoided. The second part is a roadmap for test automation. It gives six keys for software testing automation payoff:
1. Know your requriments
2. Develop a strategy
3. Test your tools
4. Track progress and adjust
5. Implement the process
6. Put the right people in the process.
Four appendixes complete the book. They provide a process checklist, explain how automation applies to various testing types, disscuss tools evaluation and give a case study.

The fact that the autors have worked with the Defence industry might have affected the way the book was conceived and written: with structure and rigor. The discussions, recommandations, references and tools suggestions apply however to every software testing situation and not only to organization that are strongly process oriented. The aim of the book is to be a guide that can help to implement successfully automated software testing and it certainly achieve its objective.
Comment 3 people found this helpful. Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback.
Sorry, we failed to record your vote. Please try again
Report abuse

Most Helpful Customer Reviews on Amazon.com (beta) (May include reviews from Early Reviewer Rewards Program)

Amazon.com: 3.4 out of 5 stars 13 reviews
4.0 out of 5 stars Four Stars 2 Oct. 2016
By Amazon Customer - Published on Amazon.com
Format: Paperback Verified Purchase
0 of 1 people found the following review helpful
1.0 out of 5 stars give me my 2 hours back. 23 April 2014
By Michael Yim - Published on Amazon.com
Format: Kindle Edition Verified Purchase
Absolutely no useful information at all. The author keeps rambling repetitively about topics without telling the reading exactly how to implement automated software testing.
22 of 23 people found the following review helpful
5.0 out of 5 stars Pragmatic and practical help for test automation 12 May 2009
By Lisa Crispin - Published on Amazon.com
Format: Paperback
Although this book is not oriented towards agile software development, it's still a solid resource for anyone new to test automation. It's pragmatic, practical, clearly written, easy to understand. I especially like the six "Keys" for automation payoff. The authors explain the reasons for automating - it might seem obvious to some but many newbies don't see all the potential benefits. The book also blows through automation myths. There's a lot of emphasis on ROI, which is often overlooked.

Where the advice I give on automation differs from this book is making it a whole team effort, rather than the test team only, but that's easier to do in an agile setting. Also, the authors do talk about things like interviewing stakeholders, and getting people with the right skills, these are all so important.

I wish the book had a section on continuous integration and automated build process. I think in another few years nobody will question the need for this, any more than people currently question the need for automated source code management. Whereas a few years ago nobody in my conference tutorials was doing CI, nowadays about a third of the people are. I think it's so critical to have a way to continually run all the automated regression tests every time new code is checked in. The book makes a passing reference to this, and it does mention test automation at different levels starting at the unit level, but it doesn't explain why you need a build process and how to set one up.

Nevertheless, it's a great resource, and will give readers a good grip on the fundamentals of test automation. I get so frustrated when people think it's impossible to automate, or that they have to hire some expensive consultant to get it done. This book will enable teams to be much more successful. It is a good overview of all the different areas where automation can help a team tremendously.

Just be sure to also buy a book that tells you how to set up continuous integration and automated builds, such as _Pragmatic Project Automation_ by Mike Clark, or _Continuous Integration_ by Paul Duvall, Andy Glover and Steve Matyas. Or _Ship It_ by Jared Richardson and William Gwaltney.
9 of 9 people found the following review helpful
4.0 out of 5 stars first, automate the unit tests 28 Mar. 2009
By W Boudville - Published on Amazon.com
Format: Paperback
The authors give you a top level description of why automated software testing is highly desirable, along with detailed guidelines for doing so. The tone is very realistic, making you aware of many issues associated with the topic.

For one thing, you are cautioned to avoid the blandishments of a vendor who might suggest that her product will meet all your testing needs. In the authors' experience, there is no single tool that covers all major operating systems. The book also advises you to look at open source freeware. There is a surprising amount of good stuff freely available, that you might want to check first before considering proprietary products.

The book mentions many reasons for automation. These include manual tester fatigue. But also that some things are very difficult to test in a manual fashion. Often this could be because manual testing is at the GUI level. There could be bugs deep in the code, maybe in computational blocks.

Which also leads to the point that the "testers" for making automated tests often have a different skill set from manual testers. The latter might not be programmers. The former should be, with access to the source code [white box or grey box testing]. Because this gives them knowledge about what automated tests to write, that test critical aspects.

Naively, given the book's nature, we might expect it to say automate everything in sight. But the book's credibility is enhanced by it explaining that this is simply not economically feasible. The estimate is 40-60% of tests to be automated. Table 6.2 in the book is a list of questions that can be applied to each test, to suggest whether a test is suitable for automation. Roughly, tests that will be run often are a high candidate for automation.

The book also strongly recommends extensive unit testing. This is the lowest level of testing and bugs caught here have the best payoff in terms of minimising the cost to fix. A tight software development loop; "agile" as opposed to "waterfall"-like, though the book doesn't use these terms. Plus often unit testing might not be doable at the GUI level anyway, if the units are computational routines. So punting by not having automated unit tests and expecting manual tests to later find bugs in these units is very bad. Of coure, the book also describes higher level tests like regression and functional tests. But first do the unit tests.
24 of 26 people found the following review helpful
3.0 out of 5 stars Strong on theory and planning, weak on practical implementation 12 May 2009
By James Holmes - Published on Amazon.com
Format: Paperback
This book isn't for everyone, but everyone can get some value out of it. What I mean by that rather confusing statement is that folks working in Agile environments will likely want to throw the book across the room while folks in more bureaucratic environments like CMMI or other waterfall environments will likely get a great deal of value from the book.

I'm an Agile fanatic and I had a difficult time dealing with book's approach which emphasizes spending large amounts of time creating documentation such as requirements traceability matrixes, detailed test plans, etc. My preferred approach is to have testers working side-by-side as part of a team, creating specifications from user stories/requirements and moving those right in to automated test suites via tools like Selenium, Cucumber, or RSpec.

That said, I did indeed get some good value from the book. I found the discussions on making hard evaluations on what to test very worthwhile reading: teams can easily vaporize large amounts of time creating large suites of brittle, unmaintainable automated tests. This book has several really good chapters on using business cases to drive return on investment (ROI) decisions for testing, understanding automated test pitfalls, and adjusting your testing as you progress through your project.

Additionally, one of the book's high points was on building the test team: "Put the Right People on the Project - Know the Skill Sets Required." This is a great chapter which emphasizes starting the search by focusing on how to interview test team members - and how those testers' skills are greatly different than other members of the team.

The book's very academic, dry tone makes for some difficult reading, and few concrete examples are used until very late in the book. Having spent a large number of years either in the DOD or working for DOD contractors, it quickly became apparent that much of the book seemed targeted to folks working in those environments - too many dry acronyms are scattered through the book, adding to the difficulty in reading.

The lack of examples using real tools frustrated me. While the appendices contain some examples of comparing various tools, the book doesn't actually show how a real world testing environment would use those tools. One appendix, eight or nine pages in length, is touted as a "Case Study" but falls short, in my opinion.

Overall it's a decent book. The dry tone and lack of real environments is balanced out by the excellent coverage of team skills and emphasis on selecting how and what you test.
Were these reviews helpful? Let us know
click to open popover