Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Quick second build losing code coverage?

    Sorry - I need to bombard you with a few questions here to fully understand what's happening: - Do the test results themselves (not the coverage) in the Tests Window seem correct? i.e. do the passing tests pass, failing tests fail, etc - Does this seem to be specific to one solution, or to all …

  2. slow typing in VS2015

    Something I thought I would check on this is whether everyone experiencing this issue is encountering it with NCrunch set in manual mode? (i.e. with all testing disabled). Such a thing would point directly to the problem being caused by background builds, which might be related to Roslyn's feature …

  3. slow typing in VS2015

    [quote=crazyoatmeal;8044]Has there been any follow up on this issue from ncrunch? I'm experiencing the same issue even with the latest release which said it fixed some vs 2015 performance issues. None of the suggested changes in this thread have helped.[/quote] Sorry, but there have been no act…

  4. Quick second build losing code coverage?

    Hi, Thanks for sharing this issue. Sorry, but I'm having a little trouble understanding the nature of this problem - are you saying that the build somehow breaks itself, or that you have an intermittent failure? Are your tests losing their pass/fail status in the tests window?

  5. Sharing test case source between tests

    Sorry, the likelihood of a solution being introduced for this in the near future is not high. The way in which the NUnit integration works here with NCrunch means that there is no effective way to solve it without significant risk/effort/consequences required. There is a likelihood that it will …

  6. Grid node high disk latency on c:\users\GridNodeUser\AppData

    Are you certain that this is being caused by nCrunch.BuildHost? I would expect that only the engine process should be interacting with the hash cache. The hash cache does, unfortunately, need to be stored somewhere persistently. This cache is used to allow the node to quickly identify matching …

  7. Coverage issue with lambdas / xUnit?

    Hi, thanks for posting. This line is marked as not covered by NCrunch - because it is physically not being executed at runtime. When SomeException is thrown, the exception bubbles up the call stack and any code after it is inside the scope is not executed. You'll notice that if you put a brea…

  8. Test Window Popup in Win 10/VS2015 with Win8 app

    Sorry, support for Windows Store has now been dropped entirely in NCrunch - [url=http://blog.ncrunch.net/post/Windows-Store-Apps-No-Longer-Supported-By-NCrunch.aspx]http://blog.ncrunch.net/post/Windows-Store-Apps-No-Longer-Supported-By-NCrunch.aspx[/url].

  9. Cannot debug tests with the 2.17 version

    Thanks for sharing this log. I couldn't find anything in the actual test execution itself that described abnormal behaviour. Could you confirm which of the tests in this run were giving you an error after the end of the run? Something worth investigating is this: Process 26592: C:\Users\mart…

  10. Cannot debug tests with the 2.17 version

    Thanks for sharing this. I've done some basic testing with the NUnit features you're using here (async, descriptions, SetUp, TearDown, etc). I haven't been able to recreate any problems, so I think we need to take a deeper look at what may be happening in your environment. My first thought was …

  11. Unattended installation for NCrunch GridNodeServer

    In an ideal world, it should be possible to push updates to the grid node directly from the client. We aren't there yet, but given the way the ecosystem keeps changing and the frequency of NCrunch updates, such a feature might become very popular.

  12. Unattended installation for NCrunch GridNodeServer

    When automating the updates of the grid node service, I'd suggest performing an initial manual install, then simply performing an xcopy over the top of the installed files when you need to update. Suppressing the wizard for upgrades would be simple to do, but I'm concerned about the impact this m…

  13. Incompatible versions of NCrunch (grid nodes)

    [quote=GreenMoose;8026] I more often than seldom seem to need to upgrade ncrunch grid nodes to the same version I use for vstudio2015. Wasn't the idea to minimize this so the grid nodes can continue working with their old version towards a newer vstudio NCrunch version? [/quote] Yes, sorry. Th…

  14. Cannot debug tests with the 2.17 version

    Sorry, is a sample project an option? There must be some feature of NUnit that you're using in your production solution that is causing this failure. Perhaps you can narrow it down to a small purpose-built code sample you can share?

  15. Cannot debug tests with the 2.17 version

    Thanks Martin. Is there any chance you could share a project or solution with me that can demonstrate these issues? You can submit it via the [url=https://www.ncrunch.net/support/contact]contact form[/url] if you like. If I can get a project that reproduces these issues, there's a good chance I c…

  16. Cannot debug tests with the 2.17 version

    [quote=Cokyn;8016]Good morning, you are right, the same problem is happening during the test run as well so it is not specifically debugging problem. When I created a brand new project with 1 test only then everything seems to be working :/[/quote] Ok - we've now narrowed it down to a soluti…

  17. Error executing tests

    Thanks! I've managed to identify a couple of things that might have the potential to cause the problem you've found. I still have no way to reproduce it, and it isn't clear to me why this is happening on your system and not on others .. though I'd like to try including a speculative fix for it i…

  18. Cannot debug tests with the 2.17 version

    Can you confirm 100% that this is only impacting debug sessions, and that running the tests without the debugger (by right clicking and choosing 'Run') works correctly? If so, does adding a System.Diagnostics.Debugger.Launch(); call into the test allow you to attach a debugger? Does the proble…

  19. Error executing tests

    v2.16 had all the NCrunch modules stored in the root installation directory. So I guess reverting back to 2.16 would put in place the same workaround you'd already discovered (moving the MSTest module to the root install path). In v2.17 they were moved into their own subdirectories to make way for…

  20. Error executing tests

    Thanks! Got it. Could you check if you have any .crunchmodule files sitting under C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\Remco Software\NCrunch for Visual Studio 2015 ? These files should only be inside the nested module directories.