Conference Presentations

STAREAST 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 discusses why two testers can be more effective working together than apart. Explore the advantages of testing in pairs, including ongoing dialogue to keep both testers alert and focused, faster and more effective troubleshooting, and an excellent opportunity for a seasoned tester to train a novice.

Cem Kaner, Florida Institute of Technology and James Bach, Satisfice Inc.
Software Testing at a Silicon Valley High-Tech Software Company

This paper describes a methodology for allocating priority levels and resources to software testing and other quality activities to achieve "customer satisfaction." This methodology is based on understanding of what the market and the target users require at any point in time during the
product technology adoption life-cycle. The paper also describes the deployment by a leading market-driven company of effective software testing processes and methods that represent real-world customer issues.

Giora Ben-Yaacov and Lee Gazlay, Synopsys Inc.
System Test Measurement-What, When, How?

Elaine Soat presents an easy set of measurements to use during system testing (QA test cycle). Examine measurements taken from defect tracking and application coverage to projected testing hours versus actual testig hours. Learn how such process and measurement information is evaluated and used for proposed process improvements. Gain the ability to do comparison reporting to measure successes of process improvement within your QA test cycle.

Elain Soat, CarteGraph Systems
Managing Concurrent Software Releases in Development and Test

There is an ever-growing need to provide complex software products to customers on a short development schedule. Additionally, the customers need to be able to count on release dates for planning purposes. Instead of investing in an entirely new tool set that solves the configuration management issues associated with supporting concurrent development and support, existing tools can be used. This paper focuses on how to adapt and in some cases enhance an existing set of well-known tools to enable Lucent to excel in the market place. To this end, this project chose to implement the Fixed Interval Feature Delivery (FIFD) model of software development.

David Shinberg, Lucent Technologies
Can You Predict Danger?

Testers are in a position to see danger coming. Speaking up early about risks that others may not see can save a project. In this article Yogita Sahoo looks at the problem of NOT speaking up, and discusses the unique position of the test team in preventing failures.

Yogita Sahoo's picture Yogita Sahoo
Software Development Lifecycle: Defect and Test Case Measurement

This article focuses on how to manage the defect and test case measurement during the software development lifecycle. This should be a practical resource for software developers and project managers.

Steve Miller

Pages

CMCrossroads is a TechWell community.

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