ncrunch from commandline

Is it possible to run ncrunch from the command line?

I would like to use it as part of a msbuild script.

What test framework are you using? I always just use the framework's (normally nUnit, I'm just so dull and old fashioned) test runner during automated builds.

To me, nCrunch is all about the integration with VS, and the automatic build/run process, none of which seems relevant during an automated build. What aspect of nCrunch were you wanting to use during the build?

At the moment, it isn't possible to run NCrunch from the command line. I do, however, understand the motive behind this. As there are differences between NCrunch's test environment and that of a standard test runner, it is desirable to be able to ensure code is NCrunch-compliant as part of a continuous integration process. This could be useful for teams where not all members are making use of NCrunch.

Unfortunately, NCrunch itself is designed to be fully continuous. The architecture of a continuous test runner vs a serial test runner is very, very different. Attempts have been made to produce a console variant but so far none of these have resulted in anything reliable enough to be used for a continuous integration process or build server. There is still the possibility of this area being explored more in future.

Remco wrote:At the moment, it isn't possible to run NCrunch from the command line. I do, however, understand the motive behind this. As there are differences between NCrunch's test environment and that of a standard test runner, it is desirable to be able to ensure code is NCrunch-compliant as part of a continuous integration process. This could be useful for teams where not all members are making use of NCrunch.

Unfortunately, NCrunch itself is designed to be fully continuous. The architecture of a continuous test runner vs a serial test runner is very, very different. Attempts have been made to produce a console variant but so far none of these have resulted in anything reliable enough to be used for a continuous integration process or build server. There is still the possibility of this area being explored more in future.

If you have a test runner that can execute tests across multiple nodes (V2) then it could be very helpful outside NCrunch itself - for example it would be possible to speed up tests running in TeamCity.

Andrey wrote:If you have a test runner that can execute tests across multiple nodes (V2) then it could be very helpful outside NCrunch itself - for example it would be possible to speed up tests running in TeamCity.

Yes - definitely. The distributed and parallel execution features could massively decrease build times on a continuous integration server. The value of this is without question.

Remco wrote:Yes - definitely. The distributed and parallel execution features could massively decrease build times on a continuous integration server. The value of this is without question.

Any plans for making it a detachable feature?

Nothing I can commit to at the moment, but it will probably happen in future.

If we could use NCrunch to speed up builds as well as continuous testing, I think that would be all I required to persuade my company to set up an NCrunch cluster for running the tests.

Hi, thanks for posting. I recommend voting for this feature at https://ncrunch.uservoice.com.

I would like to retrive code coverage from ncrunch using command line, is it possible?

Not at the moment. There is a feature request for this that you're welcome to vote for though - http://ncrunch.uservoice.com/forums/245203-feature-requests/suggestions/5749303-standalone-executable-version-for-builds-etc.