Always Write Unit Tests

Unit tests are my passion. I always write them and I also encourage others to write them and even have taught developers to write unit tests. But I am quite surprised how often developers don't write unit tests. There is a lot of benefits for writing unit tests. In this blog post, I will explain three main reasons why every developer should always write unit tests.

Automatic Rollback to Integration Tests in C#

This is something that has made my integration tests better. You define a test method to run in transaction and rollback at the end of each test. This makes it possible to write integration tests that write to the database. And tests won't leave any "garbage" there because rollback at the end of the test undoes all database updates (and inserts and deletes). If this is possible in your language and testing framework I strongly recommend it. In this blog post I will explain how you can do it with NUnit in C#.

The Clean Coder by Robert C. Martin

I wrote a book review of The Clean Coder by Robert C. Martin ("Uncle Bob"). It tells what makes programmer a professional programmer and gives practical advice. Professional programmer takes responsibility for his/her work and improves himself/herself constantly. Someone who cares about his/her career as a programmer. The book is relatively short (210 pages) and easy to read. I recommend it to all software developers. My rating: 4/5.