A Manager?s Guide to Evaluating Test Suites

🔖

By Brian Marick,James Bach,Cem Kaner Whatever else testers do, they run tests. They execute programs and judge whether the results produced are correct or not. Collections of tests ? test suites ? are expensive to create. It?s fair to ask how good any giv

http://www.testing.com/writings/evaluating-test-suites-paper.pdf

✍: FYIcenter.com

2006-04-01, 8920🔥, 0💬

Measurement of the Extent of Testing
by Cem Kaner Much of the material in this paper was presented or developed by the participants of the Software Test Managers Roundtable (STMR) and the Los Altos Workshop on Software Testing (LAWST). 2006-04-01, ≈10🔥, 0💬

Painless Bug Tracking
By Joel Spolsky Includes ten top tips for bug tracking 2006-04-01, ∼9146🔥, 0💬

EXPERIENCE WITH THE COST OF DIFFERENT COVERAGE GOALS FOR TESTING
By Brian Marick In coverage-based testing, coverage conditions are generated from the program text. 2006-04-01, ∼9083🔥, 0💬

Code Coverage Analysis (test coverage analysis)
By Steve Cornett This paper gives a complete description of code coverage analysis (test coverage analysis), a software testing technique. 2006-04-01, ∼9053🔥, 0💬

How to Misuse Code Coverage
By Brian Marick Code coverage tools measure how thoroughly tests exercise programs. I believe they are misused more often than they're used well. This paper describes common misuses in detail, then argues for a particular cautious approach to the use of c 2006-04-01, ∼9046🔥, 0💬

The Rational Edge
The e-zine for the Rational community 2006-04-01, ∼9046🔥, 0💬

A Manager?s Guide to Evaluating Test Suites
By Brian Marick,James Bach,Cem Kaner Whatever else testers do, they run tests. They execute programs and judge whether the results produced are correct or not. Collections of tests ? test suites ? are expensive to create. It?s fair to ask how good any giv 2006-04-01, ∼8921🔥, 0💬

PROCESS IMPROVEMENT: Case Study of an Improvement Program Featur
by: Robert MacFarland, Ericsson Ltd. This article tells the story of Ericsson, which has unfolded over a period of five years. It describes an initiative that has continually striven to get the reviews and inspections (R&I) processes and procedures it has 2006-04-01, ∼8912🔥, 0💬

Fighting Memory Leakage
Memory leakage is probably one of the most difficult programming problems to solve, because you cannot easily search thousands of lines of code for a complex logical error that might cause a problem when some unlikely event occurs. 2006-04-01, ∼8894🔥, 0💬

All rights in the contents of this web site are reserved by the individual author. FYIcenter.com does not guarantee the truthfulness, accuracy, or reliability of any contents.