Test-driven development is a general approach to creating software. You may hear about red-green-refactor cycle which is the essence of TDD. If you are not sure if you have to write tests please take look at this article where I explained why you should do it.
Originally, TDD was a part of extreme programming but it’s now a separated programming technique. Knowledge of this technique is a very common requirement of job offers for software developers.
Want to receive useful tips, information about new Ruby gems and articles on a daily basis? Make sure you follow me and say hello!
We can just fit the essence of TDD in three repeatable steps:
- Write a test for non-existing code and let it fail
- Write a code for created test and make it pass
- Refactor code to meet your expectations
and then just repeat with every next class you will be working on.
At the end credits for the author: test-driven development was created by Kent Beck - https://pl.wikipedia.org/wiki/Kent_Beck