STAREAST 2002 - Software Testing Conference


A Crash Team Approach to Effective Testing

Rapid changes and stunted delivery deadlines are always challenging software testers. To catch up, software testing must take a different approach without cutting corners-hence, the crash team. The crash team approach focuses on integration testing and runs in parallel with functional testing. Its technique discovers system problems early, problems that would be hard to find with traditional methods. It also supports the spiral development model that's been adopted in many rapid application development environments.

Pei Ma, WeiMa Group LLC
Adventures in Session-Based Testing

This paper describes the way that a UK company controlled and improved ad-hoc testing, and was able to use the knowledge gained as a basis for ongoing, product sustained improvement. It details the session-based methods initially proposed, and notes problems, solutions and

James Lyndsay, Workroom Productions
Applying Testing Expertise to the Retrospective Goldmine

Digging up postmortem project data is like mining for gold. The returns can be significant and long-term because this is where your best (and worst) practices really shine. By allowing your test groups to drive the retrospective activities, improvements can finally be built into the product lifecycle model instead of rotting in a postmortem report. By improving retrospective facilitation and follow-up, you'll ultimately improve your software lifecycle process.

Nick Borelli, Microsoft Corporation
Automated Testing Framework for Embedded Systems

Is it possible to use an "open architecture" automation test tool to avoid the pitfalls of testing in the embedded, real-time world? It is now. In this session, Michael Jacobson presents an architecture that allows existing testing tools to be connected together as components in an automated testing framework targeted for embedded systems using network communications. He shows you how existing testing tools can become servers with just a couple lines of code.

Michael Jacobson, Northrop Grumman Corporation
Automated Web Testing Strategies

As Web applications move from static content to dynamic transactions, the risk of failure increases while cycle time collapses. Although automation is the ideal solution for this combination, those who've ventured into automated Web testing have discovered a whole new world of unexpected challenges. For instance, dynamic page layouts and content frustrate test automation requirements for predictability and repeatability, while the lack of meaningful-let along consistent-object names further complicates consistent execution.

Linda Hayes, WorkSoft

Basis Path Testing for Structural and Integration Testing

Basis path testing is a structural testing technique that identifies test cases based on the flows or logical paths that can be taken through the software. A basis path is a unique path through the software where no iterations are allowed; they're atomic level paths, and all possible paths through the system are linear combinations of them. Basis path testing uses a Cyclomatic metric that measures the complexity of a source code unit by examining the control flow structure.

Theresa Hunt, The Westfall Team
Beyond Record and Playback: The Behind-the-Scenes View of Web Test Automation

Web-based test automation goes well beyond the mere action of recording manual test scripts and replaying them. Test automation is more of a development process than the normal quality assurance or test effort. This presentation takes an in-depth look into what it takes to truly automate Web site testing. You'll explore the following building blocks: planning/analysis, design/development, implementation, and support.

Michael Prisby, UPS
Blind Alleys in Automated Testing

More often than not, even modest software test automation efforts fail to achieve their goals. Usually these project shortcomings happen because the introduction of test automation reduces the effectiveness of the test group, thereby reducing the number of tests and the number and complexity of product defects found. Several common misconceptions about the value and techniques for software test automation contribute to this problem. Douglas Hoffman explores some of the more common issues and addresses how to recognize and avoid them.

Douglas Hoffman, Software Quality Methods LLC
Calculating the Return on Investment of Testing

While revenues, cash flow, and earnings are vital statistics of a company's well-being, they're the by-product of what the company actually offers up as a product or service. Therefore, if the offering doesn't produce ROI for the customer, it doesn't represent a viable business opportunity. In this session, take a look at testing from the perspective that it's a service provided to your company.

James Bampos, VeriTest Inc/Lionbridge Technologies and Eric Patel
Career Path Activities for Test Professionals

Ever wonder how some people seem to find the time to always do that "little extra" to benefit their careers? Have you ever thought about writing an article, speaking at a conference, or even teaching a course, but didn't know where to begin? There are lots of ways to jump-start your career through professional development activities that benefit both you and your employer. Learn how your participation in these activities can enhance your career and market your company.

Eric Patel, RapidSQA


CMCrossroads is a TechWell community.

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