Pragmatic Testing

Tests exist so we can change the product and still ship it. A test that fails on every refactor and never catches a real bug makes change harder.

Most of these ideas come from Orta Therox's Pragmatic Testing. Aim for enough, not perfect. Don't test every if. Paint with a wide brush first and keep the fine brush for the edges. The examples are Swift, but the rules apply in any language.

Earn-its-place check

Answer these before you write a test. If you can't answer them, don't write it.