- Paperback: 280 pages
- Publisher: Prentice Hall; 1 edition (July 25, 2002)
- Language: English
- ISBN-10: 0130084689
- ISBN-13: 978-0130084682
- Product Dimensions: 7 x 0.6 x 9.2 inches
- Shipping Weight: 12.6 ounces (View shipping rates and policies)
- Customer Reviews:
- Amazon Best Sellers Rank: #1,559,258 in Books (See Top 100 in Books)
Just Enough Software Test Automation (Just Enough (Yourdon Press)) 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
Fulfillment by Amazon (FBA) is a service we offer sellers that lets them store their products in Amazon's fulfillment centers, and we directly pack, ship, and provide customer service for these products. Something we hope you'll especially enjoy: FBA items qualify for FREE Shipping and Amazon Prime.
If you're a seller, Fulfillment by Amazon can help you grow your business. Learn more about the program.
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
Customers who viewed this item also viewed these digital items
From the Back Cover
- Techniques that improve software quality and reduce time to market
- Pragmatic approaches to plan and manage every facet of automated software testing
- Includes a complete sample automation project plan
Practical automated testing techniques that enhance software quality and reduce 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 dos and don'ts for designing and implementing test automation infrastructurealong with pragmatic advice on what today's most popular approaches to automated testing can and can't accomplish. Coverage includes:
- Setting realistic expectations: knowing when and what to automate
- Planning for automated testing
- Implementing the Control Synchronized Data Driven Testing (CSDDT) Framework, a proven approach to simplify and accelerate testing
- Simplify maintenance of test scripts and promote reuse using structured test script writing.
- Automating unit testing, integration testing, and system/regression testing
- Managing the automated testing process for optimal efficiency
The book also includes a complete sample automation project plan, covering documentation, implementation, the automation environment, roles, responsibilities, and much more.
About the Author
DANIEL J. MOSLEY is founder and principal of Client-Server Software Testing Technologies and author of The Handbook of MIS Application Software Testing and Client-Server Software Testing on the Desktop and Web (Prentice Hall PTR). A Certified Software Test Engineer (CSTE), Mosley served as senior consultant and seminar leader for the Quality Assurance Institute and authored the TEST-RxTM Methodology.
BRUCE A. POSEY specializes in developing and implementing data-driven, framework-based test scripts utilizing SQA Suite/Rational Team Test. He has nearly 30 years' IT experience in diverse roles at MasterCard, Deutsche Financial Services, SBC, and other leading firms. He is owner and principal consultant of The Archer Group, which specializes in software testing and training.
There was a problem filtering reviews right now. Please try again later.
The only quirk I found in the book was the diatribe against the benefit of CMM or knowledge of other models. I understand their point, which is that these models don't really add value to the hands on aspect of testing or developing software. However, from personal experience, I have seen a greater tendency in developers to consider many of the points they make if their background includes an appreciation for the types of things that should happen in a mature organization.
Regardless of my opinions and views, the authors have put together a powerful, sensible approach to test automation. Key strengths include:
- Pragmatism, including compelling counter arguments to my own views (especially in the first two chapters titled "What Is Just Enough Test Automation?" and "Knowing When and What to Automate". I particularly liked the distinctions between processes, and life cycles and tools.
- Going straight to the critical success factors, such as requirements as the entire basis for test planning, and ensuring traceability throughout the development life cycle. In addition, the frank discussion of limitations of some testing tools, and the associated high maintenance associated with scripts, is illuminating. I also liked the way that the book shows what can be automated, and, more importantly, what cannot (or should not) be. It also reemphasizes the importance of developing a test strategy and test plans, and how automation tools fall short in some areas. An invaluable part of this aspect of the book is the discussion of test scripting languages and their strengths and weaknesses.
- Examples based on real tools, with an emphasis on Rational's TestStudio. Mercury Interactive's WinRunner is also used to illustrate key concepts of the Test Plan Driven framework that is discussed later in the book.
- Material that hands-on practitioners can use. While I have a high regard for the Automated Test Lifecycle Methodology that is proposed in an excellent book titled "Automated Software Testing" by Elfriede Dustin, Jeff Rashka, John Paul, that book is more for implementing and managing automated testing within the context of a life cycle, and isn't a topic to which the audience of this book will relate. Indeed, the real strength of this book is the fact that no other book on automated testing talks to the practitioners. In addition, the material covers unit, integration, and regression testing from the practitioner's point of view.
- Advanced topics including data-driven approaches to testing that ties into automated suites, hybrid approaches that combine manual and automated elements, and how to develop test plans and associated artifacts.
Despite my disagreement with some of what the authors views, I have to give this book my highest endorsement because, in my opinion, it's well thought out, provides one of the most thorough discussions of test automation at the practitioner level I've encountered, and is technically flawless.
While the book is well written and easy to read for someone who's familiar with software testing and who may have some experience with test automation, it assumes that the reader does have experience in the field.
The authors begin by reviewing important fundamental practices of software testing that are critical to effectively sustaining both manual and automated testing efforts. They provide recommendations on how to approach test automation for each phase of the software development lifecycle beginning with requirements through the final stages of testing. The authors present very specific recommended techniques and tools and offer many examples using a data driven framework with emphasis on Control Synchronized Data Driven Testing (CSDDT). Most often the tools mentioned and examples provided are those offered by Rational, Inc. as well as the use of Microsoft Excel. Frequently, automated tools from other vendors are referenced when they are applicable to the technique being discussed. They provide references to books and to several web links that offer sources of information on similar frameworks using other tools. The authors include useful information in the appendices such as a captured discussion on the subject of the data driven approach by leading practitioners, automated testing definitions, an example test automation project plan, and a test automation project work plan template.
Some of the key points in the book include the importance of identifying and documenting application and testing requirements as well as documenting test cases and conditions. They emphasize the importance of planning for test automation and implementing it similar to any other software development effort. This includes the separation of roles between test designer and test implementer. They urge that test automation be performed at most phases of software development including unit testing, but that it primarily be used for regression testing. The key success factor for test automation is the maintainability of test scripts. The authors point out that this is extremely difficult using a capture/playback method of implementation and that a data driven approach using modular scripts has shown to be much more successful in the long run. The authors do a good job of describing these key points and then making specific recommendations with examples on how to implement them.
As a practitioner of test automation, and reviewer of this book, I very much agree with these key recommendations and support the authors' intent to educate people implementing test automation as these key points can be the difference between failure and success.