The Latest

One of the most important tools a tester can keep on hand is a book, whether it contains instructions for a new method or is a reference for an old favorite. This Tool Look contains one tester’s take on the book "Fit for Developing Software" by Rick Mugridge and Ward Cunningham.
 

Testers are quick to think about speed when testing, but there are many other time-related guidewords that can help broaden your test coverage as well. Michael Bolton suggests a few guidewords to get you started.

From the Copernican solar system to an engineer’s scale replica of a bridge, the world is full of models that answer our questions and help us solve problems. Lee Copeland tells us that a model doesn't have to be correct to be useful.

Agile methods have made their way to the software mainstream in the last few years. As more organizations turn to agile development, its definition often gets obscured. Learn the facts behind five common agile myths, as Robert Holler attempts to dispel these misconceptions.

In this article, the authors the use of basic patterns that can help build a software configuration management process that works well with your agile development environment. They discuss how codeline policy, private work spaces, smoke tests, private system builds, integration building, unit testing, and regression testing all work together to enable you to maintain an active development line.

Ramnivas Laddad talks about Aspect Oriented Programming, which isn't just for security and logging anymore.

When landing an airplane, the approach is considered quite important. If the approach vector is off even by 1%, the plane may careen off the other end of the runway. Also, if the approach is incorrect, effort such as fuel and time is unnecessarily expended and wasted, especially if circling must occur.