Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Base class is not showing any code coverage

    Hi, thanks for sharing this issue. Can you confirm whether the black/white markers are showing on the base class with the missing coverage? (relevant as it determines whether the type is instrumented correctly). If you run the covering tests under NCrunch with a debugger attached, do breakpoin…

  2. .NET8 Preview 7

    I've looking into .NET 8 support now under NCrunch, as it's reached RC status and looks ready to drop soon. The good news is that at a cursory glance, it seems that the builds of NCrunch we have out right now can probably already handle .NET 8. The error being kicked up here is caused by NCrunch…

  3. CilAssemblyNotFoundException

    [quote=IanBowyer;16891]Thank you that worked. I knew there would be a setting somewhere I just couldn't find it.[/quote] Thanks for confirming this. We do have a fix pending for this issue which will be out with the next release. I'd suggest staying with DynamicAnalysis for now.

  4. CilAssemblyNotFoundException

    Hi, thanks for sharing this issue. Can you confirm if setting your 'Framework utilisation type for MSTest' to 'DynamicAnalysis' works around the problem?

  5. ClassInitializeAttribute from Base Class isn't executed (MSTest)

    Sorry, we've pretty snowed under with V5 work at the moment. I hope to get to this issue later in the year. I'd recommend adapting your code with a workaround for the time being, I don't think I'll be able to provide a fix for this in the short term.

  6. Tweak settings to behave like "dotnet test" runner with 1 process ?

    Hi, thanks for sharing this issue. Because of the design of the engine and the limitations of the frameworks we integrate with, we can't have NCrunch simulate the process hosting behavior of a serial test runner without axing many of the features that make it worth using. Marking the tests with …

  7. Endless churn to respect engine mode

    Hi, The best way to do this is to pin the tests you want to churn, then select them in the Tests Window and use the context menu option to churn the tests until they fail. Churn mode lets you work with targeted tests too (not just the whole lot), so I hope there would be no need to involve the…

  8. NCrunch fails to build a project when there's a file in it with long path

    Hi, thanks for sharing this issue. The last time I checked, support for LongPathsEnabled is quite hit-and-miss in the underlying toolset, so this particular error can still happen. The simple fix for this issue is to change your 'Workspace base path' setting to put it closer to the root of C: …

  9. Unable to pin or unpin tests in bulk

    Hi, thanks for sharing this issue. We haven't changed anything around the pinning functionality in quite a while. Can you submit a bug report after using the bulk unpin option and having it fail for you? I'm hopeful the log in the report will yield some clues as to what is happening here.

  10. NCrunch.Framework 4.17.0.5 transitive dependency vulnerability

    I would argue that this is probably a false positive. NCrunch.Framework only has one package reference, which is to System.Collections.NonGeneric. I expect this is probably being raised because NCrunch.Framework is compiled to target netstandard 1.5, which is done for compatibility with older ve…

  11. NCrunch tests fail randomly

    It does feel like a bit of an intellisense trap. There should be a relatively trivial way to search out these calls and flag them up in a test using Mono.Cecil to traverse the test assemblies and examine the IL in each method. It might only take a few minutes to write (maybe ChatGPT could even wri…

  12. ClassInitializeAttribute from Base Class isn't executed (MSTest)

    Hi, thanks for sharing this. Yes, we have no handling for InheritanceBehavior.BeforeEachDerivedClass. I'll take a look and see if we can find a way to introduce it.

  13. NCrunch tests fail randomly

    Wow, this is nasty. We've had our own share of sequence dependent issues like this with our tests. It's not easy to track them down. You did well to isolate this. I'd suggest raising it with the NSubstitute devs. It seems like something that many people would have trouble with. Note that…

  14. NCrunch tests fail randomly

    I suspect this issue may depend on the sequence in which your tests are executing. Can you try placing the NCrunch.Framework.IsolatedAttribute at assembly level in all of your test projects? It will be interesting to see if this gets rid of the problem. When tests are marked as isolated, they w…

  15. Avalonia Build Failure -- InitializeComponent

    Hi, thanks for posting. We haven't put in place any integration with Avalonia. My best guess would be that this is being caused by a malfunctioning build step or a file that isn't being picked up by NCrunch. Could you try [url=https://www.ncrunch.net/documentation/troubleshooting_compatibilit…

  16. Dots are white, saying no covering tests (VS 2022)

    Great to hear you are back up and running again. If you find a way to reproduce this, could you please let me know?

  17. Dots are white, saying no covering tests (VS 2022)

    Hi, thanks for posting. v4.18 has been out since mid July, and this is the first report we've had of this kind with this build. Can you check whether [url=https://www.ncrunch.net/documentation/troubleshooting_missing-code-coverage]this documentation page[/url] helps at all?

  18. NCrunch tests fail randomly

    Can you get it to happen for specific tests by using Churn Mode? Does setting your 'Instrument output assembly' setting to 'False' for all the involved projects resolve the issue? (note this will drop all code coverage)

  19. NCrunch internal exception

    Hi, thanks for sharing this issue. This problem is caused by an odd structure in the CIL of the assembly being instrumented by NCrunch. We've seen this one in the wild before, but it tends to be fleeting and seems to depend on the size of the assembly in question. So far, we haven't been able t…

  20. NCrunch tests fail randomly

    [quote=zlicht;16843] I was wrong about the previous statement. I added meaningless spaces to trigger NCrunch.[/quote] Can you confirm whether you receive this problem when running the tests using any other runner? Is this something you can reproduce with a sample solution that you might be ab…