Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Large number of threads

    Hi! Thanks for sharing this issue. It is not normal for this process to guzzle threads, although this is the same process that is used to execute your test code, so if you have a test (or series of tests) that create suspended threads, then this is certainly possible. Try connecting to the proce…

  2. Silverlight 5 and VS2013 RC

    Thanks for submitting the report. I've managed to reproduce this issue. The root of the problem is an toolset incompatibility between v12 and v4 of MSBuild (v12 was newly introduced in VS2013). MSBuild works around this issue through binding redirections that force the Silverlight build tasks t…

  3. Specific red/green markers when a test is selected

    Hi, thanks for this suggestion! The focus right now is on moving towards greatly increasing the visibility and accessibility of the 'Advanced->Show coverage for selected test only', as it seems this is very frequently used. There is also the likelihood that future features will be attached to it…

  4. Silverlight 5 and VS2013 RC

    Hi, Thanks for sharing this issue. The problem you've described is an error NCrunch gives when the behaviour of the underlying build process is not as expected. NCrunch is then unable to identify the location of the assembly output from the build. Is there any chance you could submit a bug…

  5. Add expected test duration as engine mode criteria

    There will certainly be situations where such a filter would give inconsistent results. Another case could be tests where the engine is not yet aware of their normal execution time (i.e. they've never been run before). I'd expect whoever uses this to be very broad in how they apply it. For exam…

  6. Add expected test duration as engine mode criteria

    Hi Kaleb - Thanks for the suggestion! This feature is currently pending in the upcoming V2 release. Cheers, Remco

  7. Static initialization code isn't considered covered

    This would be happening because the static members are being initialised during the test discovery step, which happens before any tests begin executing. You're correct in your understanding that NCrunch will re-use the dynamic analysis processes for test execution. If you set the 'Framework utilis…

  8. "Pin" items in metrics window.

    Thanks for the suggestion! It doesn't look like features in this area will be in V2.. The scope of V2 is already very big in different areas, and with many compatibility and integration upgrades. We'll see how things go in future releases.

  9. Getting NCrunch to load NUnit Addins

    For anyone interested in getting AutoFixture.NUnit2 working with NCrunch, Gert Jansen (gertjvr) has [url=http://gertjvr.wordpress.com/2013/10/02/howto-get-autofixture-nunit2-working-with-ncrunch/]published a way to do this[/url] by inheriting the addin into the test project. Thanks Gert!

  10. Negative priorities in processing queue?

    This is absolutely by design. Priorities can fall well into the negatives for long running tests that haven't been impacted or marked for execution by user. This is done by the engine to prevent long running tests from chewing up resources when more important work can be done.

  11. Ignore tests using attributes

    Yes, this is the intended behaviour. A test ignored by the engine mode is still considered to be a test that could be run under different circumstances (i.e. manually). It may well be that if you want the tests to be gone and never looked at by NCrunch, using the [url=http://www.ncrunch.net/docume…

  12. Set Parallel Execution option at test project level

    Hi Mark - The solution-level parallel execution option is basically just a shortcut for using attributes at fixture or project level. If you have a project containing tests that can't be run in parallel with each other (i.e. an integration test project), the easiest option is to place an [url=…

  13. Feature request - triggering SpecFlow test runs

    Hi Dan, Great to hear from you! There's been several requests for the ability to specify a wildcard for project files that don't trigger NCrunch's build and test logic. I don't see why this same feature couldn't be used for .feature files. Delivery date is uncertain but I'll see what I can d…

  14. NCrunch doesn't run xUnit.net 1.9.2 tests

    This makes really good sense now. So Nuget is adding the binding redirections in order to ensure that you're using the right version of xUnit when you run tests. NCrunch adds its own binding redirection to the .config file too, so the CLR must be randomly choosing which redirection to use at run t…

  15. NCrunch doesn't run xUnit.net 1.9.2 tests

    Hi, thanks for sharing this issue, and for taking the time to put together so much information about it. As you've perhaps speculated by looking through the plugin config files, NCrunch's integration with xUnit (via Gallio) works by using assembly binding redirections. This means that if NCrunch…

  16. nCrunch exit code

    Great to hear you isolated the issue. NCrunch V2 is expected to bring improved handling of stack overflows. It's a tricky area, as a stack overflow generally causes the CLR to completely annihilate the process with no chance of recovery.

  17. NCrunch and Typemock

    Great! Thanks for sharing this information, I'm sure that others will find it useful. There are no known compatibility issues between NCrunch and PostSharp - although you may need to turn on the 'Copy referenced assemblies to workspace' setting for projects that make use of it.

  18. nCrunch exit code

    Hi Rattle - NCrunch tries to handle every exception it can, with the intention of reporting more detailed information as part of the test result. Because of this, any exit codes returned from the testhost process are indicative of a system error that NCrunch isn't able to handle or accurately re…

  19. 1.47 is missing nCrunch.TestHost.x64.exe

    Hi Olaf - Because of a packaging and deployment issue, the x64 task runner was left out of the 1.47.0.12 package. I've updated the download page with a new revision of 1.47 - 1.47.0.18, which has the x64 task runner included. I'm very sorry for the trouble. If you download and install the …

  20. Getting NCrunch to load NUnit Addins

    In theory, NUnit should try to load from C:\Program Files (x86)\Microsoft Visual Studio 11.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2012\bin\addins - although admittedly I have never personally seen this work ... it may be worth a try. The only situation I have observed N…