Not Just for eBusiness,
This review is from: Risk Based E-Business Testing (Artech House Computer Library,) (Hardcover)
This book is written for the software tester and/or test manager, but not just those professionals who test eBusiness Web sites. Rather, there is something in here for any software tester, or IT manager who has responsible for software quality.
In some ways this book is actually 4 books in one - the first part of the book focuses on using Risk to drive the test strategy for a product being evaluated, an approach that works as well for testing embedded software in aircraft engines, as for testing a Web site used for eCommerce. For example, in Chapter 3 Paul & Neil pose age-old software testing questions such as; "how good was your testing?" and "when can we stop testing". Later providing answers based on a systematic (& defensible) approach, as opposed to good old fashioned "gut feel".
Part II provides a high-level overview of some of the more common risks that a Web site might face, and then applies the risk based testing strategy discussed in part 1 to this particular problem domain. In effect, providing a high-level generic case study for risk based testing.
Part III is the largest section in the book, and is a series of 9 Chapters that go into the details of how to test Web sites. The last chapter in this section focusing on tools that can be used to automate many of these tests.
The last part of this book; looks at some of the common challenges a testing team might face when trying to implement any new approach to software testing (i.e. many of these aspects being applicable to any testing environment, not just eCommence Web sites).For example; how to handle incident management, staff retention, and Beta testing.
In summary; this book has something for anyone involved in software testing (whether it is as a test executioner or in a test management capacity). Please do not let the title lead you into believing that this book is only appropriate for testing Web app's; there is plenty that is applicable for any software testing effort - especially the concepts of applying a risk based approach to determining what to test, and when to test it.
Note, additional details on this book can be found at [...]
Also, in the vain of "full disclosure", you should know that I've known Paul for many years, and consequently I cannot be considered a completely impartial reviewer.