You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
While #pragma works fine, it's not really convenient for excluding unit test code from the code coverage process. You basically end up writing that in every piece of code...
What we need is a simple way to exclude complete namespaces from the coverage tool. That way, our coverage results don't get messed up with all test code that isn't hit when everything works correctly...
This is absolutely non-trivial, because the application doesn't have knowledge of the coverage tool.
One way to do this is to create a special stub 'PassToCoverageTool' call, and intercept that using a breakpoint, thereby passing information to the coverage tooling. The implementation in the application should be a stub that's never inlined. Once that's implemented, we have a way of passing data to the coverage engine, which will help significantly with this issue.
It's tricky, it might just do the job...
The text was updated successfully, but these errors were encountered:
While #pragma works fine, it's not really convenient for excluding unit test code from the code coverage process. You basically end up writing that in every piece of code...
What we need is a simple way to exclude complete namespaces from the coverage tool. That way, our coverage results don't get messed up with all test code that isn't hit when everything works correctly...
This is absolutely non-trivial, because the application doesn't have knowledge of the coverage tool.
One way to do this is to create a special stub 'PassToCoverageTool' call, and intercept that using a breakpoint, thereby passing information to the coverage tooling. The implementation in the application should be a stub that's never inlined. Once that's implemented, we have a way of passing data to the coverage engine, which will help significantly with this issue.
It's tricky, it might just do the job...
The text was updated successfully, but these errors were encountered: