I'm just wondering.
Should we provide way to include/exclude files (paths) with mask?
That seems more consistent when looking at the project from filesystem perspective rather than from database perspective.
It would also be aligned with sonar include/exclude approach.

Any opinions?

I'm not using code coverage yet so I don't have experience on the matter, but I see this change as low-hanging fruit I'd like to include as similar to the db framework as possible.
At the moment I'm not sure how much benefit doing the additional effort of pattern-based include/exclude will bring.

@justedro: I'd like to add a system test for the code-coverage use case before merging. We don't have one yet and for include/exclude functionality only affects these use-cases I'd want to add it right now.
Don't know how long it will take - Christmas Holiday is family time so I don't have much leisure time ;)
You are of course very welcome to provide one yourself if you want to contribute even more - though thanks for the work you've already done.