Code coverage metrics help you to mitigate risk
How can you measure your testing quality while testing? Usually you get the feedback, only later from the production whether you have done your job right. And afterwards to solve production bugs results in higher costs. During testing several questions can pop up. Do you get all the information you need in order to do your job well? Do developers have the same understanding of the task as you do? Refactoring the code might not be a crucial issue for the developer, so what happens if this information does not reach you, and you do not test deeper in that area? It is all risk you have to mitigate, but how?
With this session I would like to show you a method, how you can predict the testing quality on the fly.
30-minute New Voice Talk