STARWEST 2006 - Software Testing Conference

PRESENTATIONS

STARWEST 2006: All I Need to Know about Testing I Learned from Dr. Seuss

Through the stories and parables of Theodor Geisel, we can learn simple, yet remarkably powerful approaches for solving testing problems. In a tour of common issues we encounter in testing-test planning, staff training, communications, test case design, test execution, status reporting, and more, Robert Sabourin explains how you can apply lessons from the great books of Dr. Seuss to testing. Green Eggs and Ham teaches us combinations; Go, Dog,
Robert Sabourin, AmiBug.com Inc
STARWEST 2006: Branch Out Using Classification Trees for Test Case Design

Classification trees are a structured, visual approach to identify and categorize equivalence partitions for test objects to document test requirements so that anyone can understand them and quickly build test cases. Join Julie Gardiner to look at the fundamentals of classification trees and how they can be applied in both traditional test and development environments. Using examples, Julie
Julie Gardiner, QST Consultants Ltd.
STARWEST 2006: Improving the Skills of Software Testers

Many training courses include the topic of soft skills for testers, specifically their attitudes and behaviors. Testers are told that to be effective they need a negative mindset and a negative approach. Krishna Iyer challenges this belief. He believes testers must be creative rather than critical; curious rather than destructive; and empathetic rather than negative.
Krishna Iyer, ZenTEST Labs
STARWEST 2006: Lightning Talks: A Potpourri of 5-Minute Presentations

Lightning Talks are nine five-minute talks in a fifty-minute time period. Lightning Talks represent a much smaller investment of time than track speaking and offer
Robert Sabourin, AmiBug.com Inc
STARWEST 2006: Positioning your Test Automation Team as a Product

Test automation teams are typically created with the expectation of facilitating faster testing and higher product quality. To achieve these goals, the test
automation team must overcome many challenges--stale test data, burdensome test script maintenance, too-frequent product upgrades, insufficient resources, and unfamiliarity with the systems under test. Satya Mantena describes a creative approach to test automation that overcomes
Satya Mantena, Nielsen Media Research
STARWEST 2006: Session-Based Exploratory Testing: A Large Project Adventure

Session-based exploratory testing has been proposed as a new and improved approach to software testing. It promotes a risk-conscious culture that focuses on areas where there are likely to be defects and allows for rapid course corrections in testing plans to accommodate testing "discoveries", feature-creep, and schedule changes.
How can a test manager take a highly talented manual testing team, accustomed to running test scripts, and
George Bliss, Captaris
STARWEST 2006: Test Estimation: Painful or Painless?

As an experienced test manager, Lloyd Roden believes that test estimation is one of the most difficult parts of test management. In estimation we must deal with destabilizing dependencies such as poor quality code received by testers.
Lloyd Roden, Grove Consultants
STARWEST 2006: The Art of SOA Testing: Theory and Practice

SOA (Service Oriented Architecture) based on Web Services standards has ushered in a new era of how applications are being designed, developed, and deployed. But the promise of SOA to increase development productivity poses new challenges for testers, challenges dealing with multiple Web Services standards and implementations, legacy application (of unknown quality) now exposed as Web services, weak or non-existent security controls, and services of possibly diverse origins chained together to create applications.
Rizwan Mallal, Crosscheck Networks
Step Away from the Tests: Take a Quality Break

Designing, implementing, and executing tests is critically important, but testers sometimes need to take a break. John Lambert describes four un-testing techniques that can quickly improve quality: watching bugs, helping
developers, talking to other testers, and increasing positive interactions. Watching bugs enables us to see defect patterns that might otherwise go unnoticed. Helping developers allows you to understand their process and help
John Lambert, Microsoft Corporation
Testing Web Applications for Security Defects

Approximately three-fourths of today’s successful system security breaches are perpetrated not through network or operating system security flaws, but through
customer-facing Web applications. How can you ensure that your organization is protected from holes that let hackers invade your systems? Only by thoroughly testing your Web applications for security defects and vulnerabilities. Brian
Brian Christian, SPI Dynamics Inc

Pages

CMCrossroads is a TechWell community.

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