To complement functional validation, software teams are expected to validate performance. But, according to Jun Zhuang, you must be prepared to invest time, personnel, and resources to benefit from performance testing.
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.
In this FAQ column, Claire Lohr discusses the International Software Testing Qualifications Board's (ISTQB) syllabi for topics related to software testing and it's application and usage among those who perform some aspect of testing.
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.
QA is often considered that lonely department of testers whose job is to find defects before the customer does. It's not always glamorous, but QA deserves to be recognized as a key cog in the testing machine. To achieve business goals, it is Susan Bradley's view that the QA process needs to be embraced throughout the entire software development lifecycle.
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.