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.
Automated testing is vital for every software development organization's quality assurance activities. Dorothy Graham and Seretta Gamba demonstrate how to classify issues that occur during test automation. The authors maintain that certain test results have root causes that can be categorized as patterns that require specific mitigation strategies.
Taking lessons from the lean business model, Matt Heusser explains how a tester can present different values and properly set expectations with the team using the lean test canvas. His approach starts with defining who the customer is and ends with key qualitative measures that will be used to ensure success.
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.
Speaking from his experience with test-centered design projects, Jon Hagar explores some testing pitfalls that could have been avoided if the right test strategy had been chosen. You won't find a better, easier-to-understand explanation of a practical test strategy.
Finding defects late is a common issue when teams don't consider levels of precision or detail. You must take into account how stories and features fit into the system. In this FAQ column, Janet Gregory tells you how you should remember the big picture—even while testing the small stuff.
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.
With mobile and small embedded devices extending the reach of modern computing, the predictions are that wearable computing is definitely the next biggest thing. If you want to know more about the wearable device revolution, Mukesh presents facts that will convince you this is the next hottest trend.
What happens when defects go unnoticed until it is too late? Mayank provides an insightful view of the true cost of not providing enough test coverage during a software development lifecycle. He also suggests some techniques to ensure that defects are identified and mitigated early.