Test-driven development (TDD) is fundamental to agile, but to most of us caught up in projects, there's never enough time to commit to it. Erick Fleming shows how to use TDD to improve product quality and time to delivery.
The ISO/IEC/IEEE 29119 has defined a set of requirements for testing software. As a member of the ISO working group, Jon Hagar wants you to know the basics and why testing teams should consider this recommendation.
Johanna Rothman compares the experience a patient has with doctors to software development. Producing value implies that the customer believes the software you create provides an important benefit by taking into consideration the way a user works along with an exceptional user experience.
By emphasizing better communication and collaboration between software development and IT, this article explores ways to establish trust by focusing on customer value. For example, Manoj Khanna suggests continuous integration and validation as techniques that helps build that trust.
Matt Heusser presents ten key factors to establish a team cadence—the time between running tests and getting a product into production. The shorter the cadence, the less time spent in test/fix/retest land, and the more time spent working on new features.
Agile projects assume that test planning, test creation, and test execution take place throughout a project's lifecycle. So the need for unit testing (and especially automated unit testing) can't be ignored and should be considered as a key responsibility of the entire team—not just the software developers.
In part one of our Learning for Agile Testers series, we addressed general "thinking" skills that go beyond technical competence and how learning these enhances the value you contribute. In part two, we discuss some specific technical skills that benefit testers and how to acquire them.