>each test is one better than none My experience has been the reverse: lots of ultimately pointless tests add nothing to a given codebase but maintenance costs

>each test is one better than none My experience has been the reverse: lots of ultimately pointless tests add nothing to a given codebase but maintenance costs and developer frustration. The most successful projects I've worked on used (completely automated, no code getting pushed to staging unless the CI server says it passes) tests sparingly.