Testing is an integral part of a software product’s life-cycle. Some people prefer
executing their tests continuously while they develop, others have a separate
testing phase before each release. The goal, however, is always the same:
finding bugs. The more, the better.
Unfortunately, the time available for testing and for writing new tests is limited. At some point, you
have to get on with development, ship your software and be confident it contains
no serious flaws. Often, more tests exist than can be run in the
available time span. This is especially true if your tests are executed manually,
as is the case for many of our customers.
Then the question becomes: which tests do I select to find the
most bugs before the release?