Organizations spend countless hours in load testing exercises with the intent of finding and fixing system bottlenecks to improve overall performance.  But how much time is spent in the process of preparing and executing the test versus finding and fixing real issues.

Finding time to test the basic functionality, performance, and security of a system is difficult enough, so how do you find time to add internationalization (i18n) and localization (l10n) testing? Today’s world is very small, and you may already have international users in your target market.

To assist in risk analysis, prioritization of testing, and test reporting (telling your testing story), you need a thorough Test Coverage Outline (TCO)—a road map of your proposed testing activities. By creating a TCO, you can prepare for testing without having to create a giant pile of...

We've all been there. You work incredibly hard to develop a feature and design tests based on written requirements. You build a detailed test plan that aligns the tests with the software and the documented business needs. When you put the tests to the software, it all falls apart because the requirements were updated without informing everyone. But help is at hand. Enter business-driven development and Cucumber, a tool for running automated acceptance tests. Join Mary Thorn as she explores the nuances of Cucumber and shows you how to implement specification-by-example, behavior-driven development, and agile acceptance testing. By fostering collaboration for implementing active requirements via a common language and format, Cucumber bridges the communication gap between business stakeholders and implementation teams.