|
|
Basis Path Testing for Structural and Integration Testing Basis path testing is a structural testing technique that identifies test cases based on the flows or logical paths that can be taken through the software. A basis path is a unique path through the software where no iterations are allowed; they're atomic level paths, and all possible paths through the system are linear combinations of them. Basis path testing uses a Cyclomatic metric that measures the complexity of a source code unit by examining the control flow structure. Basis path testing can also be applied to integration testing when software units/components are integrated together. You'll see how the use of the technique quantifies the integration effort involved as well as the design-level complexity.
|
Theresa Hunt, The Westfall Team
|
|
|
Selecting Re-Tests for Corrected Defects Using Coverage Analysis Data Topics covered in this presentation include: Why and when to trim the test suite; How to select tests to run with
Coverage Analysis System (CAS) tools; Testing Code Changes before push; How we create CAS databases; and When CAS methods are not useful.
|
Jim Boone, SAS Institute, Inc.
|
|
|
The Simplest Automated Unit Test Framework That Could Possibly Work Everyone pays lip service to the importance of unit testing, but rarely do developers actually integrate unit testing into their daily routine. In the spirit of eXtreme Programming, this presentation offers a simple two-class framework for automating unit tests in three popular languages: C++, Java, and C. No GUI, no templates, just a fast and productive way of organizing and running suites of unit tests. You'll walk away wondering how you have done without this simple technique for so long.
|
Chuck Allison, Utah Valley State College
|
|
|
Software Code Inspection for Defect Prevention Thousands of hours are spent testing, but most software professionals find that traditional testing simply isn't enough to ensure code quality. This presentation gives software professionals a complementary approach: software inspection. Learn how software inspection differs from traditional testing, and gain an understanding of principal inspection techniques.
|
Jasper Kamperman, Reasoning
|
|
|
Is Quality Negotiable? Experiences of an eXtreme Programming Tester If you want a higher quality product in an eXtreme Programming (XP) project, you must be prepared to pay a higher price. We make decisions and compromises based on quality versus cost every day. Extreme programming teams are driven to do their best work, but customers have the right to specify and pay for only the level of quality they require. This presentation explores ways to resolve these two potentially conflicting points of view.
|
Lisa Crispin, BoldTech Systems
|
|
|
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
|
|
|
Managing the Test Effort Using Requirements-Based Testing Metrics It's difficult to quantify the true state of a test effort. Often, it's measured by quantity of work combined with deadline compliance. But if this is the case, then the true level of quality remains unknown. The Requirements-Based Testing (RBT) process offers a set of metrics that can be utilized throughout the development cycle. These metrics can provide an accurate picture of the test effort at any given time.
|
Gary Mogyorodi, Bit Inc.
|
|
|
A Common Sense Approach to Statistical Process Control As maturing software organizations begin using statistical process control (SPC) techniques to stabilize processes and manage quality, it's imperative that their SPC implementation approach be carefully considered, especially since it involves the use of statistical analysis techniques that are unfamiliar to most people. This presentation describes an approach to implementing SPC that maximizes project personnel involvement through creative delegation, provides for the timely utilization of the data, and keeps management well informed but not overburdened.
|
Steven H. Lett, The David Consulting Group
|
|
|
Problem Resolution Cycle Time Optimization No matter how well we plan and execute software development, defects are generated and can escape to the customers. Failure to quickly resolve software problems leads to negative consequences for our customers and increases internal business costs. A quick deterministic
method to prioritize problems and implement their solution helps to reduce cycle time and costs. Achieving this goal requires several steps. The first is to determine a model that links problem resolution performance to institutional variables and problem characteristics. Statistical Design of Experiments (DOE) is a tool that provides data requirements for estimating the impacts of these variables on problem resolution. Once data has been gathered the results of statistical analysis can be input into a mathematical optimization model to guide the organization.
This paper describes such an analysis.
|
Don Porter, Motorola
|
|
|
Predictive Metrics to Estimate Post Project Costs How much will it cost to support your software project based on current estimations? Discover the answer to this question by using statistical estimation methods-including the S-curve and the Rayleigh curve-to help you determine where your projects are in relation to required quality and trendings to meet your post-project cost goals. Learn how to use metrics to predict post-project costs and make better release decisions based on these predictions.
|
Geoffrey Facer, Intel Corporation
|
