This edition warns of the trouble that comes when you start testing the programs that test programs. Next-generation tools could be just what your project needs. Linda Hayes explains the pros and cons of implementing such a solution.

Sometimes TDD (Test-Driven Development) doesn't get used because it can be cost prohibitive to a testing budget. Read on as Joel Spolsky laments the limited real-life usefulness of test-driven development and discusses some common roadblocks to using this testing technique.

Window mapping gives elements specific names so tests are easier to update and understand. Task libraries group sequences of steps that make up part of user tasks when those sequences show up in multiple tests. Data-driven test automation separates the parameters of a test case from the test script so that the test script can be reused for many related tasks. Keyword-driven test automation formats tests as tables or spreadsheets and creates parsers to read and execute the test descriptions. Take advantage of these four techniques to help you test a graphical user interface, and see how developers can make your life easier.

Justifying the role of testing and measuring the value of testers' performance are problems that many of us struggle with. James Bach offers some things he finds helpful when he has to give a quantitative answer to the question, "What is your group saving the company?"