The Latest

For decades quality assurance (QA) has been a back-end loaded process. Developers put the bugs in, and QA tests the bugs out.

With most GUI test tools that exist today, model-based testing for Java applications is extremely difficult to implement.

Team player Dave Hoover wants to share a software development practice he enjoys. It emerged from the practices of extreme programming as a competitive yet simultaneously collaborative practice. Dave has found that this practice promotes the flow of knowledge between software developers better than any other practice he has experienced. As you might have guessed from the title of this week's column, this practice is called ping-pong programming, or P3 for short.

Connect with an expert to learn how to work smarter and learn new ways to uncover more defects. In this issue, Michael Bolton dishes out commentary on why testers who master skills instead of memorizing techniques are relished in the software industry.

Every manager has a story to tell. Find out how one management professional tackles a fictional dilemma. The story may be made up, but the solutions are tried and true. In this installment, Johanna Rothman recounts the tale of a wayward project rescued by a cross-functional team.

Brian Marick uses Jeremy Bentham's centuries-old punitive philosophy to explain why visibility and self-regulation can propel the success of a project. In today's software development environment, exposing bugs and its root causes for all to inspect can help teams avoid introducing the same and similar bugs into their code.

As an activity, performance testing is often misunderstood, especially by executives and managers. Try these tips on your next performance testing project and put your team on the fast track to success.