Over the past, oh, year and a half or so, I’ve followed the rapid ascension of Ruby on Rails to the top of the web development heap. In the process I read a lot of blog entries, a lot of “Hello World!” introductory articles and a lot of best practice documents. A big part of the thinking behind Rails is Test Driven Development (TDD) – the idea that you should write automated tests before writing code to make sure that a) you know what the code is supposed to do before you write it and b) once the code is working there is a quick, easy way to make sure it keeps working as you further develop your application.
Read more