Conference Presentations

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
GUI Application Modeling for the Automatic Generation of Test Scripts

Explore two different methods for modeling a GUI application's user behavior and variable input to automatically generate test scripts. Brad Dasko demonstrates both Lucent Technologies proprietary modeling tool and a commercially available modeling tool integrated with a commercially available test execution harness. Discover the characteristics to look for when selecting the right modeling tool.

Brad Dasko, Lucent Technologies
You Want It When? Negotiating Test Schedules

To most software developers, testers and QA managers, time is one of the most precious commodities they have. Greg Pope takes a look at negotiation tactics and other tricks of the trade that help test engineers and QA managers find more time to do their job better. Learn how realistic software process scheduling and adequate testing can increase product quality.

Greg Pope, Azor, Inc.
Paradigms of Black Box Software Testing

In this practitioner-oriented talk, Cem Kaner uses observations and anecdotes from his experiences to broaden and diversity your approach to the design and development of the class of tests called "Black Box." Listen as he explores the conceptual differences among significantly different approaches to testing at the functional and system level without using knowledge of the program code. Examine examples that will guide your thinking about testing within a particular paradigm. Discover the questions that a tester might ask under these approaches to design better tests. Learn what makes for a great test case or test suite under a paradigm.

Cem Kaner, J.D., Ph.D.
T-Shirt versus Kimono in Software Testing

Can your testing efforts eliminate 99.98% of the bugs made during software development? If not, are there cost-effective methodologies that you can use to reach this goal? Tsuneo Yamaura explains current methods that make this goal attainable, and draws on personal experience to show how it can be done in less time using fewer personnel than you might think. Learn about the differences and similarities between American and Japanese software testing methods and discover how features of each can be combined to form a new and more efficient software testing process.

Tsuneo Yamaura, Hitachi Software
Integration Testing for Enterprise Resource Planning (ERP) Systems

Many companies make the assumption that Enterprise Resource Planning (ERP) systems need less testing because they are, after all, purchased software. Unfortunately, the systems are highly configurable and changes in one module can have drastic effects in another module. Based on her experiences, Linda Malchow describes the test strategy and results of a $115 million SAP project and explores the lessons learned.

Linda Malchow, Shell Services International
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
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.
STARWEST 1999: The Result of Testing Is Not Quality!

The result of testing is not quality; it's information! You can have the best test system in the world, find all of the defects, not do anything with that information, and still ship an inferior product. Learn how a decision and information-driven approach to designing an integrated test strategy will drive higher quality, data-driven product quality, and risk decisions.

Joni Ohta, Hewlett-Packard
Identifying Critical Requirements Using FMEA

The Failure Mode and Effects Analysis (FMEA) process was developed by the auto industry to prevent quality problems with their products. Discover how engineers in other industries use FMEA to analyze their manufacturing process or product and how to apply the method to software. Learn how to identify potential software failure modes and their causes, and assess the effects these failures might have on your customers.

Edith Maverick-Folger, LifeScan Inc.

Pages

CMCrossroads is a TechWell community.

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