STARWEST 2002 - Software Testing Conference

Trying to figure out how you can become a more effective tester? That's easy: Become a better bug hunter. This tutorial uncovers the root cause of software failure and offers specific, prescriptive strategies you can use to expose bugs-and system interfaces-to testing scrutiny. James Whittaker shows you examples of real bugs and diagnoses their cause, while giving you the opportunity to ask questions based on your own determinations.

Why is it that some testers get better responses from developers than others? Part of the answer lies in their defect reports. Following a few simple guidelines can smooth the way for a much more productive environment. That's because the objective shouldn't be to write the perfect defect report, but to write an effective defect report that conveys the proper message, gets the job done, and simplifies the process for everyone. It's important that you use this report to ask and answer the right questions.

Test automation has remained a popular topic for discussion among testers. In this session, Jim Dougherty walks you through the development of an actual, first-stage automation process. He also explains how to facilitate the formation of an automation team in a lessons-learned study of how to get from here to there, and why you should. He also explains how his newly formed team developed its processes, action plan, and benefits-derived reporting.

How will your Windows CE application perform once you start deploying it in the "real world"? This session addresses the many issues developers face when building distributed applications using embedded Windows. The ability to set up your application simulating the "real world" in a controlled lab environment using automated testing tools-along with the option to troubleshoot-saves critical time and money. Don't forget to be aware of the many pitfalls you face.