Implementing Automated Software Testing: How to Save Time and Lower Costs While Raising Quality [NOOK Book]

Overview

“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...
See more details below
Implementing Automated Software Testing: How to Save Time and Lower Costs While Raising Quality

Available on NOOK devices and apps  
  • NOOK Devices
  • NOOK HD/HD+ Tablet
  • NOOK
  • NOOK Color
  • NOOK Tablet
  • Tablet/Phone
  • NOOK for Windows 8 Tablet
  • NOOK for iOS
  • NOOK for Android
  • NOOK Kids for iPad
  • PC/Mac
  • NOOK for Windows 8
  • NOOK for PC
  • NOOK for Mac
  • NOOK Study

Want a NOOK? Explore Now

NOOK Book (eBook)
$25.49
BN.com price
(Save 42%)$43.99 List Price

Overview

“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.

In Implementing 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.
Read More Show Less

Product Details

  • ISBN-13: 9780321619594
  • Publisher: Pearson Education
  • Publication date: 3/18/2009
  • Sold by: Barnes & Noble
  • Format: eBook
  • Edition number: 1
  • Pages: 368
  • Sales rank: 882,579
  • File size: 5 MB

Meet the Author

Elfriede Dustin, Thom Garrett, and Bernie Gauf work together at Innovative Defense Technologies (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.
Read More Show Less

Table of Contents

Foreword by Admiral Edmund P. Giambastiani, Jr. xv
Foreword by Dr. William Nylin, Jr. xvii
Preface xix
Acknowledgments xxiii
About the Authors xxv

Part I: What Is Automated Software Testing and Why Should We Automate? 1
Chapter 1: What Is Effective Automated Software Testing (AST)? 3

1.1 Automated Software Testing Definition 4
1.2 Automated Software Testing Recipes 5
1.3 Advances in AST Technologies 8
1.4 Automating Various Software Testing Types 11
1.5 Providing AST-Based Production Support 16
1.6 Automating Standards Assessments 18
Summary 20
Notes 21

Chapter 2: Why Automate? 23
2.1 The Challenges of Testing Software Today 24
2.2 Reducing the Time and Cost of Software Testing 26
2.3 Impacting Software Quality 38
2.4 Improvements to Your Software Test Program 42
Summary 49
Notes 50

Chapter 3: The Business Case 51
3.1 Definition of the Business Case 51
3.2 Identifying the Business Needs 53
3.3 Justifying Automation in Terms of Cost and Benefits 55
3.4 Risks 65
3.5 Other Considerations 67
Summary 68
Notes 68

Chapter 4: Why Automated Software Testing Fails and Pitfalls to Avoid 69
4.1 R&D Does Not Generally Focus on Automated or Manual Testing Efforts 71
4.2 AST Myths and Realities 74
4.3 Lack of Software Development Considerations for AST 83
4.4 The Forest for the Trees–Not Knowing Which Tool to Pick 91
4.5 Lack of Automation Standards across Tool Vendors 94
4.6 Lack of Business Case 97
Summary 97
Notes 97

Part II: How to Automate: Top Six Keys for Automation Payoff 99
Chapter 5: Key 1: Know Your Requirements 101

5.1 Understand the AST Support Requirements 102
5.2 Additional Information in Support of AST Requirements 114
5.3 When Information Is Not Available 116
5.4 Start Implementing Your Requirements Traceability Matrix (RTM) 124
Summary 128
Notes 128

Chapter 6: Key 2: Develop the Automated Test Strategy 129
6.1 The AST Strategy Document 131
6.2 Scope and Automated Test Objectives 132
6.3 Identify the Approach 139
6.4 Automated Software Test Framework (ASTF) 146
6.5 AST Environment/Configuration 150
6.6 Automating the RTM 159
6.7 Automated Defect Tracking 164
Summary 164
Notes 165

Chapter 7: Key 3: Test the Automated Software Test Framework (ASTF) 167
7.1 Verify That the ASTF Meets Specified Requirements and That Features Behave As Expected 169
7.2 Peer-Review All ASTF-Related Artifacts, Including Design, Development, and Test Cases 170
7.3 Verify Requirements and Coverage 182
7.4 Hold a Customer Review 183
Summary 184
Notes 184

Chapter 8: Key 4: Continuously Track Progress–and Adjust Accordingly 187
8.1 AST Program Tracking and Defect Prevention 188
8.2 AST Metrics 192
8.3 Root Cause Analysis 205
Summary 206
Notes 207

Chapter 9: Key 5: Implement AST Processes 209
9.1 AST Phases and Milestones 211
9.2 AST Phase 1: Requirements Gathering–Analyze Automated Testing Needs 212
9.3 AST Phase 2: Test Case Design and Development 215
9.4 AST Phase 3: Automated Software Testing Framework (ASTF) and Test Script Development 216
9.5 AST Phase 4: Automated Test Execution and Results Reporting 217
9.6 AST Phase 5: Program Review and Assessment 218
9.7 Virtual Quality Gates 219
9.8 Process Measurement 220
Summary 221
Notes 222

Chapter 10: Key 6: Put the Right People on the Project–Know the Skill Sets Required 223
10.1 Program Management 232
10.2 Systems Engineering 236
10.3 Software Development 239
10.4 Configuration Management 242
10.5 Quality Assurance 244
10.6 Subject Matter Experts (SMEs) 246
Summary 247
Notes 248

Appendices 249
Appendix A: Process Checklist 251

A.1 AST Phase 1: Requirements Gathering–Analyze Automated Testing Needs 252
A.2 AST Phase 2: Test Case Design and Development 253
A.3 AST Phase 3: Automated Software Testing Framework (ASTF) and Test Script Development 254
A.4 AST Phase 4: Automated Test Execution and Results Reporting 255
A.5 AST Phase 5: Program Review and Assessment 256

Appendix B: AST Applied to Various Testing Types 257
B.1 Security Testing 257
B.2 Soak Testing 261
B.3 Concurrency Testing 263
B.4 Performance Testing 265
B.5 Code Coverage Testing 269
B.6 Unit Testing 271
Notes 274

Appendix C: The Right Tool for the Job 275
C.1 Requirements Management (RM) 276
C.2 Unit Testing Frameworks–Example Evaluation 281
C.3 Configuration Management–Example Evaluation 284
C.4 Defect Tracking–Example Evaluation 292
C.5 Security Testing 299
C.6 Automated Software Testing Framework (ASTF)–Example Evaluation 306
C.7 Other STL Support Tools 316
Notes 319

Appendix D: Case Study: An Automated Software Testing Framework (ASTF) Example 321
D.1 Key Design Features 323
D.2 Test Manager 325
D.3 More on Automated Test Case and Test Code Generation 326
D.4 Results Reporting 328
D.5 Automated Defect Reporting 328
Notes 329

Contributing Authors 331

Index 333

Read More Show Less

Preface

Preface

Is your test automation strategy a losing proposition? Are you soured on the notion of automated software testing based on less than adequate past results? Are your test automation silver bullets missing their mark? Are you disappointed in your test automators? We at IDT1 have identified a boilerplate solution, strategies, and ideas, all provided in this book, that can help increase the chances of your automated testing success.

Given the arsenal of system and application software testing strategies, techniques, and solutions, automated software testing is one of the most effective practices that if implemented correctly can help increase testing efficiencies and ultimately reduce the testing cost while contributing to increased systems and software quality in terms of faster, broader, and more efficient defect detection.

This book is a guide that can help organizations implement successful automated software testing programs and efforts. The book does not provide gimmicks or magical solutions, as none exist, but it provides experience-based discussions and recommendations. It includes a thorough dissection of automation issues, such as in Part I of the book, where we describe what automated software testing is and is not; why a business case is required for successful automation, including step-by-step instructions for developing one; why to automate and when. Then we summarize why automation often fails and the pitfalls and blunders that can be prevented; we describe the tools that are available to help implement successful automation efforts, with a focus on open-source testing tools. In Part II of the book we present six keys to successfully implementing automated software testing. These are

  • Key 1: Know Your Requirements
  • Key 2: Develop the Automated Test Strategy
  • Key 3: Test the Automated Software Test Framework (ASTF)
  • Key 4: Continuously Track Progress—and Adjust Accordingly
  • Key 5: Implement AST Processes
  • Key 6: Put the Right People on the Project—Know the Skill Sets Required

IDT conducted two separate surveys related to automated software testing with approximately 700 total responses from test professionals all over the world, across organizations that were diverse in size and in what they do. The survey showed two very consistent themes:

  • About 70% of survey respondents said they believe automation is high-payoff, but they are generally not sure why to automate and how automation applies to their project.
  • Half of the survey respondents also said they felt they lacked the experience, time, or budgets to implement automation.

Most seem to agree: Automated software testing is useful, and an increasing need for it exists. However, the lack of experience seems to be the reason why automation is not implemented more often with a higher success rate. Finding people with the skills for the project is therefore important; a summary of skills required is provided in Chapter 10. For more details on the outcome of this survey, see Chapter 4.

Material Coverage and Book Organization

Part I: What Is Automated Software Testing and Why Should We Automate?

Chapter 1, What Is Effective Automated Software Testing (AST)?, describes what automated software testing is. The definition of automated software testing we use throughout this book is the “application and implementation of software technology throughout the entire software testing lifecycle (STL) with the goal to improve STL efficiencies and effectiveness.”

In Chapter 2, Why Automate?, we address this question that is asked so often. Here we discuss the challenges of software testing today and how the time and cost of software testing can be reduced. Reasons for why to automate, laying the foundation to help build the business case discussed step by step in Chapter 3, are presented here.

In Chapter 3, The Business Case, we define a step-by-step approach to defining the business case, which will cover the business need, the reasons for an automated software testing project, the business benefits (tangible and intangible), an analysis of the expected costs and timescales, an investment appraisal, and return on investment (ROI).

Chapter 4, Why Automated Software Testing Fails and Pitfalls to Avoid, clarifies some of the myths and realities surrounding automated software testing. The goal is for companies and organizations to review the lessons described here and not to repeat them during their automated software testing implementations.

Part II: How to Automate: Top Six Keys for Automation Payoff

Once management has been convinced by the business case that was laid out in Part I of this book and understands the pitfalls to avoid and the realities of automated testing, the next step is to determine how to automate. Part II of the book addresses how to successfully implement the various automated software testing tasks. We have determined that successful automated software testing can be achieved by implementing six top keys, described next.

Chapter 5, Key 1: Know Your Requirements, covers the importance of understanding the requirements before developing an automated testing strategy. Here we discuss approaches to determining the problem we are trying to solve along with how to gather information when requirements are not available.

Chapter 6, Key 2: Develop the Automated Test Strategy, discusses developing an automated testing approach in detailed steps, including test environment considerations, configuration management for automated test scripts, and related artifacts, among others. Here we also discuss what to consider when deciding what to automate and the importance of choosing the right tool, whether open-source, vendor-provided, or in-house-developed.

Chapter 7, Key 3: Test the Automated Software Test Framework (ASTF), covers the importance of understanding testing techniques and documenting test cases as part of automated testing. Automators often forget that documentation is still a vital part of the automated test program. The test case documentation serves as the blueprint for the automated software testing efforts. This chapter describes the importance of tracing test cases back to requirements; the content of the test cases, such as needing to include inputs and expected results; and how documented test cases become the basis for developing and implementing the automated tests.

Chapter 8, Key 4: Continuously Track Progress—and Adjust Accordingly, addresses the importance of tracking the goal that was set at the outset of the automation program. For example, during the discussion of business case development in Chapter 3 we explain the need for defining goals; in this chapter we discuss how peer reviews, inspections, and various automation and testing metrics can help measure and track progress against those goals.

Chapter 9, Key 5: Implement AST Processes, points out the need for a lightweight process. Some automated testing scripts can be implemented successfully without much process in place, but in order to effectively implement a large automated testing program a lightweight adaptable process should be in place. This chapter discusses a summary of this process, linking back to the details in various chapters.

Chapter 10, Key 6: Put the Right People on the Project—Know the Skill Sets Required, clarifies the skill sets needed for developing automated software testing, for instance, a skill set similar to that of the software development team, which includes requirements analysis, design, software development, and testing. Key 6 points out that although knowledge of testing techniques and analytical skills is important, effective automated software testing implementation requires software development skills. The skills described here parallel the automated testing process described in Chapter 9.

Audience

The target audience of this book is software test professionals such as test managers, leads, and practitioners. It is also geared toward all quality assurance professionals, QA leads, and practitioners. Project managers and software developers looking to improve the effectiveness and quality of their software delivery will also benefit from this book.


  1. 1 www.idtus.com.

© Copyright Pearson Education. All rights reserved.

Read More Show Less

Customer Reviews

Be the first to write a review
( 0 )
Rating Distribution

5 Star

(0)

4 Star

(0)

3 Star

(0)

2 Star

(0)

1 Star

(0)

Your Rating:

Your Name: Create a Pen Name or

Barnes & Noble.com Review Rules

Our reader reviews allow you to share your comments on titles you liked, or didn't, with others. By submitting an online review, you are representing to Barnes & Noble.com that all information contained in your review is original and accurate in all respects, and that the submission of such content by you and the posting of such content by Barnes & Noble.com does not and will not violate the rights of any third party. Please follow the rules below to help ensure that your review can be posted.

Reviews by Our Customers Under the Age of 13

We highly value and respect everyone's opinion concerning the titles we offer. However, we cannot allow persons under the age of 13 to have accounts at BN.com or to post customer reviews. Please see our Terms of Use for more details.

What to exclude from your review:

Please do not write about reviews, commentary, or information posted on the product page. If you see any errors in the information on the product page, please send us an email.

Reviews should not contain any of the following:

  • - HTML tags, profanity, obscenities, vulgarities, or comments that defame anyone
  • - Time-sensitive information such as tour dates, signings, lectures, etc.
  • - Single-word reviews. Other people will read your review to discover why you liked or didn't like the title. Be descriptive.
  • - Comments focusing on the author or that may ruin the ending for others
  • - Phone numbers, addresses, URLs
  • - Pricing and availability information or alternative ordering information
  • - Advertisements or commercial solicitation

Reminder:

  • - By submitting a review, you grant to Barnes & Noble.com and its sublicensees the royalty-free, perpetual, irrevocable right and license to use the review in accordance with the Barnes & Noble.com Terms of Use.
  • - Barnes & Noble.com reserves the right not to post any review -- particularly those that do not follow the terms and conditions of these Rules. Barnes & Noble.com also reserves the right to remove any review at any time without notice.
  • - See Terms of Use for other conditions and disclaimers.
Search for Products You'd Like to Recommend

Recommend other products that relate to your review. Just search for them below and share!

Create a Pen Name

Your Pen Name is your unique identity on BN.com. It will appear on the reviews you write and other website activities. Your Pen Name cannot be edited, changed or deleted once submitted.

 
Your Pen Name can be any combination of alphanumeric characters (plus - and _), and must be at least two characters long.

Continue Anonymously
Sort by: Showing 1 Customer Reviews
  • Posted April 14, 2009

    more from this reviewer

    first, automate the unit tests

    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.

    1 out of 1 people found this review helpful.

    Was this review helpful? Yes  No   Report this review
Sort by: Showing 1 Customer Reviews

If you find inappropriate content, please report it to Barnes & Noble
Why is this product inappropriate?
Comments (optional)