When executing test modules, an interesting question to ask is “What needs to happen with issues that are found?” Hans Buwalda suggests making a distinction between issues found during a sprint and after the team has declared the functionality under test "done"—and describes how to proceed from there.

Software testing tools can be incredibly helpful, but only if you're implementing them from a good starting place. If your code is a mess, a tool won't fix that; you'll end up simply adding layers on top of the mess. Matt Heusser explains how your team would be better off learning elements of code as craft.

In making the move to agile practices, testing teams are finding that a specific skill set—or more than one—is necessary in order to take advantage of the benefits of agile methodologies. Sanjay Zalavadia looks at the skill sets and information that teams need before an agile project can begin.