|
|
|
STAREAST 2006 Concurrent Sessions
Go To: Agile Methods | Exploratory Testing | Outsourced Testing | Performance Testing | Security Testing |
Special Topics | Test Automation | Test Management | Test Metrics | Test Techniques
View by Date
| Test Metrics | | | Wednesday, May 17, 2006 11:30 AM |
Five Core Metrics to Guide the Testing Endgame
Robert Galen, RGCG, LLC
By its very nature, the endgame of software projects is a hostile environment. Typical dynamics include release pressure, continuous bug discovery, additional requirements, exhausted development teams, frenzied project managers, and “crunch mode”—a politically correct term for unpaid overtime. Although testing teams are usually in the thick of this battle, they usually do not do enough to help guide the project in this critical stage. To improve the overall endgame experience, testers can help entire team’s focus with a few key defects metrics. Robert Galen discusses ways to track these five key defect metrics: found vs. fixed; high priority defects found; project keywords; defect transition progress; and functional distribution of errors. Join Robert to increase the likelihood of delivering your projects on time—and surviving yet another endgame.
• Help traffic the action for the incoming defect stream during the endgame
• Highlight defect repair performance characteristics without alienating development
• Provide Pareto guidance into project risk areas |
| | | Wednesday, May 17, 2006 1:45 PM |
S-Curves and the Zero Bug Bounce: Plotting the Way to Better Testing
Shaun Bradshaw, Questcon Technologies, A Division of Howard Systems Intl.
The use of objective test metrics is an important step toward improving your ability to effectively manage any test effort. With the two test metrics—the S-Curve and Zero Bug Bounce—you can easily track the progress of the test effort. Learn to graph the S-Curve, showing cumulative test cases planned, attempted, and completed over time. Keep track of the Bug Bounce—the number of open bugs at the end of a period (usually one to several days)—and especially Zero Bug Bounce—the first time development has resolved all the bugs raised by the testers and there are no active outstanding issues. Improve your ability to communicate to the project team test results and test needs and make better decisions about when your application is ready to ship.
• Derive a theoretical and actual S-Curve for test cases using historic and current data
• Use the Zero Bug Bounce for tracking defect correction activities
• Assess the risk of component and application failure prior to release |
| | | Wednesday, May 17, 2006 3:00 PM |
Test Metrics in a CMMI® Level 5 Organization
Shalini Aiyaroo, Motorola Malaysia Sdn. Bhd
As a CMMI® Level 5 company, Motorola Global Software Group is heavily involved in software verification and validation activities. Shalini Aiyaroo, senior software engineer at Motorola, shows how tracking specific testing metrics can serve as key indicators of the health of testing and how these metrics can be used to improve your testing practices. Find out how to track and measure phase screening effectiveness, fault density, and test execution productivity. Shalini describes the use of Software Reliability Engineering (SRE) and fault prediction models to measure test effectiveness and take corrective actions. By performing orthogonal defect classification (ODC) and escaped defect analysis, the group has found ways to improve test coverage.
CMMI® is a registered trademark of Carnegie Mellon University.
• Structured approach to outsource testing
• Framework for setting up a client-focused Testing Center of Excellence
• Measurement of the business value of test outsourcing |
| |
|
|
