STARWEST 1999 - Software Testing Conference


A Baker's Dozen Questions to Ask Before Writing a Test Plan

Have you ever needed to generate a test plan for a project or product you knew little about? Have you ever felt grossly unprepared when starting a testing project? If so, this presentation will help you. Howie Dow presents thirteen questions to help evaluate test readiness. Learn when and how to answer these questions before starting a test plan.

Howie Dow, Compaq Computer Corporation
Automating Testing Across The Enterprise

This presentation draws the following conclusions:

  • Simplify Complex Environments by Breaking Them Down into Components
  • Test for Regression
  • Test for New Functionality
  • Use Test Automation for Inter- and Intra-Application/
    Environment Testing
  • Business User Involvement is Key!
Andrew Pollner, ALP International Corporation

Birth of a Test Organization

Discover how a new test group becomes respected within an existing IT infrastructure. Learn how to crawl, take your first steps, and walk before attempting to run. Lisa Bresko discusses approaches such as her "Hugs for Bugs" campaign that helped build cooperation with applications development.

Lisa Bresko, Infoworks
Code Coverage: Don't Release Without It

How do you know if you have done a good job of testing your product? Banged around on the product and found no problems? NOT! The only way to assure you are fully testing your product is by running code coverage numbers while you test. Only code coverage gives you the data that confirms your test cases are hitting the mark.

Brent Coursey, BMC Software
Compressing Test Execution Time to a 24-Hour Cycle

Software development projects face a growing trend of tighter schedules, more complex environments, and increased time-to-market pressures. Thomas Poirier presents a composite case study that explores how frequently encountered situations can severely impact the duration of the Test Execution Cycle (TEC). Learn strategies and tactics to shorten the TEC to within a 24-hour cycle without sacrificing test coverage.

Thomas Poirier, Conduciv inc.
Cost-Benefit Analysis of Test Automation

There are many factors to consider when planning for test automation. It is important to understand the potential costs and benefits before undertaking the kind of change that automation implies. In this presentation, you will explore financial, organizational, and test effectiveness impacts observed when software test automation is installed. Listen to suggestions and examples to help you decide when automation is beneficial to your organization.

Douglas Hoffman, Software Quality Methods, L.L.C.
Defect Management in Development and Test

Defect management can leverage development and test costs with 10 to 1 benefit-to-cost margins or better. Most organizations never achieve these results because they focus on product metrics rather than process metrics. Ed Weller discusses data analysis and project management decisions using data from the full development cycle. Explore examples of data analysis techniques useful for project, product, and process analysis.

Ed Weller, Bull Worldwide Information Systems

Effective Testing for Java-based Web Software

This presentation addresses the following: What is Java software, anyhow? How do you test Java? How do you build testable Java applets/applications?

Sam Guckenheimer, Rational Software
Ensuring Software Maturity Via Software State Criteria

You can increase confidence in software releasability (quality, time-to-market) by implementing processes that allow you to gauge and benchmark software maturity via software state models. Software state transition is subject to established criteria, such as software engineering, best practices, etc. Learn how ADP successfully implemented software releasability improvements by defining and implementing transition benchmarks including entry/exit criteria.

Fareed Shaikh, Automatic Data Processing
Establishing the Test Process in a Young Software Organization

Establishing a test process in a young software organization with ongoing projects is a complex and intensive activity. It may be difficult to make upper management understand the test team purposes and to establish good relationships with the development, quality assurance, and configuration management teams. Explore some of the problems and lessons learned during a two-year span of test activity. Learn useful ideas from other testers who have been there, done that.

Enrico Omar Casati, Spazio01 S.P.A.


CMCrossroads is a TechWell community.

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