The Latest

For one reason or another, team members don't feel safe reporting bad news that marks the delay of a project. No one wants to take responsibility for the set back, so the blame is passed down the production line. At this point, the blame game is in full swing. In this week's column, Peter Clark refers to this game as Schedule Chicken. His commentaries on the game's development reveal strategies that perpetuate delays. And this game only has losers: the project and the customer.

Because Web services are especially vulnerable to security breaches, verifying the integrity of Web services is critical to successful deployment.

One of the major goals of testing is to provide information to decision-makers about the quality of the product under test and the risks of releasing or not releasing the software.

It is often difficult for testers and test teams to look beyond their current project. However, software test automation works best within frameworks that address all projects not just one.

Most programmers learn very little about testing techniques in school. This has a ripple effect through the software development cycle, often leaving quality issues until too late in the project.

Performance testers use various methods to describe user workloads-scenarios, operational profiles, and more. Understanding these workloads and accurately simulating them is one key to developing useful performance tests.

Creating an effective test strategy is an expensive undertaking for complex software applications. While the money invested in the process is relatively easy to measure, the return on that investment (ROI) is much harder to quantify.