Agile methodologies bring new complexities and challenges to traditional performance engineering practices, especially with Web 2.0 technologies that implement more and more functionality on the client side. Mohit Verma presents a Scrum-based performance testing lifecycle for Web 2.0 apps...

As test managers and test professionals we can have an enormous emotional impact on others. We're constantly dealing with fragile egos, highly charged situations, and pressured people playing a high-stakes game under conditions of massive uncertainty. We're often the bearers...

In this interview, Penny Wyatt discusses her Agile Development Conference West session, "Transform Your Agile Test Process to Ship Fast with High Quality," to share some of the ways she and her team achieved success, and how they—and you—can continue to develop and grow together.

I have been tasked by my company to come up with a single page document that shows the "value" that QA provided to the project.  Basically we need to show how we have saved and/or made the company money through any given project.

I have things like number of hours tested, if we went over budget, number of defects found, etc., but what are your suggestions?

How do I show the value of the defects found and come up with a comparison to what it would cost to fix these things in the field?