This article describes how to use techniques from extreme programming for teams that have not implemented XP.

This article presents how to build and manage efficient test team. It also introduces the "tester’s style analysis questionnaire" to discover the 4 types of tester that exist within organisations.

This article explains how to improve testing efficiency with risk evaluation.

This article presents a practical perspective on test automation and the various points to consider for achieving positive results in this area.

This article provides a checklist for testing GUI.

The key is to follow the rules of software development when automating testing. This paper presents seven key steps: improve the testing process, define requirements, prove the concept, champion product testability, design for sustainability, plan for deployment, and face the challenges of success. Follow these steps as you staff, tool, or schedule your test automation project, and you will be well on your way to success.

This article shows how continuous integration can help to keep projects on track.

Agile teams accept change as inevitable and tailor their processes accordingly. Short iterations mean that stakeholders can see steady progress and provide frequent feedback. Continuous integration means that if one part of the system isn’t playing nicely with others, the team will find out almost immediately. Merciless refactoring, where programmers improve the code internally without changing its external behavior, prevents code from becoming fragile over time. Extensive automated unit tests ensure that fixing one bug won’t introduce two more.

This article lists the main work habits that make teams difficult to work with. May serve as a brief catalog of bug reporting "anti-patterns" that testers can use a checklist to make sure they are not accidentally annoying the developers they work with, and that developers can use to identify sources of friction between themselves and their testing team.

Mark Doliner's Cobertura (cobertura is Spanish for coverage) is a free as in speech GPL tool that handles this job. Cobertura monitors tests by instrumenting the bytecode with extra statements to log which lines are and are not being reached as the test suite executes. It then produces a report in HTML or XML that shows exactly which packages, classes, methods, and individual lines of code are not being tested. You can write more tests for those specific areas to reveal any lingering bugs.