In Rails, you have no excuse not to write tests! The model and controller generators create the tests - you just need to keep them up to date. In Java land, a little more is involved in writing JUnit tests. I’ve been trying to get into the practice of writing the tests before I actually write the code. I must admit that I have found this hard. I prefer to code first and then write the tests (if time permits). This is against TDD but I enjoy writing the actual code and not the tests. I recently discovered ModelJUnit. The process is simple - create a Finite State Machine to model the code/functionality and then let ModelJUnit generate test cases and coverage metrics. The concept has a lot of merit. I’ll be using ModelJUnit in some small projects - I’ll be sure to post my experiences.