Conference Presentations

Moving from Conventional to Object-Oriented Testing

Elfriede Dustin outlines the steps required for a test team to transition from traditional test methods to an object-oriented test methodology. Learn how to best make this transition by addressing several pertinent questions and issues, including a test process suited to object-oriented development.

Elfriede Dustin, Computer Sciences Corporation
Use Case Derived Test Cases

Use cases are used to specify the required functionality of an object-oriented system. Test cases that are derived from use cases take advantage of the existing specification to ensure good test coverage of the system. Discover what additional test cases are required besides the use case derived ones.

Dave Wood, Harris Corporation
Stress Testing Enterprise-wide SAP Applications

Based on real-life examples, this presentation examines the overall approach to stress testing an enterprise-wide global application using SAP. Learn about the objectives and scope of stress testing and how to build stress test models and design stress test scenarios. Test documentation, execution strategies, and data analysis techniques are described.

Mike Swanson, Guidant Corporation
Evolution of a Management Tool for Manual Tests

A test management tool is essential, even for manual tests, to ensure quality software. The process of finding the best tool, however, can all too often be an overwhelming task. Sarah Pagel discusses the process her company went through to find the right tool and identifies the mistakes that were made along the way.

Sarah Pagel, McHugh Software International
STAREAST 1999: Test Estimation

How often have you been asked the question, "When will system testing be completed?" without knowing the final scope of the functionality, when the system will be ready for testing, and what test resources are available. In this double track session, learn how to develop realistic and credible estimates. Learn why accurate estimates are a critical survival skill for test professionals and managers.

Ross Collard, Collard & Company
Case Studies Testing Third Party Software

Testing software can be a daunting task under normal circumstances. When a third party develops the software, managing the software test process can become nearly impossible. Through four case studies, learn how one unit of Sony Electronics has effectively handled outsourced development over the past five years, providing invaluable lessons for both large and small projects.

Samuel Shore, Sony Electronics, Inc.
Getting Buy-In for Acceptance Testing

Experienced testers know that acceptance testing is important, but often only the testers appear to be really concerned. Geoff Quentin draws on nearly 20 years of experience persuading management, users, and even developers that an early start to the acceptance test process is the most cost-effective way to implement testing. Learn how to identify the key issues to help you persuade managers and users to invest their time and resources in acceptance test planning and execution.

Geoff Quentin, QBIT Limited
A Low-Tech Testing Dashboard

One of the fundamental problems in testing is reporting progress in a way that non-testers and busy executives can understand and use. Testing progress should be reported in such a way that users and clients are not overwhelmed with detail or theory. James Bach shows how a concise test cycle dashboard, using qualitative metrics, is one way to approach the problem. Learn how to design such a dashboard and the risks and benefits associated with it. Discover how a dashboard helps the whole team own the test strategy and brings the project to a successful conclusion.

James Bach, Consultant
Get More Out of Existing Tests

Learn how to leverage the defect-finding and confidence-building power of existing tests by inducing changes that should make no difference to results. This principle is used in "algorithmic stress modes" within InCert Software Corporation to test their own binary instrumentation tool.

Richard Schooler, InCert Software Corporation
How to Get Developers to Unit Test

Test managers often lament that developers fail to thoroughly unit test their code. Bill Pearce covers techniques to sell the need for unit testing, implement guidelines and entry criteria, and reduce inter-department friction. Learn how to influence and institute changes in the development process and increase the level of unit testing by development staff.

Bill Pearce, Corbel

Pages

AgileConnection is a TechWell community.

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