The Latest

Change is hard, but leading your managers and co-workers toward higher quality needn't be dull and dreary. In this article, author Lisa Crispin explains several techniques you can use to take your organization to the next level, including gauging your visibility and recruiting a quality champion.

Test managers often need to make an initial estimate of the number of people that will be required to test a particular product, before the information or the time to do a detailed task breakdown is available. One piece of data that is almost always available is the number of developers that are or will be working on the project in question. Common sense suggests that there is a relationship between the number of testers and the number of developers. This article presents a model that can be used in describing that relationship. (Editors note: Click here to read another paper on this topic, by Cem Kaner, Elisabeth Hendrickson, and Jennifer Smith-Brock.)

Why is it that some testers get better responses from developers than others? Part of the answer lies in their defect reports. Following a few simple guidelines can smooth the way for a much more productive environment.

Testing system-level components such as the Java API for XML-Based Remote Procedure Calls is a challenging task.

Many projects' first test approaches are characterized by uncontrolled, ad hoc testing. Session-based testing can help you manage unscripted, reactive testing.

A Java development project team had proceeded to 25% completion using the traditional waterfall development method when they were suddenly asked to adopt eXtreme Programming (XP) practices and continue with the project.