Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    Hi Tony, can you confirm whether the 3.12.0.1 build has solved this problem for you?

  2. Building precompiled C# Azure Function fails

    [quote=SteveC;11180] @Remco ... any plans to offer support of the various Azure projects, especially the App Service ones, i.e. Web / API / Function App ?[/quote] Sorry :( No short term plans for this. I'm currently overloaded trying to keep up with platform level changes and don't have the c…

  3. Context menu Shift+F10 stopped working in 3.12.0.2 (worked in 3.10)

    I've been making changes to the context menu in preparation for some performance improvements, to resolve problems with the opening times being so high. These changes included moving the opening options to a mouseclick, and it looks like the keyboard shortcut was missed. So this is a regression.…

  4. Don't know how to fix constant "This test was not executed during a planned execution run."

    You'll need to disable this attribute when working under NCrunch. For example: #if !NCRUNCH [assembly: Parallelizable(ParallelScope.Children)] #endif Tracking code coverage data is impossible when tests are being run concurrently in the same process, because there is no way to differentiate…

  5. NCrunch failing to build 4.6.1 project (VS2017)

    Hi Jon, Thanks for sharing this problem. This looks to be a regression in v3.11. Try the build below and see how you go: [url=http://downloads.ncrunch.net/NCrunch_Console_3.12.0.2.msi]http://downloads.ncrunch.net/NCrunch_Console_3.12.0.2.msi[/url] [url=http://downloads.ncrunch.net/NCrunch…

  6. Don't know how to fix constant "This test was not executed during a planned execution run."

    Thanks for the report. Something is going seriously haywire in the way that NUnit is reporting results here. Everything is being reported very badly out of sequence. Are you using any NUnit plugins? Do you have any specially coded settings that might cause NUnit to try to implement concurren…

  7. Don't know how to fix constant "This test was not executed during a planned execution run."

    Something is going seriously wrong in the test process when it tries to execute your tests. If you can send through a bug report after you've had this happen, I should be able to advise further. If there's an error, this should show up in the logs. If you set your 'Log Verbosity' setting to 'De…

  8. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    I'm going to lock this topic now, because it's becoming a catch-all for every problem even vaguely related to .NET Core and .NET Standard. I hope that we're most of the way there now towards full compatibility with this platform. If anyone is still experiencing problems, please create a new thread…

  9. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    [quote=Der-Albert.com;11166] of course .... first thought "Running not as a Service, i switched that to the Local User Account and it worked".... well, lets take a look to be sure. No, is running under local System. WTF. So one of the Upgrade Installs, uninstalls, and reinstalls killed the LogO…

  10. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    Can you confirm whether the grid node is running as local system, or a user account? I remember encountering some strange behaviour when trying to build and run tests under the system profile, because this stores the nuget package cache under Windows\System32 (a bad thing). Of interest is also w…

  11. 'Show unexecuted tests' behavior

    [quote=wilhelmmedetz;11161]Hi Remco, 'make the Tests Window filter more configurable so that you can show tests that are passing but out of date, while hiding the tests that are passing but are current.' seems to be exactly what I want. [/quote] Great :) Would you like to write up a [dead lin…

  12. AtomicAttribute and 'Run selected test in new task runner process'

    Hi Wilhelm, This is the design and intention of AtomicAttribute. See here for more information: [url=http://www.ncrunch.net/documentation/reference_runtime-framework_atomic-attribute]http://www.ncrunch.net/documentation/reference_runtime-framework_atomic-attribute[/url]. When a test fixture i…

  13. 'Show unexecuted tests' behavior

    Hi Wilhelm, There is a special state that the NCrunch engine uses for this. You'll notice that the status of these tests is set to Passing but Out Of Date, which is symbolised by a green question mark. Code coverage for the tests is then faded somewhat to show that this data is outdated. To …

  14. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    [quote=damianh;11152] Yeah VS, VS Test Runner, Resharper Test runner, Rider and CLI all worked :/ Edit: perhaps NCrunch should be less strict here, if the others handle it gracefully? Just a thought. Low priority.[/quote] When this area of NCrunch was built, such a recursive structure was imp…

  15. Tests utilising Microsoft.AspNet.TestHost fail in NCrunch

    .NET Core 2.0 broke everything here again, so we now need a new fixed build to address the broken areas. If you're seeing this problem in v3.11 of NCrunch under .NET Core 2.0, try the build below to see if it resolves the problem for you. [url=http://downloads.ncrunch.net/NCrunch_Console_3.12.0.…

  16. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    Hi Michal, Here is a build with a fix for you: [url=http://downloads.ncrunch.net/NCrunch_Console_3.12.0.1.msi]http://downloads.ncrunch.net/NCrunch_Console_3.12.0.1.msi[/url] [url=http://downloads.ncrunch.net/NCrunch_Console_3.12.0.1.zip]http://downloads.ncrunch.net/NCrunch_Console_3.12.0.1.zi…

  17. Grid Server keeps disconnecting

    Setting the log verbosity to Summary may prevent these warnings from being processed into the logs. It's still not clear to me why you are experiencing disconnection problems. Considering the buffering fix didn't have any effect for you, I have a stronger feeling that the connection instability is…

  18. Could not load file or assembly 'System.Runtime, Version=4.1.1.0...'

    If this message does give you trouble, it may be worth upgrading to the full release version of 3.11 (released just yesterday). This included a few resolution fixes over the preview version you've been running.

  19. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    Hi Michal, Thanks for sharing this problem. This is being caused by a .deps file generation issue in NCrunch related to the AspNet.TestHost library. A code fix will be required to resolve this problem. I'll let you know as soon as I have a fixed build available.

  20. Unable to run tests with .NET Core 2.0 referencing .NET Standard 2.0

    Hi Damian, Thanks for sharing the source code demonstrating the problem, this always makes things easier. This problem looks to be caused by a referencing issue in your solution. The solution has a Directory.Build.props file at its base, which by MSBuild convention is automatically included in …