Automated Software Testing: Introduction, Management, and Performance (Paperback)

~ (Author), Jeff Rashka (Author), John Paul (Author)

Editorial Reviews

Amazon.com Review

Written for those with some background in software engineering, Automated Software Testing: Introduction, Management, and Performance delivers a rigorous guide to the state of the art in managing automated testing in a text that will benefit anyone who tests software for a living.

First and foremost, Automated Software Testing presents a methodology for test managers called Automated Testing Lifecycle Management (ATLM). This soup-to-nuts tour of testing takes you from initial planning, budgeting, and staffing to building a test plan and choosing test tools to executing tests and even improving your testing process the next time around. Though somewhat thickly written--with plenty of software engineering terminology--this book can also be useful to more practically minded readers because of its many sample test documents. (Besides numerous lists and charts outlining the steps in the ATLM process, the book presents a sample test plan, budget estimates, and staffing guides.)

A truly standout feature is the book's survey of currently available automated tools that can be used throughout the testing cycle, as well as how to choose the right ones for your next project. For many software testers and managers, this section alone is probably worth the price of the book.

As this book points out, test engineering is a growth field. While schools and businesses work hard to meet the demand for qualified testing professionals, this title can provide a solid guide to the best thinking on automated testing solutions that will save time and money as well as improve software quality. --Richard Dragan

Topics covered: Theory and practice of automated software testing, the Automated Testing Lifecycle Management (ATLM) process, test analysis, planning, design and execution, white-box and black-box testing, metrics, and choosing testing tools.

Product Description

Comprehensive, step-by-step guide to the most effective tools, techniques, and methods for automated testing. Numerous case studies of successful industry implementations are provided. Softcover. CD-ROM included. DLC: Computer software--Testing--Automation.

See all Editorial Reviews

Product Details

• Paperback: 608 pages
• Publisher: Addison-Wesley Professional (July 8, 1999)
• Language: English
• ISBN-10: 0201432870
• ISBN-13: 978-0201432879
• Product Dimensions: 9.2 x 7.3 x 1.3 inches
• Shipping Weight: 2.3 pounds (View shipping rates and policies)
• Average Customer Review: 4.5 out of 5 stars  See all reviews (41 customer reviews)
• Amazon.com Sales Rank: #342,801 in Books (See Bestsellers in Books)

  Popular in this category: (What's this?)

  #94 in

  Books > Computers & Internet > Programming > Software Design, Testing & Engineering > Testing

Customer Reviews

Most Helpful Customer Reviews

38 of 40 people found the following review helpful:

4.0 out of 5 stars Generally a good book on how to start Test Automation..., October 5, 1999

By	Erick M. Griffin (Cary, NC USA) - See all my reviews

Reviewed by Erick Griffin, September 4, 1999

When seeing the title of this book for the first time I must admit I was immediately intrigued by its topic, being a member of Tivoli's Test Automation Group and all. Its title promised that between its covers all would be revealed regarding what automation means to software testing. It does in fact deliver on this main theme rather well. Moreover, depending upon your interest in test automation one might not be able to consider all points brought up by this book applicable to their specific area of expertise. It is however, an excellent place to start!

Below is outline of the book and what the reader will find hidden away in its pages.

Chapter 1. The first chapter discusses some of the more mundane aspects of how to define automated software testing. A necessary evil but for those already familiar with this topic you may want to skip this. Chapter 2. Mostly a discussion on the topic of 'why' software testing automation is so necessary today. Most of what the authors cite as to improving partnerships with development teams and improvements in some of the more important issues of testing are all good lessons that should be learned and clearly understood. This chapter also delves into two other important areas, the real benefits of automation and how to get management support for test automation goals. The latter is most important, the how in making management understand what the correct expectation of automated software testing should be is all important before pursuing any automation strategy. Chapters 3 and 4. Here are the 'meat and potato' chapters on how to correctly evaluate and consider test automation tools. This should be read by anyone who is considering the purchase of a tool that would perform any test automation; and gives a good account of all of the tool areas that must be considered, (e.g. source code testing tools, load/performance/stress test tools). A valuable chapter in learning what the Test Life-Cycle Tools are and what they do. Important for anyone wanting to properly weight an insistent salesperson's marketing hype! Chapter 5. Management only, enough said. Chapters 6 through 9. These are the core chapters of the book and should be read by anyone and everyone interested in overall test considerations. They therefore serve as a guide to overall test planning, development and other considerations, always with a slant on automation. Though most will find these chapters full the normal stuff any verification engineer needs to consider. Chapter 10. People responsible for deploying and managing a software test automation project will want to consider reading this chapter. Here is where the benefits are explained, it gives you a good understanding when and where the payoffs are. One of the more tacit points made in this chapter is that automation is not a short term solution to any problem. It is a long term solution and must become an integral way of life in any verification organization. Appendices. These provide information on How to Test Requirements, Tools That Support the Automated Testing Life Cycle pretty good!, Test Engineer Development good for management and your knowing your own skills and where they fit, A Sample Test Plan in case you've never seen one (I would hope this wasn't the case).

This book should be purchased by anyone who is concerned with test automation. It should be used by those development and verification individuals who need to be concerned with automation topics in their areas to help reduce costs and relieve critical resources to accomplish their group's overall product goals. These individuals include but are not limited to:

All second and first line development and verification management who really need to understand how, when and where automation should be done and why! All senior engineers who need to consider test automation during software design and development. Any company wide organizations whose charter it is to develop and deploy automation tools and technologies to their organizations. And last but not least, any other individuals who might stand to gain from learning how automated software testing might improve their understanding of the need to reduce costs and test resources, while increasing the level of test repeatability and reuse in their areas of verification.

Most organizations establish verification groups only after a product has been developed. These groups are therefore usually well behind the eight ball before they even start to consider such topics as test automation. This book could prevent such organizations from making costly mistakes with test processes and automation that most organizations do when starting.

Finally and most importantly it can be used to help define automated software testing in an organization that is already in place. It can help correct its direction towards the necessary amount of automation a group needs. Most of all it can help reduce the resources needed during verification in the long run, which ultimately drive a better product out the door. This is after all what most customers demand from the computer industry today, isn't it?!

22 of 24 people found the following review helpful:

5.0 out of 5 stars The standard for Quality Assurance groups, March 31, 2000

By	Huntley "huntley48" (New York) - See all my reviews

If your organization is interested in having a mature automated testing process, you need this book. This book will guide you throughout the entire process from thinking about standards to implementing and maintaining them. After several years in QA, I did not have a complete appreciation for all the things that could and should be done until I read this book.

I am using the information available in this book to implement the quality assurance process for my organization and I am making the book required reading for all testers. In addition to all the important information on testing in general, the book also contains many other useful resources including a wonderful sample test plan.

Automated Software Testing: Introduction, Management and Performance is an invaluable resource for everyone involved in software quality assurance, from people thinking about entering the field to seasoned individuals who manage the testing process for their organization. If you are involved in QA or want to be involved, get this book.

24 of 27 people found the following review helpful:

5.0 out of 5 stars Packed with solid test planning knowledge, September 22, 2000

By	Geordie Keitt (Washington, DC USA) - See all my reviews

I am not the world's most experienced test manager, but I've been doing it for some time now, and although I knew there was a lot more to learn, I thought I knew the basics. But I had read not even 5 pages of this book before I had my pad of paper out and was scribbling down all the things I needed to do to improve my department. Most of them don't even have to do with test automation! Just software quality management.

The book presents a test automation methodology which is practical, useful, and complete, encompassing the state of the art of test automation as it stands right now (with the exception of some very recent developments in automated testing such as model-based testing, still in its infancy). One small thing I've learned: Our shop has already chosen a tool, so I skipped reading that part of the lifecycle, but wound up coming back to it when the authors discussed how to test the tool when it gets upgraded. I'm anticipating a tool upgrade soon, and there are lot of aspects of my testing that can be negatively affected if I don't plan for them. Now, I'm planning for them and expect to have a smooth transition, and to have confidence that my tool will continue to do the job with the scripts I've already written.

The automation methodology, though, really serves as a focal point around which the authors place a tremendous amount of information about how to perform software quality inspection.

Admittedly I would not take this book to read on the beach. First, the amount of work there is to do to run a test group well is staggering, and the authors are determined to jam it all in here. They make you concentrate. Second, they write using an extremely dry style, which doesn't obscure the points they make, but doesn't inject much life into them either. (I suppose if you want personality, you can always read Boris Beizer. But I still hear my old English major self talking: "Stop using the passive voice! Make somebody DO something!" Forgive my outburst - I feel better now.)

Elfriede Dustin and Jeffrey Rashka have packed this book with knowledge about how to run your testing and your defect-prevention efforts. They don't say it's easy, but they do map the territory very well. I will use and re-use this book for a long time.