STARWEST 2002 - Software Testing Conference


Smarter Testing with the 80:20 Rule

It may not be a silver bullet, but knowledge of the 80:20 rule, and the special variation that applies to software testing, can help you dramatically improve your testing-and your entire software development lifecycle. This session explains what the rule is using real-life examples, then shows you how to use it within your test team. Erik Petersen then investigates the different ways the rule is being used by leading testers and developers today. This talk has motivated some Australian testers to change the way they test.

Erik Petersen, Specialist

STARWEST 2002: How to Break Software

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.

James Whittaker, Florida Institute of Technology

STARWEST 2002: How to Break Software Security

This presentation addresses classifying, finding, and attacking software security vulnerabilities.

James Whittaker, Florida Institue of Technology and Herbert Thompson, System Integrity

STARWEST 2002: Writing Better Defect Reports

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.

Kelly Whitmill, IBM
Tackling the Test Automation Challenge: The Centralized Team Approach

There's no doubt that setting sail into the test automation universe is a challenging endeavor indeed. In this session, Dave Torresan provides a true account of the challenges faced by his team in becoming his company's centralized test automation specialists. After dispelling some of the myths of test automation, he describes how his team was established and the prerequisites you'll need before attempting to do the same.

Dave Torresan, RBC Financial Group
Test Automation: Reducing Time to Market

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.

James Dougherty and Keith Haber, Lexis-Nexis
Test Lab Stability through Health Check Test Automation

New application code is installed on Sunday. Your test team arrives on Monday to run test scripts and certify the release. Unfortunately, one environmental problem leads to another and suddently it's Friday before you run your first test script against the new code. Does this sound familiar? One way to buck this trend is to run daily health checks on the test environment. By running daily health checks, you'll minimize the time required to test new application code installs.

John Rappa, Verizon Communications
Testing a Distributed Application Written in Embedded Windows CE

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.

Jim Walters, BSQUARE Corporation
Testing and QA with eXtreme Programming Practices

A Java development project team had proceeded to 25% completion using the traditional waterfall development method when they were suddenly asked to adopt eXtreme Programming (XP) practices and continue with the project. While XP may be good for management because it provides good visibility on the product, it may not be so good for developers who have to change their processes quickly. And it certainly presents a challenge to QA and testing, whose roles are not well defined.

Sanjay Srinivas, Sabre Inc

Testing for Section 508 Accessibility Compliance

Section 508 of the Rehabilitation Act is a key issue affecting testing for more and more companies. Section 508 requirements include a set of Web design guidelines that allow users with various disabilities to more easily access information from the Web. Adoption language by the federal government in June 2001 stated that all federal agency Web sites must be 508 compliant-but the push for accessibility is spreading to state government and the private sector as well.

Bill Chandler, Rational Software


AgileConnection is a TechWell community.

Through conferences, training, consulting, and online resources, TechWell helps you develop and deliver great software every day.