Hello,
I'm in a project where we want to collect code coverage for different systems. A problem we have is that coverage from test code are added to the total code coverage, this is bad because the test code have like 99 % code coverage. In a Project with 28 000 lines of test code with a total of 62 000 lines this will give a coverage result that is worthless. We have not found any way to exclude Projects from the analyze, is it possible?
Our situation is that we have many different systems (40+ or so) with different setups. A system can have one or many solutions, and each solution can contain one or more projects and test projects.
Today we build the code in TFS both 2015 and some older version. On the build servers we got NCrunch console tool to export the test results to a folder where we parse them and add the result to our database.
Thankful for any suggestions!
Setup Problems
How to choose what projects and solutions not to test
Started by kontinuerligkodanalys on 6,427 views
Remco NCrunch Developer
#7925
04 Nov 2015 21:58 UTC
Hi, thanks for posting!
I'm sorry in that I'm having a hard time understanding exactly what you're asking. Are you saying that you want to try and use NCrunch across multiple solutions at the same time? Or that you want to consolidate coverage reports together for multiple solutions?
In the NCrunch Metrics Window, there is a toolbar option that will allow you to exclude specific projects from the metrics aggregation. Is this what you're after? The NCrunch console tool will consider this setting when it writes its coverage report.
I'm sorry in that I'm having a hard time understanding exactly what you're asking. Are you saying that you want to try and use NCrunch across multiple solutions at the same time? Or that you want to consolidate coverage reports together for multiple solutions?
In the NCrunch Metrics Window, there is a toolbar option that will allow you to exclude specific projects from the metrics aggregation. Is this what you're after? The NCrunch console tool will consider this setting when it writes its coverage report.
The second row will probably solve the problem, will try it. Thank you very much. :)
Post a reply
Log in to reply.