As a good tester, surely more than once you have considered looking at the coverage of your tests on the scope of a project. This indicator allows you to know, through the execution of a test suite, which lines of code have been executed and which have not, allowing programmers to see if there are parts of the code that are not being tested. Many times the detail ends up summarized in a percentage of code that is being executed, which is the measure that is most often taken into account when talking about this concept.
Many of the programmers I know establish as a goal to reach 100% coverage of their projects, in the aims of achieving a code robust in terms of quality. They tend to believe that covering the whole code will make sure you do not leave anything to check, and thus satisfy all testing needs.
But, is that statement true? 100% coverage makes me sure that my code will be wonderful? Can I say that my code is well tested if I have a good coverage?
Surfing on the (execution) flow 