Developer Testing refers to testing by the developer, which typically consists of unit tests, component tests, and integration tests. The purpose of Developer Testing is to reduce the gap between when defects are introduced into the code and when defects are found and further removed.

Numerous additional kinds of testing are performed by specialized test personnel and are rarely performed by developers, including beta tests, customer-acceptance tests, performance tests, configuration tests, platform tests, stress tests, usability tests, and so on. Books on these kinds of testing are unexpected in this list.

(adapted from Code Complete, c22)