Rating: 
Summary: recomended
Review: it is a very interesting and useful book. The methodology that is using for automated software testing is original and i like it. I recommend the book to students in System analysis and design course and also to Application development course.
Rating:
Summary: A book long awaited for!
Review: It's great to know that somebody has written a "New" book about Software Quality Engineering in general, but this one is extra special... It's on a topic that many before did not cover at all or felt that 1 or 2 pages on the subject were enough. Automated Software Testing covers so much missing ground, which has never been covered before. It's a book I believe every QA Engineer already is or wanting to be should have. I got this book as soon as they started shipping it, and I spent some great amount of time enjoying it. I do have to tell you that it won't make you a SilkTest, WinRunner or a tool expert in general, simply because it does not discuss a specific tool. What it will make you is more aware of how to approach, design and implement your automated test system. I give it an easy 5 stars rating. -AJ Alhait (www.betasoft.com)
Rating:
Summary: Closing the Shelfware Gap
Review: Many organizations own some kind of automated software test tool (or tools), however only a minority (about 15 - 20% by my surveys) actually use the tools they own. This indicates there is a large gap in applying automated testing tools and a resulting large pile of "shelfware" when it comes to this segment of the tool market. This book does an excellent job in helping to close the gap between having an automated test tool and actually using the tool in the testing process. Automated Software Testing is definately the most complete guide to the process of test automation I have seen compiled in one source. The book is detailed and contains many tables, samples and case studies to provide practical application of the concepts presented in the book. I highly recommend this book for anyone considering test automation or for those who have been involved with test automation wishing to improve their processes.
Rating:
Summary: Mandatory Guide for Implementing Automation
Review: Most organizations purchase automated test tools as a "silver bullet" or cure-all for their testing woes. Any test engineer will tell you this is simply not feasible and that planning for automation is as important as planning any other portion of the testing process. This book explains the process of testing with automation and should be required reading for any manager who has purchased automated test tools. Automation may not be right for every organization, but following this book's guidelines is right for every test automation effort.
Rating: 
Summary: Excellent book -- using on our software development project
Review: Not only does the book explain in detail how to automate your project's testing activities, it also is useful for explaining the basics. Currently we're using this book as a guide while we scrub our requirements to make them testable.
Rating:
Summary: At Last! How to conduct effective automated testing!
Review: Remarkable book that every test engineer should read! Being a software programmer, I need the test engineers to work closely with us to help produce a successful product while staying on schedule, satisfying defined requirements and eliminating errors. The book defines a logical approach and provides best practices for the test engineer to provide a comprehensive and efficient automated software test program. This book brings needed structure to the way the test team approaches their work. I've experienced two projects now where the introduction of automated testing was a considerable problem. Automated Software Testing guides the test engineer every step of the way from considering whether or not automation is beneficial to tool selection and introduction. Furthermore it lays out test planning requirements and provides instruction on how to design the test program to include both automated and manual tests. Our development team will be applying the book's test design guidance to our development test efforts. Finally a book that outlines the pitfalls and provides solid examples of best practices that can be applied to automated software testing projects. Software developers everywhere should give a copy of this book to their test team.
Rating:
Summary: Generally a good book on how to start Test Automation...
Review: Reviewed by Erick Griffin, September 4, 1999 When seeing the title of this book for the first time I must admit I was immediately intrigued by its topic, being a member of Tivoli's Test Automation Group and all. Its title promised that between its covers all would be revealed regarding what automation means to software testing. It does in fact deliver on this main theme rather well. Moreover, depending upon your interest in test automation one might not be able to consider all points brought up by this book applicable to their specific area of expertise. It is however, an excellent place to start! Below is outline of the book and what the reader will find hidden away in its pages. Chapter 1. The first chapter discusses some of the more mundane aspects of how to define automated software testing. A necessary evil but for those already familiar with this topic you may want to skip this. Chapter 2. Mostly a discussion on the topic of 'why' software testing automation is so necessary today. Most of what the authors cite as to improving partnerships with development teams and improvements in some of the more important issues of testing are all good lessons that should be learned and clearly understood. This chapter also delves into two other important areas, the real benefits of automation and how to get management support for test automation goals. The latter is most important, the how in making management understand what the correct expectation of automated software testing should be is all important before pursuing any automation strategy. Chapters 3 and 4. Here are the 'meat and potato' chapters on how to correctly evaluate and consider test automation tools. This should be read by anyone who is considering the purchase of a tool that would perform any test automation; and gives a good account of all of the tool areas that must be considered, (e.g. source code testing tools, load/performance/stress test tools). A valuable chapter in learning what the Test Life-Cycle Tools are and what they do. Important for anyone wanting to properly weight an insistent salesperson's marketing hype! Chapter 5. Management only, enough said. Chapters 6 through 9. These are the core chapters of the book and should be read by anyone and everyone interested in overall test considerations. They therefore serve as a guide to overall test planning, development and other considerations, always with a slant on automation. Though most will find these chapters full the normal stuff any verification engineer needs to consider. Chapter 10. People responsible for deploying and managing a software test automation project will want to consider reading this chapter. Here is where the benefits are explained, it gives you a good understanding when and where the payoffs are. One of the more tacit points made in this chapter is that automation is not a short term solution to any problem. It is a long term solution and must become an integral way of life in any verification organization. Appendices. These provide information on How to Test Requirements, Tools That Support the Automated Testing Life Cycle pretty good!, Test Engineer Development good for management and your knowing your own skills and where they fit, A Sample Test Plan in case you've never seen one (I would hope this wasn't the case). This book should be purchased by anyone who is concerned with test automation. It should be used by those development and verification individuals who need to be concerned with automation topics in their areas to help reduce costs and relieve critical resources to accomplish their group's overall product goals. These individuals include but are not limited to: All second and first line development and verification management who really need to understand how, when and where automation should be done and why! All senior engineers who need to consider test automation during software design and development. Any company wide organizations whose charter it is to develop and deploy automation tools and technologies to their organizations. And last but not least, any other individuals who might stand to gain from learning how automated software testing might improve their understanding of the need to reduce costs and test resources, while increasing the level of test repeatability and reuse in their areas of verification. Most organizations establish verification groups only after a product has been developed. These groups are therefore usually well behind the eight ball before they even start to consider such topics as test automation. This book could prevent such organizations from making costly mistakes with test processes and automation that most organizations do when starting. Finally and most importantly it can be used to help define automated software testing in an organization that is already in place. It can help correct its direction towards the necessary amount of automation a group needs. Most of all it can help reduce the resources needed during verification in the long run, which ultimately drive a better product out the door. This is after all what most customers demand from the computer industry today, isn't it?!
Rating:
Summary: "Great All-Round Book On Testing Methodology"
Review: Software Testing is all about methods and technology- 80% methods, 20% technology. I find the methods that are listed in this book to be sound. ... Other topics (i.e., test project management, test cycle, test plan, etc) that are also listed in this book are well explained. There isn't that many great books in automated software testing or general software testing . However, the delinated concepts in this book and Graham's book (Software Test Automation) are well-written good. After reading these books, I feel most readers (beginning and intermediate SQA professionals) could have a better sense of what Automated Software Testing is about. Recommend this book very highly.
Rating:
Summary: ¿Automated Software Testing¿ is a very informative book!
Review: The book covers many automated testing topics. This book is especially useful to managers and experienced testers, but would also be an excellent training tool for novice testers. This book provides a comprehensive guide to automated and manual software testing. It covers all aspects of testing - e.g., test techniques, methods, plans, scripts, and procedures. This book is an excellent training and reference tool.
Rating:
Summary: excellent book which illustrates the whole life cycle
Review: The book discusses the manual Vs automated testing processes. It talks about when to apply automated testing and when not to. Since i'm an entry level tester this book proved to be very useful in understanding the pro and cons of the above processes. I would suggest that this book be a part of a college curriculum so students can get a good over view to a first introduction and a solid understanding of a 'Software Testing' methodology.
| 
