How to write a better unit tests

Few rules that I follow to write the best possible unit test..

Think more Code Less:

Always think the the unit you are trying to test. And think more. Code less. Code only the smallest of functionality that you are trying to test. So that you do not build a very complex unit test. Unit tests are supposed to be simple and comprehensive. Think Clean and accurate and more robust test scenarios

More the better:

Always try to cover up as much scenarios, the better. Remember a useless test would not affect anything but a missed test scenario could land you in trouble.

Abstraction over Concretion:

Always interfaces over concrete classes.

Now, considering you want to mock objects with any mock providers..

Follow Rules & Patterns

If you follow rules and write with patterns, will be easy to add new tests with extension. I follow this pattern mentioned below. Makes thing more readable. Plus I love decorations.

This makes things more easy to identify and easy to change. There can be need to modify tests in future. And we need to make sure those are easy

Its a daily thing

Unit tests are not a shelf sitting tools. Its more of a daily thing. Always add new tests as you code changes and keep em up to date. Developers usually fall short of what and how many unit tests are required. So always be generous with it. Add more tests regularly.

Related posts:

Streamloots is a Valencia-based startup that was born in Silicon Valley that has developed a unique platform for streamers to interact, monetize and have fun with their fans Ambition is the word that…

The education system worked for me. I went to a snobbish franchise school and scored in the 99th percentile despite not sitting in the classroom most of the time. I got accepted to the best of Indian…

The summer before my senior year of high school I took a collegiate creative writing course. One of the neat — and scary — things about that class was that since creativity was involved, it was not…