Jamie Mitchell explores an underused and often forgotten test type-white-box testing. Also known as structural testing, white-box techniques require some programming expertise and access to the code. Using only black-box testing, you could easily ship a system having tested only 50 percent or less of the code base. Are you comfortable with that? For mission-critical systems, such low test code coverage is clearly insufficient. Although you might believe that the developers have performed sufficient unit and integration testing, how do you know that they have achieved the level of coverage that your project requires? Jamie describes the levels of code coverage that the business and your customers may need-from statement coverage to modified condition/decision coverage. He explains when you should strive to achieve different code coverage target levels and leads you through examples of pseudo code.

Would your marketing department like to know which website feature will excite online customers to buy more products, return to your site again and again, and increase revenue and profits? Harish Narayan describes how his team uses risk-based testing and statistical test design to optimally check features deployed with multiple website options. At Vistaprint, their measurement-focused marketing department requires live production tests of multiple web options-split runs in their jargon-that expose different features for different customer sessions; they choose to retain the one that “wins” to maximize returns. Preproduction testing of split-run features, especially when multiple runs are deployed in every release, presented challenges for Vistaprint’s testers.

The best software development teams find ways for programmers and testers to work closely together to build quality into their software. These teams recognize that programmers and testers each bring their own unique strengths and perspectives to the project. However, working in agile teams we need to unlearn many of the patterns that traditional development taught us. In this interactive session with Nate Oster, you learn how to use the agile practice of "concurrent testing" to overcome common "testing dysfunctions" by having programmers and testers work together-rather than against each other-to deliver quality results throughout an iteration. Join Nate and practice concurrent testing with games that demonstrate just how powerfully dysfunctional approaches can act against your best efforts and how agile techniques can help you escape the cycle of poor quality and late delivery.

Are you testing an application or web site whose complexity has grown exponentially through the years? Is your test data efficiently and effectively supporting your test suites? Does the test data reside in systems not under your direct control? Learn how the WellsFargo.com test team integrated test data management processes and provisions to gain control over test data in their very large and complex web system environment. Join Ron Schioldager to explore the lifecycle of data, its relationship to effective testing, and how you can develop conditioned, trusted, and comprehensive test data for your systems. Learn about the tools Wells Fargo developed and employs today to support their test data management process, enabling them to maintain a shorter data maintenance cycle while improving their test reliability.