Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
Add the # of tests that were run by test project and in metrics
Options
Previous Topic Next Topic
jeffras
#1 Posted : Thursday, January 17, 2013 8:24:55 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 7/26/2012(UTC)
Posts: 5

Thanks: 1 times
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
Back to top
Remco
#2 Posted : Friday, January 18, 2013 11:20:16 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,000

Thanks: 932 times
Was thanked: 1259 time(s) in 1172 post(s)
Hi Jeff,

Thanks for the suggestion! Are you thinking in terms of the NCrunch Metrics view? i.e. another column perhaps?


Cheers,

Remco
Back to top
jeffras
#3 Posted : Tuesday, January 22, 2013 7:55:13 PM(UTC)
Rank: Newbie

Groups: Registered
Joined: 7/26/2012(UTC)
Posts: 5

Thanks: 1 times
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
Back to top
 |  Edit by user
Remco
#4 Posted : Tuesday, January 22, 2013 8:20:19 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,000

Thanks: 932 times
Was thanked: 1259 time(s) in 1172 post(s)
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
Back to top
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.028 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download