Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Console farms out a excessive number of tests to a single processing thread

    Thanks for these extra details. For some reason, the engine running in the console tool seems to think that the 5793 tests have a very low execution time, and that it must therefore be optimal to run them in one batch. I wonder if this may be caused by cached data being used by the console too…

  2. Unpinned tests reappear as pinned

    Thanks for these extra details. I think I understand what is happening here. The 'Run pinned tests automatically, others manually' default engine mode is configured with a config setting override that will automatically pin a test when it is newly discovered. When you switch branches, this ca…

  3. Unable to cast object of type

    Thanks for sharing this issue. I've reproduced it as described. It looks like we're not handling the separators properly. This should be a simple fix. I'll ensure it's included in the next build published.

  4. Unpinned tests reappear as pinned

    For step 4, is the engine restarting automatically, or is this being done manually in the UI? If you restart VS during switching of branches, do you experience the same problem? If not, what kind of behaviour do you see if you have the NCrunch engine shut down when you switch branch?

  5. Console farms out a excessive number of tests to a single processing thread

    Hi, thanks for sharing this issue. Can you share any more details about how you're observing this? Is this using the timeline report? Does the running of these tests work the same way when you run it from the NCrunch VS/Rider clients? Or do you see something different?

  6. Unpinned tests reappear as pinned

    Hi, thanks for sharing this issue. The 'pinned' status is a state flag that is stored with the representation of the test inside NCrunch's .NCrunch_SolutionName\SolutionName.crunchsolution.cache file. This allows it to persist between sessions of NCrunch. However, when you unpin a test, this …

  7. .NET Core unit tests for project build as exe

    [quote=piotr_s;17655]I appreciate you help. It would be great if NCrunch would have such a functionality (maybe not turned of by default, it could be configurable).[/quote] No need to configure. We have enough settings already. It should just happen, like the other files in the workspace. I …

  8. .NET Core unit tests for project build as exe

    [quote=piotr_s;17649]In my opinion, instead of necessity to write additional code to copy .exe file or linking it as resource, NCrunch should know that if the project is configured as windows application (console or desktop), there are two files .exe and .dll and these two files should be copied to …

  9. cache storage path

    Hi, thanks for posting. This warning was introduced a number of years ago when I discovered a performance issue in the VS Git provider that was hammering NCrunch. At the time, their Git provider was still in its early days of development, but it was in the default installation of VS and would en…

  10. Rider: Tool Window Arrangement State is shared between projects opened at the same time

    [quote=Der-Albert.com;17651] On the Plus side, the docked Test Windows does not steal my keystrokes anymore (like the DELETE/BACKSPACE Key in an Input Field). Before that, I had occasionally Dock and Undock the NCrunch Tool Windows (also with 5.10) to finish the input.[/quote] I'd like to say th…

  11. Rider: NCrunch Tool Windows Content does resize width after after using Windows Snap Feature

    Thanks for sharing this. Can you confirm which IDE you're seeing this problem in?

  12. Rider: Flickering when using horizontal window split

    This issue should be resolved now in NCrunch v5.10 (for both VS and Rider).

  13. RDI and Console Tool / Continous Integration

    Hi, thanks for posting. At the moment, the console tool can't make use of RDI data. It stores it but there is no way to usefully retrieve it. At some stage we might add this, but it's hard to do as we don't have an available UI to bolt it into. You can override settings via the command line …

  14. Rider: Tool Window Arrangement State is shared between projects opened at the same time

    Jetbrains have responded here with the following: This is likely [url=https://youtrack.jetbrains.com/issue/RIDER-116113]RIDER-116113[/url], a known regression we are planning to fix soon. Additionally, please be aware that - Rider has a mode enabled by default that syncs the tool window state…

  15. Rider: Tool Window Arrangement State is shared between projects opened at the same time

    Thanks for sharing this. We've been tracking cross-instance problems like this for a while now. Rider is a bit unique in that to have multiple sessions open at one time, you need to start one session and then open other sessions from that first session. This causes environment variables to prop…

  16. .NET Core unit tests for project build as exe

    My understanding of this .EXE file is that it functions in the same way as calling dotnet.exe with your DLL. If you use dotnet.exe (usually under C:\Program Files\dotnet) to call the DLL instead of calling the .EXE directly, it should be possible to run the code without requiring it. Another o…

  17. Static init code coverage is suppressed when TestCaseSource is used

    Hi, yes this is behaviour as designed. We don't track code coverage data inside the analysis/discovery step. Because the static initializers are technically housed inside the static constructor for the class, they get executed during discovery. Generally, we re-use the test process that was use…

  18. .NET Core unit tests for project build as exe

    Hi, thanks for posting. The .EXE file you are referring to is just a shim that invokes the runtime to load the .DLL. Because it doesn't form part of the normal dependency structure of the solution, the 'Copy referenced assemblies to workspace' setting won't automatically copy it to the test proj…

  19. NCrunch Hot Spots not updating when coverage filter is active

    The hot spots window is the only window in the NCrunch UI that doesn't automatically update itself as the underlying data changes. It's the only part of the UI that has a Refresh button. We didn't really want it to be like this, but it's a very expensive view to create, and updating it in real t…

  20. Xunit.v3 analysis failure

    Thanks for sharing this issue. This is caused by an inconsistency between the xunit runner libraries that are packaged with NCrunch, and the xunit runtime libraries referenced from your test project. Basically, the main xunit Nuget package doesn't ship with the runner libraries, so it's the re…