Classic Testing Mistakes

🔖

By Brian Marick It's easy to make mistakes when testing software or planning a testing effort. Some mistakes are made so often, so repeatedly, by so many different people, that they deserve the label Classic Mistake.

http://www.testing.com/writings/classic/mistakes.html

✍: FYIcenter.com

2006-04-01, 10🔥, 0💬

16 CRITICAL SOFTWARE PRACTICES
This paper outlines the 16 Critical Software PracticesTM that serve as the basis for implementing effective performance-based management of software-intensive projects. They are intended to be used by programs desiring to implement effective high-leverage 2006-04-01, ∼9612🔥, 0💬

A Buyer's Guide to Code Coverage Terminology
By Brian Marick There are many kinds of code coverage. Some of the types have more than one common name, plus several uncommon ones. Discussions of coverage can get hung up on name debates, with endless claims about what the right name is and what, precis 2006-04-01, ∼9252🔥, 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, ∼8948🔥, 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, ∼8929🔥, 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, ∼8916🔥, 0💬

New Models for Test Development
By Brian Marick A software testing model summarizes how you should think about test development. It tells you how to plan the testing effort, what purpose tests serve, when they?re created, and what sources of information you use to create them. A good mo 2006-04-01, ∼8876🔥, 0💬

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

Evolution of Test and Code Via Test-First Design
By Jeff Langr Abstract Test-first design is one of the mandatory practices of Extreme Programming (XP). It requires that programmers do not write any production code until they have first written a unit test. By definition, this technique results in code 2006-04-01, ∼8770🔥, 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, ∼8738🔥, 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.