In the first installment of this article, Dr. James Whittaker discussed turning testing on its head—to revitalize and improve the value of late-stage testing. James also discussed ideas behind empowering your dogfooders, testers, and the crowd to significantly and efficiently improve software quality. In part two, Jason Arbon discusses the research and engineering experimentation behind realizing these ideas into new tools and processes.
Arguments that moving testing forward in the software lifecycle maximizes the return on investment of testing effort have been made and widely accepted. And it is hard to argue with the results. Software is getting better. But what if a shift away from early cycle testing toward late cycle testing could improve quality even more?
Ten percent of the world's population lives with some sort of disability. So, is your software product optimized accessible to these people? Rajini Padmanaban takes a look at the different types of disabilities out there and the ways to ensure your product works well with as many of these needs as possible.
Mughees Minhas is the senior director of product management for Redwood Shores-based Oracle Corporation where he specializes in application testing, database performance diagnostics, and data center monitoring and optimization. We recently had the opportunity to talk to Mughees about the rise of the cloud, market consolidation, and risk management.
The testing craft is sometimes fascinated with high-tech, expensive tools that are intended to help managers keep up to date on what's going on. Yet, sometimes heavyweight tools aren't necessary. Michael Bolton describes how Paul Holland, a senior test manager, uses a decidedly low-tech approach to track and illustrate the testing story.
Testers and developers can be friends. In fact, on teams working at a breakneck pace to deliver software, they must be friendly enough to rely on each other. However, there are a few sure-fire ways to ruin that relationship before it begins—and potentially make testing both irrelevant and unwelcome. Marlena Compton lists seven such ways here, along with suggestions for avoiding disaster.
Charles Goodhart stated: "Any observed statistical regularity will tend to collapse once pressure is placed upon it for control purposes." In other words, "When a measure becomes a target, it ceases to be a good measure."
Analysts determine what needs to be created. Programmers create it. Testers find the holes in the work of both. That's one way to do it, but all three can collaborate to do these things better, and more easily, too.