Home > Store

Just Enough Software Test Automation

Register your product to gain access to bonus material or receive a coupon.

Just Enough Software Test Automation


  • Sorry, this book is no longer in print.
Not for Sale



  • NEW - “Control Synchronized Data Driven Approach”Introduces a powerful new extension of data-driven testing that simplifies and accelerates testing by eliminating the need to modify test scripts in a wide range of scenarios.
    • Teaches students a testing technique that enables them to achieve powerful results far more quickly and efficiently. Ex.___

  • Generic test script templates—Includes a set of proven templates designed to streamline the development of new test scripts.
    • Will help students begin developing automated scripts immediately. Ex.___

  • Practical guidance for all levels of testing—Offers practical insights about which types of testing can and cannot be automated, and the best ways to automate those forms of testing that lend themselves to automation.
    • Prepares students for a wide range of testing scenarios and environments. Ex.___

  • By two of the world's leading software testing consultants—Presents authoritative insight based upon the authors' extensive real-world consulting experience.
    • Gives students the benefit of the authors' extraordinary software testing experience. Ex.___


  • Copyright 2003
  • Dimensions: 7" x 9-1/4"
  • Pages: 288
  • Edition: 1st
  • Book
  • ISBN-10: 0-13-008468-9
  • ISBN-13: 978-0-13-008468-2

Automated testing is a crucial element of any strategy for improving software quality and reducing time-to-market. Just Enough Test Automation is a practical, hands-on guide to software test automation from the perspective of test developers and users. Two leading software testing consultants offer real-world do's and don'ts for designing and implementing test automation infrastructure -- along with pragmatic advice on what today's most popular approaches to automated testing can and cannot accomplish. The authors offer a realistic approach to automating the tests that lend themselves best to automate, and facilitating manual tests with automated tools. The book presents best processes for automating unit testing, integration testing, and system/regression testing; and for managing the automated testing process for optimal results. The authors also introduce the powerful new Control Synchronized Data-Driven Approach, which simplifies and accelerates testing by eliminating the need to modify test scripts in a wide range of scenarios.

Sample Content

Online Sample Chapter

What Is Just Enough Test Automation?

Table of Contents


What Is Just Enough Test Automation?

No New Models, Please! A Life Cycle Is Not a Process. A Tool Is Not a Process. How Much Automation Is Enough? Testing Process Spheres. Test Planning. Test Design. Test Implementation. Support Activities. Testing Is a Team Effort. A Test Automation Group's Scope and Objectives. The Scope. Assumptions, Constraints, and Critical Success Factors for an Automated Testing Framework. Test Automation Framework Deliverables. An Automation Plan. Categories of Testing Tools. Conclusion. References.

Knowing When and What to Automate.

In General. When to Automate System Tests. Time to Automate Is Always the Number One Factor. An Extreme Example. A Quantitative Example. What to Automate. A Word About Creating Test Scripts. Conclusion. References.

Start at the Beginning, Define the Test Requirements, Design the Test Data.

Software/Test Requirements. Requirements Gathering and Test Planning Automation. From Software Requirement to Test Requirement to Test Condition: An Automated Approach. Requirements Management and Traceability. Functional Test Data Design. Black Box (Requirements-Based) Approaches. Gray Box (Both Requirements- and Code-Based) Approaches. White Box (Code-Based) Approaches. Requirements-Based Approaches. Requirements-Driven Cause-Effect Testing. Equivalence Partitioning, Boundary Analysis, and Error Guessing. Defining Boundary Conditions for Equivalence Classes. Error Guessing. Hybrid (Gray Box) Approaches. Decision Logic Tables. DLT as a Software Testing Tool. An Automated DLT Design Tool. Code-Based Approaches. Basis Testing Overview. The Basis Testing Technique. Conclusion. References.

A Look at the Development of Automated Test Scripts and at the Levels of Test Automation.

Developing Automated Test Scripts. Unit-Level Tests. System-Level Tests. Specialized System-Level Tests. Recording versus Programming Test Scripts. Conclusion. References.

Automated Unit Testing.

Introduction. Unit Testing Justification. The Unit Testing Process. A Rigorous Approach to Unit Testing. The Unit Test Specification. Unit Testing Tasks. Implementating the Unit Testing Tasks. Rules of Thumb for Unit Testing. Unit Testing Data. A Unit Testing Framework. For Object-Oriented Development Using Java. Conclusion. References.

Automated Integration Testing.

Introduction. What Is Integration Testing? The Daily Build Smoke Test. Build Smoke Test Objectives. Automated Build Smoke Test Checklist. Conclusion. References.

Automated System/Regression Testing Frameworks.

The Data-Driven Approach. Framework-Driven (Structured) Test Scripts. Developing Framework-Driven Test Scripts. The Archer Group Framework. Business Rules Test. GUI Test. Properties Test. Input Data Test. Formatting the Test Data File. Application-Level Errors. Building the External Data Input File. Data File Summary. Code Construction for the Business Rules Test. The Shell Script. The Main Script. After the Data Are Read. Keep Your Code Clean and Robust. Archer Group Summary. Carl Nagle's DDE Framework. DDE Overview. DDE Development Effort. Keith Zambelich's Test Plan Driven Testing Framework for Mercury Interactive Users. Zambelich Approach Summary. “Test Plan Driven” Method Architecture. Using TestDirector to Drive the Test Suite. Conclusion. References.

The Control Synchronized Data-Driven Testing Framework in Depth.

Creating Data-Driven Test Scripts. Implementing the CSDDT Approach. Common Problems and Solutions. Problem: Data Input. Solution: Utilize Input Data Text Files. Problem: Program Flow Changes. Solution: Let the Input Data Do the Driving. Problem: Managing Application Changes. Solution: Rerecord or Modify a Very Small Section of Code. Setting Up Common Startup and Ending Test Conditions. Modifying Recorded Code to Accept Input Data. Very Important Practices. Creating Functions for Common Operations—Isolating Command Objects. Continuing with the Program Flow. Using Multiple Input Records to Create a Test Scenario. Utilizing Dynamic Data Input—Keyword Substitution. Using Library or Include Files (*.sbh and *.sbl Files in Rational Robot). Utility Scripts. Debugging Your Scripts—When the Test(s) Uncover a Defect. Implementing the CSDDT Template Scripts. The DDScripts. SQABasic32 Include Files. Utility Scripts. An Example of the CSDDT Framework. Script File List. Library File List. Directions for Installing the Example Files. Conclusion. References.

Facilitating the Manual Testing Process with Automated Tools.

Introduction. Semiautomated Manual Testing Process Steps. Step 1. Identify and document the test objectives. Step 2. Translate the test objectives into specific test requirements. Step 3. Translate the test requirements into test conditions. Step 4. Construct the test data.. Step 5. Execute the manual tests. Using the List Box. Manual Testing Artifacts. Conclusion. References.

Managing Automated Tests.

Writing Effective Test Scripts and Test Data. Managing Manual and Automated Test Scripts. Test Suite Maintenance. Conclusion. References.

Data-Driven Automation: User Group Discussion.

Automated Testing Terms and Definitions.

Example Test Automation Project Plan Using Rational Suite TestStudio.

Introduction. Documentation References. Internal Sources. External Sources. Automation Implementation. Test Management. Test Design Phase. Test Implementation Phase. Test Execution Phase. Automation Environment. Test Development Workstations. Test Data Store Server. Test Execution Workstations. Test Application Servers. Organizational Structure. External Interfaces. Roles and Responsibilities. Roles. Responsibilities. Project Estimates.

Test Automation Project Work Plan Template.

Work Breakdown Structure. Project Start-Up Phase. Timeline. Implementation Iteration Objectives. Project Schedule. Project Resources. Budget. Project Monitoring and Control. Automation Effort Estimation. Schedule Control Plan. Budget Control Plan. Reporting Plan. Measurement Plan. Supporting Processes. Configuration Management Plan. Defect Tracking and Problem Resolution. Framework Evaluation. Framework Documentation Plan. Process Improvement.




There has been a glut of test automation books on the market as of late. They all espouse different approaches to, and different levels of, software test automation implementation. There is even an attempt to describe an automated software testing life cycle in the most popular offering (see the Dustin reference in Chapter 2). Traditionally, authors of information systems (IS) industry publications typically try to force a hypothetical model to describe the processes we use. Sometimes it works and sometimes it doesn't. The problem is that there is no empirical evidence to support that the approaches put into practice in these models work in the real world. The majority of the recommended approaches in software testing and software development practices are based on anecdotal evidence and project management fads that are started by so-called experts in the IS field and perpetuated by chief information officers (CIOs) in health club steam rooms.

We do not believe in an automated testing life cycle. This is an artificial construct that we find of little use. Nor do we believe in a software testing life cycle. What we do believe is that software testing occurs as a set of integrated activities in the software development process. We also believe that good software testing requires a special form of project management and its own set of operational techniques. Testing also requires a set of tools that a test engineer can rely on during test activities. These tools can be testing artifacts such as printed test scenarios that a test engineer follows or printed test logs that the engineer fills out while executing the tests.

We are not saying that we have to wait until a body of empirical evidence has been compiled before we accept and use the tools and techniques advocated by the IS authorities. We are saying that we have to evaluate the tools and methods ourselves and weed out the fluff. The real experiment is this: which techniques work and which do not when practitioners (you and we) attempt to use the technology.

Dan Mosley, the first author, explored his first automated testing tool back in 1985 and the technology was pretty crude. He was able to obtain an evaluation copy of that product while he was teaching one of the earliest undergraduate software testing courses (Washington University in St. Louis, 1985-1992). In the mid-1990s, he had long telephone conversations with Eric Schurr, then of Software Quality Automation (SQA), now of Rational Software Corporation, which subsequently absorbed SQA and its products, concerning automated software testing tools and what, functionally, they should provide for software test engineers' use.

They discussed what a good automation tool should do and what features it should include. Because of Dan's contacts with Eric, he acquired and used copies of SQA's (now Rational's) automated testing tool, which came out after that early Version 1.0. The most current version (at the time of this writing) is Rational Suite TestStudio 2002. Dan's experiences with this product have shown that test automation is not an easy overnight fix for a faltering testing effort. Furthermore, his experiences have proven that automated testing is not a substitute for manual testing. Glen Myers published the fundamental concepts of software testing in the late 1970s. Even today his Art of Software Testing (1979) is considered the premier dialogue on software testing. We still need to apply his recommendations when we test manually and when we build an automated testing infrastructure.

Our pet peeve with test automation as it is currently practiced is the lack of emphasis on front-end test planning and test design activities. We keep repeating the classic mistake that software developers have perpetuated since the first program was written—we start testing (in the case of automated testing, writing the test scripts) without doing the proper analysis of the problem and design of the testing infrastructure. It brings to mind a cartoon from years ago—a manager is talking to the programmer: "You start writing code and I'll go find out what it is supposed to build." Automated tests that "test" the wrong things can have only one result: unsuitable tests are executed much faster.

The ultimate goal of any automation effort should be a set of planned tests that corresponds to a set of test requirements that in turn are reflected in the automated tests. Furthermore, the heart of the testing effort is not the test scripts, but the test data. This is why there is so much hype about data-driven automated testing as an automation implementation framework. The underlying premise is that data should drive the tests and should exercise the application under test's (AUT) features. The test scripts are just delivery vehicles. Automated tests are effective only when the test data are designed well.

An operational goal of an automated testing framework is to minimize test script maintenance. The traditional capture/playback model that testing tool vendors have championed for years leads to inordinately high script maintenance because the test data are hard coded in the body of the test script. Mosley's first experiences developing automated test scripts intuitively demonstrated that strictly using capture/playback is not the way to go. Furthermore, the built-in test cases the tools provided were essentially useless for anything but testing the application's graphical user interface (GUI). True functional testing requires the test engineer to write test data that probe the AUT in depth. GUI testing should be done, and it can be automated with minimal effort. In actual practice, we usually have a single test script that exercises the GUI objects. It baselines and validates the properties of all GUI objects. The test script is executed for each GUI screen.

Automating functional testing requires sophisticated test data that explore the AUT. The test data must reproduce test scenarios that exercise important system features. Consequently, automated functional testing is more complicated and difficult. It requires the test engineer to write a significant portion of the test script as opposed to recording it. It also means designing effective test data. Understanding what to test (having a documented set of test requirements) and designing test data that verify the requirements are the keys to writing valuable automated functional tests.

Understanding how to verify the test results is as important as knowing what to test. Automated test verification is also data dependent. As their primary verification method, automated tests frequently capture and store baseline data that are later compared against the same data captured during regression tests. More sophisticated tests access and manipulate database records before, during, and after the tests are executed.

A powerful automated testing framework must provide tools that address test planning, test design, test construction, test execution, and test results verification. An effective infrastructure is one that is predicated on an integrated central repository where testing artifacts can be stored and reused. The infrastructure should also provide customizable reporting capabilities.

We have a history prior to coauthoring this book. We met in 1996 when we worked together on the first really successful automated testing project we had encountered up to that point. Since then, we have worked together on a plethora of test automation projects. We have developed a sense of what is required to implement a successful automation project and what is required to propagate automated testing in an IS development and testing organization. We know as much about what won't work as we do about what will work.

Working together, we implemented a data-driven automated testing paradigm before we had even heard of this now prolific industry phrase (we were unaware of the paper that Richard Strang had given at the STAR conference in 1996; see the Chapter 1 references). We pioneered and perfected our implementations of the data-driven approach while others were just beginning to discuss and write about it. Of course, as with any new hot-button technology, it is not really new, just rediscovered. Data-driven testing is no exception. Beizer, in Software Testing Techniques (1983), described "Data-Base-Driven Test Design." This was late in the mainframe era and early in the PC revolution, so it was an idea related to testing mainframe applications. He presented it as a procedure not for testing the database, but for using the database structure to derive test data. He argued that it "is best suited to the verification of functional requirements as set down in the system specification." It is a simple step to expand this approach to include tests that are based on business rules supported by the database table structures. Add data that test the GUI objects and their behaviors and you have data-driven testing.

We also discovered structured test script writing (also known as framework-based testing) during this period. Again this is not new technology. Test scripts are programs written in modified versions of common programming languages such as Visual Basic and C. They are different in that they have special features to accommodate software testing tasks. There is a vast literature base that addresses structured programming concepts such as functional decomposition, module cohesion, module coupling, and modular (functional) reusability. As a test script constitutes a software program that tests another software program, it is subject to the same design and construction rules as the programs it is testing. Thus, structured programming concepts also apply to automated test scripts.

Because automated test scripts are also subject to the same baggage that other software programs carry, they can contain logic flaws; they can contain spaghetti (convoluted) code; they can contain hard-coded variables; and they can be implemented with both procedure and data in the test script itself. All of this adds up to increased costs related to test suite maintenance, just as there are costs associated with maintaining the software systems these test scripts test. Creating structured component-based test scripts that are separate from the data they execute is the only way to create an effective software test automation infrastructure, one that maximizes testing accuracy and that minimizes testing maintenance.

There have also been recent efforts to develop high-level test automation languages that can be used to design and implement automated tests by nontechnical personnel such as business and product analysts and system customers. These efforts are advocated as the next step in the evolution of automated testing. As yet, we have not seen an approach that simplifies test script development enough to be really useful. We can see the value of this as long as we are striving toward a set of universal script libraries that will support a common Java-like test scripting language; however, most frameworks to date have been written to support contrived high-level command languages, not object-oriented ones. In addition, the supporting libraries are as yet immature in the functionality they offer to the scriptwriter. To accomplish their testing needs, organizations have to add additional code to the existing library subroutines and functions.

Because we are practitioners, the aim of this book is to offer useful advice on test automation from the test automation developer's/user's perspective. It includes pragmatic advice on what to do and caveats concerning what not to do when designing and implementing a test automation infrastructure. It also contains advice on what current popular testing approaches can and cannot do for your testing endeavors.

Our examples were developed on the Rational Suite TestStudio platform, but we feel they can easily be adapted for use with other automated testing platforms. In addition, an FTP site (www.phptr.com/mosley) supports this book. That site contains template files from the Archer Group's Control Synchronized Data Driven Testing (CSDDT) approach (for the Rational environment), Carl Nagle's Data Driven Engine (DDE) approach (for the Rational environment), and Keith Zambelich's Totally Data-Driven approach using Mercury Interactive's WinRunner automated test tool, which is based on Zambelich's Test Plan Driven framework that uses his Toolkit For WinRunner. These resources can be used to easily jump-start your data-driven automated testing effort.


Submit Errata

More Information

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020