STARWEST 2001 - Software Testing Conference
PRESENTATIONS
Space Shuttle GPCF: A Retrospective Look
This paper is based on a recent experience implementing and testing a large new software capability in a maintenance organization which had not dealt with a large change in some time. The capability was called GPC Payload Command Filter (GPCF). While the task was completed successfully, it was not without cost in terms of schedule slips and personal angst. The purpose of this paper will be to help the verifier learn from what was done right and what was done wrong, hopefully to avoid the pitfalls and emulate the successes. |
Alan Ogletree, United Space Alliance
|
STARWEST 2001: Bug Hunting: Going on a Software Safari
This presentation is about bugs: where they hide, how you find them, and how you tell other people they exist so they can be fixed. Explore the habitats of the most common types of software bugs. Learn how to make bugs more likely to appear and discover ways to present information about the bugs you find to ensure they get fixed. Drawing on real-world examples of bug reports, Elisabeth Hendrickson reveals tips and techniques for capturing the wiliest and most squirmy critters crawling around in your software. |
Elisabeth Hendrickson, Quality Tree Software |
STARWEST 2001: Designing an Automated Web Test Environment
This paper offers an alternative to the typical automated test scripting method of "record and playback now and enhance the automation environment later." It explores a regression automation system design for testing Internet applications through the GUI, along with scripting techniques to enhance the scalability and flexibility of an automated test suite. This paper will present a basic |
Dion Johnson, Pointe Technology Group, Inc. |
STARWEST 2001: Exploratory Testing in Pairs
Exploratory testing involves simultaneous activities-learning about the program and the risks associated with it, planning and conducting tests, troubleshooting, and reporting results. This highly skilled work depends on the ability of the tester to stay focused and alert. Based on a successful pilot study, Cem Kaner and James Bach discuss why two testers can be more effective working together than apart. |
James Bach, Satisfice, Inc. and Cem Kaner, Florida Institute of Technology |
Test Progress Reporting Using Functional Readiness
Are you looking for a way to effectively set the expectations of senior management? The Functional Readiness Matrix (FRM) is a decision-making tool that offers a simple way to represent test progress based on the functional areas or features of an application. By enabling the test team to track actual test progress against the implementation goals established early on, the FRM allows for the presentation of valid test metrics to management in a way they can understand. |
Robyn Brilliant, Fannie Mae
|
Test Result Checking Patterns
Determining how a test case detects a product failure requires several test case design trade-offs. These trade-offs include the characteristics of test data used and when comparisons are done. This document addresses how result checking impacts test design. |
Keith Stobie, Microsoft |
Testing an eCommerce Shopping Cart Site
Karen Johnson takes attendees through a shopping session that recreates a number of possible scenarios-and highlights what can go wrong. She'll also explain how to prevent defects from going live on your production Web site. From securing transactions to managing cart contents, this talk is a must for anyone involved in the eCommerce arena. |
Karen N. Johnson, Peapod, Inc. |
Testing for Software Security
Software can be correct without being secure. Therefore we must be vigilant in assessing the security implications of software behavior instead of being focused on the search for specification violations. If we want to include security problems in our testing periscope, we must consider the malicious use of functionality that might be possible outside normal use of the product. The goal of this presentation is to challenge current techniques by making the testing process more attuned to, and aggressive toward, security holes. |
Herbert Thompson and James Whittaker, Florida Institute of Technology
|
Testing in the Extreme Programming World
Much attention has been given to the topic of lightweight development processes-especially eXtreme Programming (XP). Robert Martin explains the concept and significance of a paradigm that believes acceptance tests should be defined by customers, and requires developers to write the unit tests before they write the code. He then separates the difficulties from the benefits inherent in this relatively new discipline. |
Robert Martin, Object Mentor, Inc.
|
Testing Middleware Communication Platforms: XML to the Rescue?
Middleware has held a significant place in software history since its advent in the 1990s. Today, middleware is being used more and more in the B2B arena. Although XML is touted as the key ingredient to connect autonomous, heterogeneous systems together, developers and testers must keep in mind that it's not a silver bullet. This presentation will address the growing interest in middleware-based architecture, along with its benefits, issues, and pitfalls. |
Nitish Rathi, Independent Consultant and Manish Rathi, Telcordia Technologies
|