Jeremy Durham

Good points. Looking through our code, we have a 1 to 1.2 code to test ratio. That's not including cucumber stories, so the majority of the typing we do is writing tests. We'd really love to bring in a Rails developer that can teach us a thing or two about how they write tests, but the problem is that we can't find many Rails developers who are even writing tests, let alone well. I guess I just expected the percentage of Rails developers writing tests to be higher; just wondering if people see the same sort of percentages when they interview Rails developers. You're right about writing tests not being hard. All of our developers didn't actively written tests when they started, but they're all very good at it now and seem to really enjoy it. We're always happy to hire developers who are new to Rails, testing, and such as help them along, but we'd also love to hire someone who has some different opinions on it so we can improve our process.

Writing tests is important, but not always necessary. Why does it matter if they have always been heavy test writers? Because of the skill or knowledge in writing tests? Some developers haven't written tests because previous teams didn't do it, or the framework didn't really support unit testing, or what have you. Correct me if I'm wrong, but unit testing isn't the hardest thing for a developer to pick up, and if you really want to keep your code base maintainable though tests, then just making sure the developer is on board with unit testing most of the time and willing to learn, isn't that good enough?