Experience with JetBrains' dotCover?

Anthony Stevens

unread,

May 7, 2012, 5:46:31 PM5/7/12

to dotnetstartup

Anybody have any direct experience using the code coverage tool from JetBrains, dotCover? I'm evaluating whether or not it's worth a close look relative to NCover. It's cheaper, and we use ReSharper, so it seems like it might be a good fit.

Thanks,

a

Scott Porad

unread,

May 8, 2012, 3:02:08 AM5/8/12

to dotnet...@googlegroups.com

We use it a lot, and I'm a HUGE fan.

Why am I a fan? Because it shortens the feedback loop on test coverage. With NCover, you gotta commit your code, then have CI do a build and run the coverage, then you get your results. With dotCover, you run your tests and get your coverage before you commit your code.

Also, it does covered/uncovered highlighting right in Visual Studio, so you can easily see what code is un/covered.

We also use dotCover as our code coverage tool as part of CI...it has a command line interface.

--
Scott Porad
sc...@cheezburger.com

Give me anonymous feedback

All your funny in one place at http://cheezburger.com

Tom Lianza

unread,

May 8, 2012, 1:56:43 PM5/8/12

to dotnet...@googlegroups.com

Wondering also if anyone's had any luck with nCrunch, which is nice in that it's free: http://www.ncrunch.net/

But, every time I've tried to use it, it hasn't worked. The tests never complete, or some complete and some hang, and I can never get a good stack trace out of it, etc. I was hoping this was my answer to the .NET equivalent of Rails' autotest... but sounds like dotCover is the better bet.

Tom

On Mon, May 7, 2012 at 2:46 PM, Anthony Stevens <anth...@crowdify.com> wrote:

Reply all

Reply to author

Forward