I’m a fan of test-driven development and absolutely believe that tests should be included in the scope of all software development projects.
Some frameworks are geared more towards test-driven development than others – if you’re in the Rails world, then you’re used to having testing support; however, if you’re in Java or .NET, then you’ve likely had to integrate JUnit or NUnit into your workflow.
Andrzej Krzywda – a polish developer – has a slick guide on 15 test-drive-development-based steps to Rails application development. Though the article is platform specific, the general rules of TDD apply:
- Write your tests first (before implementing your classes)
- Verify the test fails
- Write code that populate the class and pass the test
- Verify the test passes
- Rinse and repeat
Regardless of your platform of choice, TDD helps to greatly improve the integrity of your application.
Speak your mind...