Showing posts from February, 2017

Keep a code coverage on a radar

Last time we discussed significance of unit tests. They must be clean, fast and also comprehensive. First two points developer can control manually. But what about the last? Value of tests is directly proportional to the code coverage. Of course the level of code coverage is not a main purpose, but it is a good sign of their usefulness. How can we control and maintain this rate on sufficient level? Cobertura maven plugin will help us.

Separate and rule your tests

Everyone who cares about quality of his code must write tests. Would be better to write tests before code (I mean TDD), but presence at least some kind of tests are already well. Tests are the best way to prove that your code works as well as you expect. Also your tests are the best documentation not only how to use your code, but also how you understand a task.