Why you should never skip writing tests

When I first read the headline, I thought the poster meant "taking a writing test" like taking an exam.<p>Thanks for sharing. We do test first on one of the projects I've recently joined. The project uses JUnit for unit tests and integration tests, Maven for automated builds, JIRA for tracking, and Subversion. The project manager keeps things simple, no heavy process. Also, We're a geographically distributed team.

I never take a break, even an overnight break, at an "appropriate breaking point". That way, it's easy to pick up where I left off. A nice byproduct is that I rarely rush to get something done while tired.