Question

Since NCrunch has left the free market, I was looking for a similar tool for code coverage marking, and continous testing like NCrunch

edit: I'm using VS2012

update:

I've been using ContinuousTest for a while now, it's OK, but I think it lacks feedback when I write code. The feedback is good when I write tests, but when I break a test (while editing source code) it won't tell me that the test broke (in the margin, like it does for NCrunch). So if anyone knows other tools, I'm still listening.

Was it helpful?

Solution

From what I've read, most people are in the same boat and are moving to ContinuousTests. I do not think there is a perfect replacement... yet.

Here is a decent comparison between NCrunch and ContinuousTests

Update

Upon recent usage of ContinuousTests with VS2012 I have decided to uninstall. There was too much friction to get it running. I believe it needs an update to support VS2012 properly.

OTHER TIPS

NCrunch is a fantastic tool that I discovered while it was still in beta, as a developer I try to do my best to support people that are doing cool projects. If people were using NCrunch and liked it, I'd encourage you to purchase a license.

Stuff like that takes a lot of time to develop and less people will be creating the cool tools you love if people aren't willing to support it.

NCrunch is worth every penny. $159 is really not that bad considering the effort put in by Remco to integrate it seamlessly into VS; which is really not easy. That when combined with the metrics it provides make it a simple decision in my opinion.

Have a look at Giles for continous testing.

It currently supports NUnit, xUnit.net, Machine.Specifications and NSpec, but the roadmap shows that support for all major testing frameworks is planned.

A tool similar to NCrunch would be ContinuousTests but I don't think they do code coverage in the classical sense.

Open Source code coverage tools for .NET such as PartCover and OpenCover also exist.

NCrunch is an absolutely good product, a bit expensive though. The suggested alternative (ContinuousTest) does not work very well, as it doesn't have line by line coverage, total code coverage metrics and it complains about properly referenced NuGet packages in large solutions (works perfectly fine with NCrunch).

NCrunch also has a seamless integration with Visual Studio which makes coding even faster and more fun, and you know when you met all criteria specified in unit tests while you are coding, without the need to press any button.

I was an avid NCrunch user. Now that they have went commercial I am using ContinuousTests and TestDriven.net which contains NCover for code coverage.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top