There are two aspects that you should always take into consideration when planning and implementing your tests. Firstly, 100 percent code coverage won't help you in removing the possibility of having or introducing a bug, which means that exploratory manual testing will always be needed, and it will have to be factored in while writing your initial draft of the master test plan. Secondly, until now, all the tests and reports that we've generated for such a small project can be run manually by whoever changes the code.

When the size of your code starts to grow and you start to support hundreds of classes and multi-faceted frontend functionalities, when your code lives past the first month and more than one developer will need to access it over and over again, all the knowledge related to tests and how they work or what kind of information can be extracted from them will become more and more difficult to maintain. The worst part is that most likely nobody will use...