Software testing is very valuable when done right, but can be a huge time sink when done wrong. The main error that causes this issue is to approach t

Catching the Biggest Fish

submited by
Style Pass
2022-05-15 03:00:06

Software testing is very valuable when done right, but can be a huge time sink when done wrong. The main error that causes this issue is to approach testing as being “one size fits all”. You might have some specific experience of testing for a past project, and apply it again to a subsequent project, without thinking about whether it makes sense. 

Under this falls any general policy (for example, “100% code coverage unit testing” or “test-driven development”) that doesn’t consider the specific type of test or project involved. And even within a project, some parts might require more or less thorough testing than others. A better approach is to match each type of software with the appropriate type and quantity of tests. In this article I’ll go over the three common types of tests, and how they can be applied to three common types of software.

Unit tests are the most common type of test, and some people will assume that’s what you mean if you just use the word “test” unqualified. Similarly, some people will say that unit tests should be the bulk of your tests, although I don’t think that is universally true either.

Leave a Comment