How to Assess Automation Coverage

How can we document what an automated test does and covers without adding a lot of overhead?

How do we know what is not covered by automation?

All coverage assessments involve comparing some sort of model, to some sort of implementation.

We often have to work in small chunks when doing this because it is hard to hold an entire model of the system in our heads.

Document what the automated execution does using Class names, Method names and package structure. Try to make it self documenting.

Use the package structure to help support reviewing for gaps and basic coverage.

Coverage is a 'mapping' process. We have to have some model of 'cover this' and then a way of mapping the test to the 'covered'.

In this video I show code in the IDE to demonstrate how the code itself can help you review coverage.

I created a supporting blog post here



---

Remember to subscribe to this YouTube channel.

You can support me on Patreon (watch my videos ad free and receive extra content)

I blog at

Learn more about my consultancy, books and online training at:

-
-

Follow me on:

-
-
-

eviltester,software testing,test automation,code review java,test automation coverage,test coverage,test coverage review,