Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. License Issue

    For anyone interested, a fix for this problem has been introduced with the newly released version of NCrunch (v1.45).

  2. Can't uninstall NCrunch if you've already uninstalled Visual Studio 2010

    For anyone interested, a fix for this problem has been introduced with the newly released version of NCrunch (v1.45).

  3. NCrunch seems to get confused sometimes during frequent typing

    This makes sense. Synchronisation problems are most likely to happen in response to a large number of changes to files (for example, a source control checkout, or a big refactoring operation). You might want to try the new version of NCrunch just released (1.45). I'm keen to hear if this version …

  4. Cancel test runs

    Hey Ben, Great to hear from you! There's some work in progress here. The idea is to extend the 'Stop' button so that after it's clicked, it immediately turns into a 'Kill' button that can be clicked again to cancel the execution of all tests. The context menu option to kill a test process …

  5. MSpec with Behaviors does not 'Go to selected Test'

    Hi, thanks for posting! Although this behaviour is not ideal at all, it is, quite sadly, the best approach available given the design of NCrunch. NCrunch's analysis and test discovery is all entirely post-build, which means that its ability to navigate to tests is constrained by the debugging …

  6. Why Slow Report

    Hi, Thanks for the suggestions! A 'hot spot' view is definitely a nice to have. I've been thinking about ways this could perhaps be included in the metrics view. Something that I think will help with finding slow tests and projects would be to introduce different grouping options in the Test…

  7. Inscrutable build error

    Hi, thanks for posting! I've introduced a fix for this issue in the 1.45 release, due out within a few days. In the content of the Nuget solution, I recommend removing the default IntPtr from the NativeMethods.CredUIPromptForCredentials method inside the PowershellHost project as a temporary w…

  8. System.UnauthorizedAccessException

    Great to hear that the big issues are solved. It is unfortunate that environments do still exist where NCrunch needs special attention (i.e. extensive configuration and messing around with tests). Usually these tend to be solutions that involve a lot of extensive integration testing and cross-plat…

  9. System.UnauthorizedAccessException

    Hi Rodney - We're establishing a few parallel lines of communication now, so I'll try to break up the areas of discussion and we'll work through them separately :) Regarding the locking of the mixed mode resource assembly: I get the impression that you've managed to find workarounds for t…

  10. NCrunch 1.44 license details

    Hi Mohana, Thanks for posting! License details usually aren't discussed in the technical support forum, if you'd like to ask a question about licensing, please do so via the [url=http://www.ncrunch.net/Support/Contact]contact us[/url] form. Cheers, Remco

  11. Tests are not executed

    Thanks for sending through the report. I've inspected the log file and found evidence of an intermittent code coverage mapping issue that is surfacing on your solution. A fix for this issue is being included in the 1.45 release that I hope to have ready next week. Hopefully the new release should…

  12. System.UnauthorizedAccessException

    [quote=Rodney;3865] 1. I have troubleshooted this to your process holding the locks because it never really exits and the tests are testing an API that holds on to resources by design until the application that called it finishes. This is because the cost of using these resources is high initially,…

  13. Tests are not executed

    Hi, thanks for posting! I'm wondering if you wouldn't mind me bombarding you with a few questions to narrow down the scope of this issue. - Which engine mode are you using? Is it the 'Run impacted tests' mode? - How often does this issue occur? I.e. how many times per day of use? - Have you…

  14. System.UnauthorizedAccessException

    Hi Rodney, As you've described that the files being locked are resources being used by your application, this means that the locks are being opened and held by your code. NCrunch does not control or manipulate the execution of your code, so if your tests hold the locks after they finish executio…

  15. Coverage markers going missing partway through methods

    Hi Andy - The only issues that I currently know of that can produce this kind of effect show themselves only infrequently, so I suspect this may be something new .. Straight after you've noticed it happening, would you mind submitting a bug report? I'd really like to take a look at the log fi…

  16. System.UnauthorizedAccessException

    Hi Rodney, NCrunch will spawn as many test and build runners as necessary to meet its parallel execution needs. This is controlled by the [url=http://www.ncrunch.net/documentation/reference_global-configuration_max-number-of-processing-threads]Max number of processing threads[/url] configuration…

  17. Coverage markers going missing partway through methods

    Hi, thanks for posting! This looks like a mapping/sync issue between the coverage information and the source file. A known bug exists in 1.44 (and prior) which can cause an issue like this. A fix is pending in the upcoming 1.45 release. Does a reset (disable/enable) of the engine fix up th…

  18. Coverage information for Automatic Properties

    Hi Bob, Thanks for posting! Auto-properties do not have debugging information generated for them by the compiler (i.e., you'll notice that you can't set breakpoints on them). Because of this, it's impossible for NCrunch to instrument them to retrieve code coverage information. NCrunch will…

  19. Xunit tests won't runwhen you have them in a nested class

    Hi, thanks for posting! This issue is caused by a limitation in the Gallio adapter NCrunch is using to discover Xunit tests. Basically, the adapter doesn't search nested Xunit classes for tests when using Static Analysis. A workaround is to set the '[url=http://www.ncrunch.net/documentation/ref…

  20. Code coverage indicators not appearing

    Hi Jon, Thanks for posting! Generally this problem stems from a bug in Visual Studio that corrupts the adornment layer used by NCrunch to display coverage markers. The bug can be triggered by VS package install/reinstall/uninstall actions, NCrunch upgrades, etc. Forcing Visual Studio to prope…