Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. xUnit Collection handling

    [quote=michaellogutov;7623]Well, I guess this is fail-safe implementation but I think it's a huge resource waste in most of use cases.[/quote] Reliable parallel execution through any other method is impossible without requiring people to re-engineer their tests. Unfortunately, most people don't …

  2. slow typing in VS2015

    [quote=willcowell;7618]I have tried varying the [b]Sliding build delay[/b] with values ranging from 500 to 10,000: this had no affect. I have tried two other solutions: an [b]ASP.NET MVC[/b] app and another [b]Windows 8.1 app[/b] (the solution with 19K lines, 2.5K tests is a Windows 8.1 Universal…

  3. slow typing in VS2015

    [quote=willcowell;7619]One other minor difference between the slow solution and the other two that work fine: the slow solution is using MSTest (not my choice!) and the other two are using xUnit.[/quote] Did you have much luck with narrowing down the issue through ignoring projects, or examining …

  4. xUnit Collection handling

    [quote=michaellogutov;7617]Wait, nCrunch run tests in parallel using multple processes instead of threads?[/quote] That's correct. It's a common misconception - [url=http://www.ncrunch.net/documentation/concepts_parallel-execution]http://www.ncrunch.net/documentation/concepts_parallel-execution[…

  5. xUnit Collection handling

    [quote=michaellogutov;7615] Hm... That not what I meant. I have a problem - my xUnit test correctly executing when runned from xUnit console runner even with "parallel all" option (which will make all tests within one collection across assembly to run in parallel). This is because xUnit console ru…

  6. xUnit Collection handling

    Hi, thanks for posting. To avoid confusion and to facilitate better control over system resources, NCrunch deactivates xunit's parallel execution and overrides it with its own. NCrunch already performs parallel execution with better separation between the tests (at process level) as part of it…

  7. slow typing in VS2015

    Thanks for sharing these details. Can you try adjusting the [url=http://www.ncrunch.net/documentation/reference_global-configuration_sliding-build-delay]Sliding build delay[/url] configuration setting to see if this makes any difference? With the issue appearing on such a wide range of differe…

  8. slow typing in VS2015

    Hi Abu, thanks for sharing this issue. Would you be able to help with answering the following questions? This should help with narrowing down the issue: - What are the specifications of the machine you're running on? Is it a high-end system? - Approximately how large is the solution you're …

  9. Unable to Debug tests in Visual Studio 2015

    [quote=Furynation;7607]Thanks Remco. I just filed a bug over at Connect. Hopefully, they'll be able to narrow this down. It started happening now under normal debugging situations.[/quote] I'm sorry to hear that. I recommend sharing a link to your report on connect here, that way if anyone else …

  10. VS 2013 - NCrunch_VS2013_2.16.0.13 - Error

    Hi, thanks for sharing this issue. Does the ActivityLog.xml contain any useful information? A stack trace perhaps? Make sure that when installing manually you also 'unblock' any files you've extracted from the ZIP. Windows can often implicitly block things when perhaps it shouldn't, and this…

  11. Unable to Debug tests in Visual Studio 2015

    This reported issue may be relevant - [url=https://github.com/dotnet/coreclr/issues/1350]https://github.com/dotnet/coreclr/issues/1350[/url].

  12. VS 2015 MSI installer does not work.

    Hi, thanks for reporting this. I've just run a couple of quick tests with a fresh download, and it does seem to be working on my end. Could you try re-downloading to see if this makes any difference?

  13. Build failed on Projects with unsafe code

    Sorry to keep you waiting on this, but a fix for this issue is now available in the just released v2.16 - [url=http://www.ncrunch.net/download]http://www.ncrunch.net/download[/url].

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

    Hi Will, Thanks for sharing this issue. Unfortunately, I have only bad news to report here. NCrunch is reliant on the IApplicationActivationManager.ActivateApplication service call to launch a Windows Store app (or test project) with its sandboxing intact. This is the same service call used …

  15. Support new Universal Windows Apps

    Hi Julien, Thanks for posting! At the moment there are no plans to support Universal apps, but you are welcome to request this as a feature on [url=https://ncrunch.uservoice.com]uservoice[/url].

  16. Build failed on Projects with unsafe code

    Nice work. This consistently reproduces the issue. I'll see what I can do about a fix. I'll get back to you soon.

  17. Build failed on Projects with unsafe code

    Hi, Thanks for sharing this issue. This problem is caused by an incompatibility in NCrunch's instrumentation. Somehow (likely through unsafe code) you've managed to find an IL configuration that NCrunch isn't able to handle. It's often difficult to be sure, but it looks like it may be relate…

  18. Inconsistent tests results

    Hi, thanks for sharing this issue. My first thought is that the code under test may be providing an intermittent pass/fail result, depending upon which tests have been executed before it inside the process. See here for more details about this problem - [url=http://www.ncrunch.net/documentation/…

  19. Build fails with custom analyzers

    Hi Mark, Thanks for the Nuget link. I'm not sure why this wasn't showing up via a Nuget search, but I've managed to install the package and can confirm that this is a dependency resolution issue that can be solved by including the necessary dependencies using the 'Additional files to include' se…

  20. Build fails with custom analyzers

    Hi Mark, Unfortunately I can't seem to find this package in the nuget directory as expected, so I haven't been able to reproduce the issue myself ... however, my first guess would be that this package is making assumptions about output assemblies being co-located: [url=http://www.ncrunch.net/docu…