Adam Turoff wrote:
It's out of print and nearly impossible to find. I haven't read it yet,
so I can't say whether it is as seminal as McBreen says it is.
Interesting - bn.com claims to have it available. BTW, for years now only a softcover "facsimile edition" is available. I had the original hardcover, but my darn ethics forced me to leave with the ex-employer that had reimbursed me for it.
Anyway, it's seminal in that it was the first testing book that's written more for developers than testers (if we don't count Beizer's Software Testing Techniques). Personally, I found the book somewhat tedious at times. It goes into lots of low-level detail about designing test cases. I do remember some interesting test catalogs in the appendices that serve as reminders for things to test for. If I weren't on the road right now I'd take another look at it.
See http://testing.com/writings/bookrev.htm for Brian's own comments on the book. One interesting comment - "The bookkeeping that subsystem testing requires cries out for automated assistance. There isn't any." Perhaps his "multi" tool is directed at that concern to some extent.
--
Danny R. Faught
Tejas Software Consulting
http://tejasconsulting.com/
