Programming Books C Java PHP Python Learn more Browse Programming Books
Automated Software Testing and over one million other books are available for Amazon Kindle. Learn more
  • List Price: $69.99
  • Save: $10.50 (15%)
Only 9 left in stock (more on the way).
Ships from and sold by
Gift-wrap available.
FREE Shipping on orders over $35.
Used: Good | Details
Sold by giggil
Condition: Used: Good
Access codes and supplements are not guaranteed with used items.
Have one to sell? Sell on Amazon
Flip to back Flip to front
Listen Playing... Paused   You're listening to a sample of the Audible audio edition.
Learn more
See this image

Automated Software Testing: Introduction, Management, and Performance: Introduction, Management, and Performance Paperback – July 8, 1999

ISBN-13: 078-5342432879 ISBN-10: 0201432870

Buy New
Price: $59.49
20 New from $19.00 47 Used from $0.25
Amazon Price New from Used from
"Please retry"
"Please retry"
$19.00 $0.25

Frequently Bought Together

Automated Software Testing: Introduction, Management, and Performance: Introduction, Management, and Performance + Software Test Automation + Just Enough Software Test Automation
Price for all three: $156.39

Buy the selected items together


Shop the new
New! Introducing the, a hub for Software Developers and Architects, Networking Administrators, TPMs, and other technology professionals to find highly-rated and highly-relevant career resources. Shop books on programming and big data, or read this week's blog posts by authors and thought-leaders in the tech industry. > Shop now

Product Details

  • Paperback: 608 pages
  • Publisher: Addison-Wesley Professional (July 8, 1999)
  • Language: English
  • ISBN-10: 0201432870
  • ISBN-13: 978-0201432879
  • Product Dimensions: 1.3 x 7.1 x 9.4 inches
  • Shipping Weight: 2.3 pounds (View shipping rates and policies)
  • Average Customer Review: 4.5 out of 5 stars  See all reviews (40 customer reviews)
  • Amazon Best Sellers Rank: #725,155 in Books (See Top 100 in Books)

Editorial Reviews 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.

From the Inside Flap

Automated Software Testing addresses the challenge for today’s software professionals who are faced with real schedule deadlines and need to introduce, manage, and perform automated testing on a project. The book addresses automated testing within a client-server or Web environment.

The focus of this book is the pragmatic concerns and information needed by the software test engineer/manager who faces the necessity of performing testing more thoroughly and quickly. By the same token, these same concerns may apply to the software developer who has the responsibility for development testing (that is, unit and integration testing) and, on some projects, system testing. The book also represents an informative guide that bolsters the ability of the quality assurance engineer to perform quality reviews on test design, test procedures, and the results of test activities.

The software project manager, who is responsible for the overall development effort, may also find this book useful. The text provides the project manager with guidelines concerning the goals and objectives of the testing effort and the decision about whether to automate testing. It also offers guidance on introducing automated testing on a project and outlines the processes for performing test planning, design, development, execution, and evaluation.

The authors have worked intimately with a number of automated testing professionals around the world, who were generous enough to share their problems and concerns. One primary concern voiced by these test engineers related to the fact that the test industry does not have the kind of structured methodologies that developers have traditionally enjoyed. Similarly, project managers, test managers, and test engineers may not be familiar with the kinds of approaches that are required to perform automated testing as opposed to the traditional test approach.

Clearly, the emphasis on automated testing represents a paradigm change for the software industry. This change does not simply involve the application of tools and the performance of test automation. Rather, it is pervasive across the entire test life cycle and the system development life cycle. The approach taken by project managers, test managers, software engineers, and test engineers is altered as a result. For software professionals to successfully make the leap to automated testing, structured approaches to testing must be embraced.

Automated Software Testing is revolutionary in that it promulgates a new structured, building-block approach to the entire test life cycle, while also providing relevant test automation and associated test management guidance needed by industry test professionals.

Automated Testing
Software project managers and software developers building today’s applications face the challenge of doing so within an ever-shrinking schedule and with minimal resources. As part of their attempt to do more with less, organizations want to test software adequately, but as quickly and thoroughly as possible. To accomplish this goal, organizations are turning to automated testing.

Faced with this reality and realizing that many tests cannot be executed manually, such as simulating 1,000 virtual users for volume testing, software professionals are introducing automated testing to their projects. While needing to introduce automated testing, software professionals may not know what’s involved in introducing an automated test tool to a software project, and they may be unfamiliar with the breadth of application that automated test tools have today. Automated Software Testing provides guidance in these areas.

The growth of automated test capability has stemmed in large part from the growing popularity of rapid application development (RAD), a software development methodology that focuses on minimizing the development schedule while providing frequent, incremental software builds. The objective of RAD is to engage the user early and throughout design and development of each build so as to refine the software, thereby ensuring that it more closely reflects the needs and preferences of the user. In this environment of continual changes and additions to the software through each software build, where requirements are encouraged to evolve, software testing takes on an iterative nature itself. Each new build is accompanied by a considerable number of new tests as well as rework to existing test scripts, just as there is rework on previously released software modules. Given the continual changes and additions to software applications, automated software testing becomes an important control mechanism to ensure accuracy and stability of the software through each build.

As noted above, a primary goal of RAD is to shorten the overall development schedule, by addressing the riskiest aspects of development in early builds. As a result, test activities are undertaken at the start of the initial RAD cycle and through each subsequent RAD cycle as well. As noted in Part III of this book, test design and development represent a complex undertaking. A test effort, in fact, may be as time-consuming as the effort required to develop the software application. When the project involves the integration of commercial off-the-shelf (COTS) products, for example, the test effort may even require more resources than software development. Instances where the test team does not participate in software specification or when test is not initiated soon enough pose a risk to the project. In these situations, potential outcomes include an incomplete software test effort, an insufficient test schedule, and an unplanned extension to the development schedule to accommodate testing.

Much of the test effort required on a project now needs to be supported by automated test tools. Manual testing is labor-intensive and error-prone, and it does not support the same kind of quality checks that are possible with an automated test tool. The introduction of an automated test tool can replace mundane manual test activities with a more efficient and repeatable automated test environment, which itself improves test engineer morale and retention.

Although some automated test tools began as capture and playback tools, the functionality and capabilities of automated test tool suites have been expanding. Automated test capabilities for software products include testing of the graphical user interface, requirements compliance, load performance, code coverage, Web interface, network communications, memory leakage, and more. New capabilities continue to be added to keep pace with the growing demand for test support.

This book concentrates on the concerns of the software test professional within the framework of an Automated Test Life-cycle Methodology (ATLM). ATLM is a structured methodology geared toward ensuring successful implementation of automated testing. The ATLM approach mirrors the benefits of modern, rapid application development efforts, where such efforts engage the user early in the development cycle. The end user of the software product is actively involved throughout analysis, design, development, and test of each software build, which is augmented in an incremental fashion.

The ATLM incorporates a multistage process consisting of six components. It supports the detailed and interrelated activities that are required to decide whether to acquire an automated testing tool. The methodology takes into account the process of introducing and optimizing an automated test tool and addresses test planning, analysis, design, development, execution, and management. The scope of the test program is outlined within the test plan, as a top-level description of test approach and implementation. The scope is further refined through the definition of test goals, objectives and strategies, and test requirements. Similar to software application development, test requirements are specified before test design is constructed. Likewise, the test program must be mapped out and consciously designed to ensure that the most efficient and effective tests for the target application are performed. Test design is developed through graphical portrayals of the test effort, so as to give project and test personnel a mental framework on the boundary and scope of the test program.

Test Training
The evolution of automated testing has given birth to new career opportunities for software engineers. In fact, while the demand for automated software test professionals has exploded, community colleges and universities have not produced a reciprocal response to help support industry demand.

Some universities that are typically more proactive in responding to changes in the software industry have already implemented software test and quality assurance courses. For example, George Mason University (GMU) provides software test and quality assurance courses (see the GMU Web site at isse.gmu/ for more information). Kansas State University (KSU) offers students several courses on the subject of software test and quality assurance and other courses that touch on the subject (see the KSU Web site at ksu/).

Purdue University offers two undergraduate courses in software engineering that cover software testing and reliability.Among other areas this center supports research projects. For more information, see the Purdue University Web site at purdue/.

The North Seattle Community College has established one of the most progressive testing curricula in the country. The college offers three levels of software testing courses (introduction, automation, and leadership) and one- and two-year software testing programs.Information concerning additional university and industry training resources is available on the author’s Web site at autotestco/.

The Automated Software Testing textbook is intended to help in classroom instruction on software testing that uses modern automated test tool capabilities. The book provides students with an introduction to the application and importance of software test, and it describes the different kinds of automated tests that can be performed. Instruction continues with the definition of the test approach, the roles and responsibilities of the test team, test planning, test design, test script development, test execution, defect tracking, and test progress reporting.

About the Authors
Automated Software Testing was developed by three software industry professionals.

Elfriede Dustin has performed as a computer systems analyst/programmer developing software applications and utilities, process and data modeling using CASE tools, and system design simulation models. She has experience supporting a variety of system application development projects, including health, financial, logistic, and enterprise information management systems. In addition, Elfriede has been responsible for implementing the entire development life cycle, from requirement analysis, to design, to development, to automated software testing. She has been a test manager and a lead consultant guiding the implementation of automated testing on many projects. Because of her automated test expertise, she has been sought out to help modify the capabilities of commercial test tool products, where her use and feedback on test products has proved invaluable.

Jeff Rashka has managed a multitude of significant information system and systems integration projects. System applications on which he has served as manager include worldwide transportation asset management, enterprise information management, financial management, bar-coded inventory management, and shipboard information systems. Jeff also has process improvement management experience in implementing the guidelines contained within the Software Engineering Institute’s Capability Maturity Model (CMM).

John Paul has worked as a senior programmer/analyst on financial and budgeting systems as well as a host of other information systems. His software development leadership responsibilities have included system analysis and design, application prototyping, and application development using a number of different methodologies and programming techniques. His software development responsibilities have included application testing using automated test tools. John has also assumed a lead role in the performance of year 2000 compliance testing.

The authors have applied their collective knowledge of software engineering, automated testing, and management to develop a book that addresses the pragmatic concerns and information needed by the software test engineer and manager. Automated Software Testing is designed to be a useful—and practical—guide for software engineers and software project managers who are responsible for software test activities.

Book Style and Organization
This book’s organization correlates with the phases, tasks, and steps of the ATLM. The sequence of the book is fashioned in a purposeful way. It addresses the reader as if he or she had just been handed a note giving that individual the responsibility for automated software testing on a project. A first question might be, "What exactly is automated testing, and why do I need it?" Part I of the book answers this question and provides other fundamental instruction allowing the would-be test to approach the new responsibility with confidence. The reader is then guided through the decision to automate testing as well as automated test tool selection and evaluation.

After receiving this fundamental instruction, the test engineer would have several more questions: "What is involved in setting up the tool?" "How do I get the test team in place?" "What early test planning is required?" Part II answers these questions. Specifically, the process for introducing an automated test tool is outlined and guidelines for structuring the test team are provided.

Part III focuses on automated test planning, analysis, design, and test automation (programming). This section of the book addresses test design techniques, which are comparable to the structured software design techniques introduced over the past 20 years. Specifically, it highlights the discipline required in the design of test automation. The goal is to give useful information on test design and test case development, so that the test engineer doesn’t have to discover (by trial and error) how to put together a good test design and set of test procedures.

Part IV helps the reader address several additional questions: "What’s involved in the performance of test?" "How do I manage my test schedule?" "How do I document and track defects?" This section provides guidelines pertaining to test execution, defect tracking, and test program status tracking. A set of best practices for the development and execution of automated test procedures is provided to assist test professionals in executing test activities in an efficient manner.

Overall, the book seeks to allay the concerns of the software test professional within the framework of the ATLM. ATLM is a structured methodology, and one that is geared toward ensuring successful implementation of automated testing. Readers with questions and comments may contact the authors via their home page at autotestco/. This Web site also provides more information on automated software testing and resources that are available to support automated software testing programs.

More About the Author

Software development is still an art and that makes automated software testing a special challenge. At IDT ( we strive to meet that challenge by producing an extensible automated testing framework, suite of tools along with context driven automated testing solutions.
For the last 7 years at IDT together with a brilliant team of engineers I have successfully lead various business development efforts as a technical director and contributed many feature ideas to IDT's automated testing suite of tools.
For any questions related to business development, program management, automated software testing, Automated Test and Re-Test (ATRT), or the various books here, please contact me at
You can also follow me on twitter @ElfriedeDustin or find me on linkedin ElfriedeDustin

My bio continued:
I have a B.S. in Computer Science with over 20 years of IT experience, implementing effective testing strategies, both on Government and commercial programs. I have implemented automated testing methodologies and testing strategies as an Internal SQA Consultant at Symantec, worked as an Asst. Director for Integrated Testing at the IRS Modernization Efforts, implemented testing strategies and built test teams as a QA Director for BNA Software, and was the QA Manager for the Coast Guard MOISE program, just to name a few of the companies and testing/QA efforts I have worked on in the past 20 years.
I am the author and co-author of 6 books related to Software Testing, i.e. author of the book 'Effective Software Testing' and lead author of 'Automated Software Testing' and 'Quality Web Systems,' and co-authored the book 'The Art of Software Security Testing,' together with Chris Wysopal, Lucas Nelson, Dino D'ai Zovi, which was published by Symantec Press, Nov 2006. See my list of books here on this page.
My goal is to continue to help further automated software testing advances and contribute to solving the automated software testing challenge.

Customer Reviews

4.5 out of 5 stars
Share your thoughts with other customers

Most Helpful Customer Reviews

42 of 44 people found the following review helpful By Erick M. Griffin on October 5, 1999
Format: Paperback
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.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
28 of 31 people found the following review helpful By Geordie Keitt on September 22, 2000
Format: Paperback
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.
Read more ›
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
23 of 25 people found the following review helpful By Huntley on March 31, 2000
Format: Paperback
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.
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again
19 of 21 people found the following review helpful By on October 1, 1999
Format: Paperback
Having been in the testing business for some years, I have yet to find a book on any aspect of software testing that is as interesting to read and as well structured as this book. The methodology (ATLM) is greatly needed, especially in my part of the world and there is also a vast amount of information relating to testing in general which it has always been difficult to find in one place. This book will be invaluable to anyone who needs to organise, plan and make decisions concerning a project test phase (this often being the area of greatest confusion in software development) and who wishes to understand and integrate the automated aspect of testing. I particularly like the extensive use of tables which give succinct descriptions of many of the key areas in testing.
I plan to adopt the principles and methodology fully in my test consultancy which I shall use alongside my company's own test management application.
Congratulations to all concerned. This is easily the best book in my extensive testing library!
Comment Was this review helpful to you? Yes No Sending feedback...
Thank you for your feedback. If this review is inappropriate, please let us know.
Sorry, we failed to record your vote. Please try again

Customer Images

Most Recent Customer Reviews

What Other Items Do Customers Buy After Viewing This Item?