Search in Book Reviews

This is a perfectly respectable text on the subject though I think it lacks the linguistic fluency ofSoftware Test Automationwhich focuses on a specific test methodology, unimaginatively titled; Automated Test Lifecycle Methodology. This is supposed to be the testing parallel to Rapid Application Development. I am not entirely convinced. If it were no more than that I would want my developers to use something more comprehensive. In fact I think ATLM is more than that description implies.

The authors include consideration of such things as gaining management support, test tool evaluation and some aspects of reuse. There are several thought-provoking case studies particularly when it comes to management of teams of software testers.

I think that if your company is responsible for large-scale software that needs proper testing you should become familiar with the available test methodologies. That is just as important as being familiar with A&D methodologies. If I were a programmer on a large- scale project I would expect the management to support my work with properly managed testing regimes. Testing should not be some after- thought added on when things go wrong, nor should it be something that is skimped on the basis that if everyone else does their jobs correctly then testing is superfluous to requirements and therefore a waste of money. Of course I will want to believe that tests will only throw up problems with the work of others but I would much prefer not to find myself working overtime because some incompetent shipped flaky software.

If your company already has a well planned test methodology you can skip this book but if their concept of testing is 'if it compiles and runs then all is well', you could do worse than invest time in reading this book so that you will be able to promote a viable alternative.