Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Hiding NUnit unit test with the Ignore attribute

    Unless you have disabled the MSTest adapter, this test will still be discovered by MSTest. MSTest uses its own ignore attribute and does not consider the NUnit one. This means you'll need to ignore the test for both frameworks.

    26 Feb 2019 00:18 UTC

  2. Slow unit test runs forever

    It's better not to think of tests as having high algorithmic complexity, but rather code itself. Look for areas of your code where the NCrunch hotspots are showing your tests as spending a large amount of time, and suppress coverage for these areas. These areas are unlikely to cover a very large…

    26 Feb 2019 00:15 UTC

  3. Could not locate the assembly "System.ValueTuple"

    Thanks for sending this through. We'll take a look and will let you know as soon as we have more information.

    26 Feb 2019 00:06 UTC

  4. Hiding NUnit unit test with the Ignore attribute

    Hi Alberto, NCrunch will not discover tests marked with an NUnit ignore attribute. If a test is marked with this correctly, it will never show in the tests window.

    24 Feb 2019 21:02 UTC

  5. Slow unit test runs forever

    Disabling instrumentation is something I would suggest in this case only as a temporary measure to discover the source of this problem. When it's off, you'll lose all code coverage information. Better to find the bottleneck methods and simply use the coverage suppression for them to make them ru…

    24 Feb 2019 21:01 UTC

  6. Slow unit test runs forever

    Do you have any tests with high algorithmic complexity? Try temporarily disabling the [url=https://www.ncrunch.net/documentation/reference_project-configuration_instrument-output-assembly]instrument output assembly[/url] setting to see if this makes a difference, or find blocks of code that have the…

    23 Feb 2019 22:12 UTC

  7. How to remove .ncrunchproject files from .Net Core project

    Hi, thanks for posting. The .NET Core CPS project system used by VS will implicitly include any file in the project directory. It isn't safe for NCrunch to mess with this logic. You can, however, configure NCrunch to place its config files in a different place using the [url=https://www.ncrun…

    21 Feb 2019 22:43 UTC

  8. Slow unit test runs forever

    Hi Alberto, I'd suggest hooking a debugger onto these hung processes to see what they're doing. As they're likely executing user code, unfortunately there's no blanket answer I can give as to what might be causing this. Note that if this is the first time you're running tests over a solution,…

    20 Feb 2019 21:25 UTC

  9. Unstable Test Generation

    Hi, thanks for sharing this issue. The problem here is that when NCrunch asks NUnit for a list of tests, it's getting a different result even though the assembly is exactly the same. It isn't possible for NCrunch to know specifically which tests are at fault here. It also isn't possible for N…

    20 Feb 2019 20:39 UTC

  10. Forcing NUnit

    For this you can just disable one of NCrunch's adapters and use the framework of your choice. The MSTest one is probably higher performance, as it's actually an emulator (not integrated), so NCrunch has more optimisation options for it.

    19 Feb 2019 22:17 UTC

  11. How to Prevent Build Events on .NET Standard 2 Library

    Hi Chris, Thanks for sharing this problem. There are two different pre-build events that can be declared in a project. One is using the 'PreBuildEvent' project property, the other is by declaring a pre-build target. By default (and through the configuration setting you've found), NCrunch d…

    19 Feb 2019 22:15 UTC

  12. Forcing NUnit

    Hi Alberto, NCrunch uses its own adapters to interact with test frameworks, it doesn't integrate with Resharper or VSTest. So the only way for NCrunch to run NUnit tests is with its NUnit adapter, and the only way it can run MSTest tests is using its own MSTest adapter (which is actually an emul…

    18 Feb 2019 21:37 UTC

  13. Forcing NUnit

    Hi Alberto, I'm not entirely sure what you're asking. NCrunch uses different adapters for each of these frameworks. If you have a project using both frameworks, NCrunch will use both adapters to execute all of the tests. It's possible to disable the adapters on a per-project basis via the co…

    18 Feb 2019 10:28 UTC

  14. Support for VS 2019?

    An update here.. We've actually been quietly working on this since December. MS have made significant internal changes in VS2019 and we wanted to be ready for this release, so we've been working with them in lockstep (admittedly somewhat painfully). I'm aware that they've announced a launch d…

    17 Feb 2019 21:57 UTC

  15. 5GB of dataset needed by unit tests

    Hi Alberto, For resources of this size, copying to workspaces is not recommended. You'll probably run out of disk space if you have too many runner processes. Instead, try using the [url=https://www.ncrunch.net/documentation/reference_runtime-framework_environment-class]NCrunchEnvironment.Get…

    17 Feb 2019 21:52 UTC

  16. There is a circular dependency in the target dependency graph involving target "ReBuild"

    Hi Alberto, Thanks for sending through the sample solution. The problem you're experiencing here seems to relate to a strange modification that has been made to these project files. At the top of the file, the project has been set to use a default target of 'Rebuild'. This seems to cause som…

    15 Feb 2019 22:09 UTC

  17. Not abled to run Test ASP.NET TestHost.TestServer on GridNode

    Here's a build with a fix: [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_3.24.0.1.msi]NCrunch_Console_3.24.0.1.msi[/url] [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_3.24.0.1.zip]NCrunch_Console_3.24.0.1.zip[/url] [url=https://s3.amazonaws.com/downlo…

    15 Feb 2019 05:41 UTC

  18. Not abled to run Test ASP.NET TestHost.TestServer on GridNode

    Good catch! Thanks for sharing this. It looks like we didn't test the ASP.NET TestHost properly using distributed processing. I have a fix pending, but our build system is dealing with the VS2019 chaos at the moment, so it might be a few days before I'm able to get it published for you.

    15 Feb 2019 00:12 UTC

  19. dotnet.exe hosted by nCrunch.EngineHost462.x64.exe using 25% CPU doing nothing

    [quote=slafave;13077]Found it and you were right, not an NCrunch issue. Not even a DotNetCore issue. An ancient class buried deep in a series of mocks had a timer that activated a while loop that spun over an empty array to simulate polling a queue. :-( Thanks for the help, sorry to bother you …

    14 Feb 2019 21:46 UTC

  20. "Impacted test" ignoring coverage filter?

    This is intentional. The coverage filter is just a UI-based filter that blocks out coverage data from all other tests. It doesn't affect the internal behaviour of the engine. It's possible to set up your own engine mode that has a coverage filter along with an execution filter, so you can easil…

    13 Feb 2019 21:04 UTC