STAREAST 2007 - Software Testing Conference

PRESENTATIONS

A Flight Plan for Testing to Keep Us Safe

Just as an airplane pilot always uses a checklist when preparing for a flight, a test engineer should use a checklist when preparing for testing. Join Sid Snook, a licensed pilot, as he provides comprehensive, high-level testing guidelines, checklists, attack methods, and documentation templates. Sid presents a menu of potential testing items for you to select from based on the unique context of your testing project.
Sid Snook, Software Quality Engineering
A Unique Testing Approach for SOA Systems

Service Oriented Architecture (SOA) systems most often use services that are shared across different applications. Some services may even be supplied by third-parties, outside the direct control of a project, system, or organization. As these services evolve, organizations face the issue of ensuring the continuing proper functionality and performance of their ever-changing SOA systems.
Ed Horst, Amberpoint
An Outsource Model for Quality Assurance and Automated Testing

Efficiency and effectiveness are the cornerstones of successful quality assurance and test automation effort. Jeff Beange describes how RBC Financial Group successfully implemented a quality assurance and automation outsourcing engagement, using a blended onshore/offshore approach. He describes the details of the engagement model and outlines the risks they encountered. Jeff describes their mitigation strategy, governance structure, and the metrics used to evaluate their implementation.
Jeff Somerville, RBC Financial Group
Automated Software Audits for Assessing Product Readiness

Rather than continually adding more testing, whether manual or automated, how can you assess the readiness of a software product or application for release? By extracting and analyzing the wealth of information available from existing data sources-software metrics, measures of code volatility, and historical data-you can significantly improve release decisions and overall software quality. Susan Kunz shares her experiences using these measures to decide when and when not, to release software.
Susan Kunz, Solidware Technologies, Inc.
Behavior Patterns for Designing Automated Tests

Automated GUI tests often fail to find important bugs because testers do not understand or model intricate user behaviors. Real users are not just monkeys banging on keyboards. As they use a system, they may make dozens of instantaneous decisions, all of which result in complex paths through the software code. To create successful automated test cases, testers must learn how to model users' real behaviors. This means test cases cannot be simple, recorded, one-size-fits-all scripts.
Jamie Mitchell, Test & Automation Consulting LLC
Bugs on Bugs! Hidden Testing Lessons from the Looney Tunes Gang

Robert Sabourin finds that characters from the Looney Tunes Gang-Bugs Bunny, Road Runner, Foghorn Leghorn, Porky Pig, Daffy Duck, Michigan J. Frog, and others-provide wonderful metaphors for the challenges of testing. From Bugs we learn about personas and the risks
of taking the wrong turn in Albuquerque. Michigan J. Frog teaches valuable lessons about bug isolation and how ambiguous pronouns can
dramatically change the meaning of our requirements. The Tasmanian Devil not only teaches us about the risks of following standard
Robert Sabourin, AmiBug.com Inc
Build a Model-Based Testing Framework for Dynamic Automation

The promises of faster, better, and cheaper testing through automation are rarely realized. Most test automation scripts simply repeat the same test steps every time. Join Ben Simo as he shares his answers to some thought-provoking questions: What if your automated tests were easier to create and maintain? What if your test automation could go where no manual tester had gone before? What if your test automation could actually create new tests? Ben says model-based testing can.
Ben Simo, Standard & Poor's
Building the Test Management Office

It's the life challenge of a test manager-leading testing while keeping the work under control. If it's not poor code, it's configuration glitches. If it's not
Geoff Horne, iSQA
Business Rules-Based Test Automation

All business applications implement business rules. Unfortunately, the rules can be very dynamic due to changes in requirements by external organizations and internal forces. Wise application designers and developers do not imbed the implementation of specific business rules within applications but define, store, and maintain them as data outside the applications that use them.
Harish Krishnankutty, Infosys Technologies Limited
Challenges in Performance Testing of AJAX Applications

The AJAX model for Web applications has been rapidly gaining in popularity because of its ability to bring the richness and responsiveness of desktop applications to the Web. Because one of the key drivers for the rapid adoption of AJAX is its promise of superior performance, it is surprising that there has been very little discussion of AJAX-specific performance testing. In fact, AJAX has a significant impact on aspects of the performance testing lifecycle including definition of goals, user modeling, and test scripting.
Rajendra Gokhale, Aztecsoft

Pages

CMCrossroads is a TechWell community.

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