Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. NCrunch runs fine in VS 2017.2 and breaks in VS 2017.3 (preview 3)

    NCrunch v3.10 has [url=http://www.ncrunch.net/download]now been released[/url], including preview support for VS2017.15.3.

  2. Visual Studio 2017 Preview 15.3

    NCrunch v3.10 has [url=http://www.ncrunch.net/download]now been released[/url].

  3. reflection issue

    NCrunch v3.10 has [url=http://www.ncrunch.net/download]now been released[/url].

  4. reflection issue

    This is likely to be related to NCrunch's handling of the .deps file used to build the test environment. [url=http://forum.ncrunch.net/yaf_postst2163_Tests-utilising-Microsoft-AspNet-TestHost-i-c-w--MVC-Views-fail-in-NCrunch.aspx]This issue is probably the same one[/url]. You'll find a published…

  5. Certain Tests Won't Run (Collection was modified from GetAccessedFiles)

    [quote=rlawley;10783]Ok, thanks. Is there any way to disable this globally, rather than in each solution's settings?[/quote] Absolutely. In your NCrunch configuration window, make sure you turn off 'Use Simplified Configuration Settings', then choose 'General Settings' in the tree, and set the …

  6. Certain Tests Won't Run (Collection was modified from GetAccessedFiles)

    [quote=rlawley;10781] I'm not aware of my tests having any background code, and this certainly isn't something which has changed recently if any do. Is this a feature recently added to ncrunch? [/quote] Yes. This was added in NCrunch V3.0 with the improved impact detection. The feature isn't…

  7. NCrunch was unable to locate this test during NUnit's execution run.

    [quote=dariusdamalakas;10777]Good point - yes, we do use SetUpFixture. Sets up logging, and some other static properties. Do you think this would have an impact in certain situations?[/quote] It depends upon the behaviour you have coded in here, but I can tell you that if the code in a SetUpFixt…

  8. Visual Studio 2017 Preview 15.3

    It'll be here soon. Keep an eye out over the coming week.

  9. Tests suddenly start failing with NCrunch v3.9.0.1

    [quote=tsimbalar;10772]Oh I see, well that's a bummer :-/ Usually, when I use XUnit Theory and parameterized tests, I like to use as a parameter a string "reason" that is a unique description of this test case for human beings ... Given that in those cases, one of the parameter could possibly use…

  10. Nancy test doesn't discover modules

    Hi, thanks for sharing this question. It's been a few years since I last tangled with the Nancy codebase, so my present knowledge on how it resolves assembly references is very uncertain and probably very out of date. Given the way this is structured, my first assumption would be that Nancy has …

  11. Tests suddenly start failing with NCrunch v3.9.0.1

    Hi, thanks for sharing this problem. This is caused by a compatibility problem with AutoFixture. Unfortunately, there is no solution available for this problem. AutoFixture is officially unsupported by NCrunch. For more information about this problem: [url=http://www.ncrunch.net/documentatio…

  12. Certain Tests Won't Run (Collection was modified from GetAccessedFiles)

    Hi, thanks for sharing this problem. This problem has me quite puzzled, mostly because the collection involved is fully contained within thread locks and there doesn't seem to be any way that it should change outside this. I haven't been able to reproduce the problem itself, but I can give more …

  13. NullReferenceException with NCrunch 3.9.0.1

    Hi, this does look like the same issue. We have at least one test here that is somehow disassociated with all the projects in your solution, so it's basically floating around disconnected. This could be due to something going wrong in the startup process, or cache data corruption, or possibly some…

  14. NCrunch was unable to locate this test during NUnit's execution run.

    Are you using a SetUpFixture of any kind? It seems like something is going wrong inside the NUnit environment itself. Would you be able to submit a bug report immediately after the issue appears?

  15. NCrunch was unable to locate this test during NUnit's execution run.

    Hi, thanks for sharing this problem. Although changing your framework utilisation type to static analysis is recommend in the error message (as sometimes this works), static analysis is considered to be generally less compatible than dynamic analysis under NUnit. Especially so when dealing with …

  16. NUnit 3 and OneTimeSetUpAttribute

    Hi Ed, Thanks for sharing this problem. Are you able to share any code that I might be able to use to reproduce it? Presently all NCrunch tests around this are passing, so it may be a use case that I haven't been tracking. Usually this sort of thing is all handled internally within NUnit. D…

  17. NullReferenceException with NCrunch 3.9.0.1

    Hi, thanks for posting. There are two different exceptions thrown here. One is related to connectivity, and is known to be caused by unexpected disconnection with a grid node. This is essentially a 'noise' exception, as the client will always reconnect when this happens. There are some improve…

  18. Can't uninstall NCrunch with Visual Studio 2017 Enterprise

    Hi, thanks for posting. Make sure that all installed files under "C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\Remco Software" (or your normal install path) are removed. Then run the following as an administrator: "C:\Program Files (x86)\Microsoft Visu…

  19. ConsoleTool: System.AccessViolationException: Attempted to read or write protected memory.

    The socket related issue above is essentially a noise exception that can happen if the connection is suddenly closed without warning. This won't be related to the earlier problem you've reported, but it does make sense that this could slow things down for your test run. A disconnection means that …

  20. ConsoleTool: System.AccessViolationException: Attempted to read or write protected memory.

    I've seen this also, rarely, on a heavyweight grid node. It may take me time to track it down. I had hoped I was the only one seeing it. I guess you just crushed that delusion :( A reset of the client or grid node always gets rid of it.