STAREAST 2006 - Software Testing Conference

PRESENTATIONS

The Art of Exploration

In order for exploratory testing to be perceived as a valuable process by all stakeholders in the organization, we need to make sure the result of that testing-our documentation-is presented with the same professionalism and attention to detail that distinguishes an artistic masterpiece from a paint-by-number kit. David Gilbert discusses the practical steps testers can take to improve the perceived value of exploratory testing in their organizations.

David Gilbert, Sirius Software Quality Associates, Inc.
The Last Presentation on Test Estimation You Will Ever Need to Attend

Estimating the test effort for a project has always been a thorn in the test manager's side. How do you get close to something reasonable when there are so many variables to consider? Sometimes, estimating test effort seems to be no more accurate than a finger in the wind. As Geoff Horne likes to call it, the "testimation" process can work for you if you do it right.

Geoff Horne, Geoff Horne Testing

The Software Vulnerability Guide: Uncut and Uncensored

Warning: This talk contains graphic examples of software failure . . . not suitable for the faint of heart. This "no holds barred" session arms testers with what they really need to know about finding serious security vulnerabilities. Herbert Thompson takes you on an illustrated tour of the top twelve security vulnerabilities in software and shows you how to find these flaws efficiently. Each vulnerability is brought to life through a live exploit followed by a look at the testing technique that would have exposed the bug.

Herbert Thompson, Security Innovation LLC
Translating Business Risks into a Risk-Based Test Plan

We all know that testing should be based on business risks. In practice, test managers often go from those risks to test coverage in an ad-hoc, intuitive way. Instead, by taking a step-by-step approach, you can improve coverage and better prioritize your tests. After translating business risks into product risks and establishing the required test coverage, you select the appropriate techniques and estimate test effort.

Ruud Teunissen, POLTEQ IT Services BV

Trends, Innovations and Blind Alleys in Performance Testing

Join experts Scott Barber and Ross Collard for a lively discussion/debate on leading edge performance testing tools and methods. Do you agree with Scott that performance testing is poised for a great leap forward or with Ross who believes that these "silver bullets" will not make much difference in resolving the difficulties performance testing poses? Scott and Ross will square off on topics including commercial vs.

Scott Barber, PerTestPlus, and Ross Collard, Collard & Company

Using Production Failures to Jump Start Peformance Test Plans

Learning from a production system failure is not a model MassMutual Financial Group would have chosen. However, when one of their key applications failed under load in production, they turned on a dime and changed their performance testing approach, focus, and capabilities. Let’s set the scene: They ran large numbers of transactions through a performance test tool and, then, went live with a new application that was to be used by all their key users.

Sandra Bourgeois, Massachusetts Mutual Life Insurance Company
You'll Be Surprised by the Things Testers Miss

Why do some bugs lie undetected until live operation of the software and then almost immediately bite us? Drawing on instances of problems that were obvious in production--but missed or nearly missed in testing, James Lyndsay can help you catch more bugs starting the day you return to work. James first describes bugs not found because too little time is spent on testing.

James Lyndsay, Workroom Productions
Your Development and Testing Processes Are Defective

Verification at the end of a software development cycle is a very good thing. However, if verification routinely finds important defects, then something is wrong with your process. A process that allows defects to build up-only to be found and corrected later-is a process filled with waste. Processes which create long list of defects are . . . defective processes. A quality process builds quality into the software at every step of development, so that defect tracking systems become obsolete and verification becomes a formality.

Mary Poppendieck, Poppendieck LLC

Pages

StickyMinds is a TechWell community.

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