The current documentation specifies the coverage_exceptions parameter as "List of package names to exclude from coverage analyzation.".
Given a package structure of:
HarnOS
|- UI
| -| -Modals
| - WebServices
Providing a coverage_exception of either 'HarnOS.UI' or 'UI' (I just supplied a list with both) I would expect the coverage to ignore the entire UI Package.
It looks like the code is actually using a name of module_exceptions with this property instead of package. It doesn't look like the function has access to any package names so it might need to be elsewhere, but it would be really helpful to be able to ignore a whole package and not receive failures for not covering the code.
The current documentation specifies the coverage_exceptions parameter as "List of package names to exclude from coverage analyzation.".
Given a package structure of:
HarnOS
|- UI
| -| -Modals
| - WebServices
Providing a coverage_exception of either 'HarnOS.UI' or 'UI' (I just supplied a list with both) I would expect the coverage to ignore the entire UI Package.
It looks like the code is actually using a name of module_exceptions with this property instead of package. It doesn't look like the function has access to any package names so it might need to be elsewhere, but it would be really helpful to be able to ignore a whole package and not receive failures for not covering the code.