STAREAST 2005 - Software Testing Conference

PRESENTATIONS

Rapid Bottleneck Identification for Successful Load Testing

Rapid bottleneck identification is a methodology that allows QA professionals to very quickly uncover Web application limitations and determine what impact those limitations have on the enduser experience. Starting with the premise that every application has a scalability limit, this approach sets out to quickly uncover where those limitations are and to suggest corrective action.
Joe Fernandes, Empirix
Software Inspections for the Common Folk

Many have tried to implement software inspections in commercial development shops ... and failed. Common reasons include “not enough resources," "takes too long," and "makes people uncomfortable." Ron Yun demonstrates how ADP has implemented both "full” and "lite" inspection practices that reduce resources, automate many aspects of the process, and help take the personality issues out of the process. With their practices, ADP completes inspection meetings quickly and has eliminated all manual forms.
Ronald Yun, ADP
STAREAST 2005: Planning for Successful Test Automation

You have the automation tool. You have the right technical skills. You have the application experts at your disposal. It’s time to jump in and start coding! Or is it? Many well-intentioned test automation efforts fail due to a lack of planning. Steve Walters describes his practical approach for developing an overall test automation strategy. Learn how to plan for automation success, select the right tests to automate, and prioritize them for a faster return on investment.
Steve Walters, Dell Computer Corporation
STAREAST 2005: Testing Dialogues - Management Issues

As a test manager, are you struggling at work with a BIG test management issue or a personnel issue? If so, this session is for you. "Testing Dialogues-Management Issues" is a unique platform for you to share with and learn from test managers who have come to STAREAST from around the world. Facilitated by Esther Derby and Robert Sabourin, this double-track session takes on management issues-career paths for test managers, hiring, firing, executive buy-in, organization structures, and process improvement. You name it!
Facilitated by Esther Derby and Robert Sabourin
STAREAST 2005: Testing Dialogues - Technical Issues

Is there an important technical test issue bothering you? Or, as a test engineer, are you looking for some career advice? If so, join Esther Derby and Robert Sabourin, experienced facilitators, for "Testing Dialogues-Technical Issues." Practice the power of group problem solving
Facilitated by Esther Derby and Robert Sabourin
Strive for Quality in System Testing: A Top 10 List

Finding non-functional, system level problems before a system is delivered-and early enough to allow for low cost corrections-is a perennial testing issue. You need a systematic approach to system testing that keeps key system test objectives visible and assigns the correct priority among other test activities. Based on his team's experiences at IBM, Jerry Cobry describes how there needs to be a special mindset for system testing and describes some of the challenges they faced.
Jerry Cobry, IBM Corporation
Structured Testing within the Rational Unified Process

Many organizations have adopted, or are in the process of adopting, the Unified Process (UP) and, in particular, the Rational Unified Process (RUP). The test process defined within UP/RUP differs from more traditional, structured testing processes such as TMap (Test Management Approach) in Europe and STEP™ (Systematic Test and Evaluation Process) in the US. Tim Koomen, who has operated within these and other development lifecycle and test processes,
Tim Koomen, Sogeti - Netherlands
System Implementation Details: Understand, Test, Ignore

Join John Lambert to see examples of implementation details that cause problems in GUI-based applications, APIs, and Web systems. Find out how you can develop skills that will help you test your current product and will transfer to entirely different products in the future.
John Lambert, Microsoft Corporation
Test Driven Development (TDD) for Secure Applications

Test Driven Development (TDD) has emerged as a successful productivity technique for development teams. As a unit testing methodology, TDD prescribes a simple three-step process of (1) develop test, (2) write code, and (3) re-factor the code. In a question-and-answer tag-team
James Whittaker, Florida Institute of Technology
Test Improvement for Highly Reliable NYSE Trading Systems

With billions of dollars changing hands every day, financial trading systems demand extremely high accuracy and reliability. So, how do you improve test process performance in the areas of time to market and efficiency and at the same time reduce failures? Over the last three years, using process and project measurement data as a guide, SIAC has focused on doing exactly that.
Steve Boycan, SIAC

Pages

CMCrossroads is a TechWell community.

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