As we gather metrics we sometimes want to know the number of tests that contributed to that metric. If you could display the count of tests run for a metric and also the number of tests that exist in an assembly that would be awesome.
Keep up the great work!
Thanks,
Jeff
Feature Suggestions
Add the # of tests that were run by test project and in metrics
Started by jeffras on 7,056 views
Remco NCrunch Developer
#3555
18 Jan 2013 23:20 UTC
Hi Jeff,
Thanks for the suggestion! Are you thinking in terms of the NCrunch Metrics view? i.e. another column perhaps?
Cheers,
Remco
Thanks for the suggestion! Are you thinking in terms of the NCrunch Metrics view? i.e. another column perhaps?
Cheers,
Remco
Yup, that would work. Maybe for unit test assemblies just add a (#) next to the test name with a count of the tests in that assembly.
For example:
Name,Code Coverage %,Compiled Lines,.....,Tests Executed
SomeAssembly,15.00%,27.0,.....,14
SomeAssemblyTests (14),100.00%,......
With this I can quickly determine if I have invalid tests (wrong location, old, not testing the correct code) and how many tests I have that actually touch an assembly. For example, if the "tests executed" column from above had more then the tests assembly that may be a code smell (too coupled, not adhering to Single responsibility, etc)
Thanks,
Jeff
Edit: Formatting didn't work so changed it to csv format
For example:
Name,Code Coverage %,Compiled Lines,.....,Tests Executed
SomeAssembly,15.00%,27.0,.....,14
SomeAssemblyTests (14),100.00%,......
With this I can quickly determine if I have invalid tests (wrong location, old, not testing the correct code) and how many tests I have that actually touch an assembly. For example, if the "tests executed" column from above had more then the tests assembly that may be a code smell (too coupled, not adhering to Single responsibility, etc)
Thanks,
Jeff
Edit: Formatting didn't work so changed it to csv format
Edited 22 Jan 2013 19:57 UTC
Remco NCrunch Developer
#3571
22 Jan 2013 20:20 UTC
So basically we'd be look at a code coverage metric that applies to file/assembly level. I can see value in that. Let me see what I can do :)
Cheers,
Remco
Cheers,
Remco
Post a reply
Log in to reply.