Conference Presentations

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
Creating Testable Requirements

A project manager strides purposefully into your office. "This disk has the latest and greatest release of our software. Please test it. Today.” You say, "Okay, sure ... what does it do?" The manager stops in his tracks and says, "Uh, the usual stuff..." Sound familiar? We've run into this situation as employees and as consultants. And we've seen testers take the disk, stick it in the drive, and just start testing away. That's testing in the dark. We think there are approaches that are more productive. When we test or manage testers, we plan the testing tasks to know what value we can get from the testing part of the project. Let's try turning on the lights!

Johanna Rothman, Rothman Consulting Group, Inc.
Database Design for Test Information Management

Every test organization must report its findings in a concise, timely, and comprehensive way. Using a relational database to manage test information can dramatically reduce the cost and effort of such reporting. Learn the pitfalls to avoid when designing a test information database. Examine a concrete example of good test database design that you can apply immediately.

Stephen Liss, Motorola
Understanding Test Oracles

To get value from test execution, the results must be determined and evaluated. This presentation describes the dimensions and alternative approaches to results. It identifies three types of oracles and more than ten different reference functions. Listen as David Gelperin discusses design for testability issues relating to lower-cost oracles and the elements of an oracle strategy.

David Gelperin, Software Quality Engineering
Mutation Testing: A New Approach to Automatic Error-Detection

Mutation Testing is a proven and powerful method for finding errors in software programs. Adam Kolawa describes the process of Mutation Testing ("re-writing" source code) and how a new approach to this technology, creating equivalent mutants, is applied. Mutation Testing can assist your company where it matters most-the bottom line.

Adam Kolawa, ParaSoft Corporatin
Test Coaching-- Helping Users and Developers with Early Testing

All too often, we wait to involve the testing and user groups until it is too late and quality is a dream instead of a reality. Learn some methods that proved successful for USA Group that bridged the gap between the developers and users by having "test coaches" working with both teams to bring these two worlds together. Create a "common" strategy for building a quality system early.

Shelley Auld, USA Group

Pages

CMCrossroads is a TechWell community.

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