The Latest

Danny Faught recommends Testing Applications on the Web: Test Planning for Internet-Based Systems by Hung Q. Nguyen. Faught concludes: "This book does not attempt to be a general reference on software testing. What it provides, instead, is domain-specific information that helps the reader plan for testing a Web-based application. Its clear illustrations of important Web testing approaches and its extensive checklists give testers detailed suggestions for their testing, based on real Web development experiences."

Don Gray recommends Measuring and Managing Performance in Organizations by Robert D. Austin. The book is not a five-step program toward measurement success; instead, it gives an in-depth look at what makes or breaks measurement systems. The book presents information in an intuitive way; if you understand algebra and simple logic, you will understand what Austin is presenting.

Do testers really belong in early reviews? For Michael Dedolph, the answer is yes! For that matter, he thinks more installers should be involved as well. Why? Testers and installers are usually involved in the "end game," so they add value by bringing that very different point of view to the review process.

After almost twenty-five years as a professor, Elaine Weyuker left academia for full-time work at AT&T. Here, she shares how industry and academia can both benefit from collaborating.

Before they started using T-VEC, David Statezni's group was manually creating and running requirements tests and separately creating and running code coverage tests. T-VEC's features allowed them to save time.

The success or failure of a downsized organization depends on the work force remaining after the storm. Before deciding to change jobs, survivors should carefully analyze their company's situation. Downsizing many be an indicator of poor economic peformance, or it may be just what the company needed in order to turn itself around. Employees who "weather the storm" may discover new opportunities for career advancement hidden among the ruins.

Patterns, as described by the architect and theorist Christopher Alexander and his colleagues over the last thirty-five years, are a way of describing problems and customizable solutions. Patterns became popular in the software development field, and they've been applied to testing. Here, Brian Marick explores patterns and problem solving.