Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Grid node stuck on initializing

    Hi, thanks for posting. It's possible somehow the node is bugging out during its bootstrap. Could you try turning on the logging feature inside the grid node's configuration tool, then checking to see if there are any exceptions in the logs?

    01 Dec 2018 01:15 UTC

  2. Code Coverage Markers Misaligned

    [quote=chonuff;12861] It happens consistently on certain files (I didn't find any that had issues that weren't repeatable), however you're absolutely right that scrolling seemed to fix the alignment issue. I also tried disabling CodeLens, and it rendered without issue. Upon re-enabling CodeLens, th…

    29 Nov 2018 00:20 UTC

  3. Problem with impacted test for "Track File Dependencies"

    [quote=GreenMoose;12858]Although... It is a real pity this very neat feature does not work with net core. Is there any plans of supporting it?[/quote] Sadly, this feature is heavily dependent on a 3rd party library that hasn't yet been updated to support .NET Core. Maybe we'll have a chance to…

    29 Nov 2018 00:08 UTC

  4. Code Coverage Markers Misaligned

    [quote=chonuff;12859]I'm seeing the same thing as Remco with the latest build in VS2017 using CodeLens. I noted that the NCrunch markers are lined up properly initially, then the CodeLens information pushes the lines downward. Unfortunately, the NCrunch markers don't follow the lines. Is it poss…

    28 Nov 2018 23:55 UTC

  5. Problem with impacted test for "Track File Dependencies"

    I expect that the .resx files likely won't trigger the impact detection using this feature, as they get accessed by the runtime prior to the test beginning its execution. Good catch on the documentation. I'll make sure this gets updated with our next release :)

    27 Nov 2018 23:14 UTC

  6. Problem with impacted test for "Track File Dependencies"

    Hi, thanks for posting. The tracking of file dependencies for the purposes of impact detection is best effort, since there's quite a few constraints around what we can easily do in this area. This feature is subject to a couple of critical conditions that I know about: 1. The files being acce…

    27 Nov 2018 00:17 UTC

  7. NChrunch 3.22.0.1 has issue with with building.

    Hi, Thanks for sharing this issue. I've reproduced it as you've described. The problem is caused by FSharp Type Providers being used in the referenced assemblies. Type Providers are a special feature native to FSharp, allowing assemblies to create implicit design-time references to other ass…

    24 Nov 2018 23:59 UTC

  8. Re-run specific tests

    The cache file is usually stored on the machine running NCrunch.exe. This file won't be stored on the grid nodes, although they do have cached data of a different kind (not relevant in this scenario). The contents of the cache file can be quite important when using the NCrunch console tool in th…

    24 Nov 2018 23:37 UTC

  9. Extra tests reported in TC.

    Hi Sam, Thanks for posting. This is behaviour as designed, because without it we have no way to report data from the fixtures themselves. It's quite common for fixture tests to report information outside their child tests. For example, trace data and code coverage data from methods like Te…

    24 Nov 2018 23:31 UTC

  10. Re-run specific tests

    Hi Sam, Thanks for posting. The best way I can think of to handle this would be to have a second engine mode that only runs tests that have been marked as failed. Once the first run completes and the intermittent tests fail, they'll be stored in the NCrunch .cache file with a failed status. …

    23 Nov 2018 23:03 UTC

  11. NCrunch Console and TeamCity muted tests

    Hi, Right now there is no option in NCrunch that will shut this off. We'd probably need to implement another configuration switch to handle it. You can [url=https://ncrunch.uservoice.com]write a request for this on uservoice if you like[/url].

    20 Nov 2018 20:34 UTC

  12. NCrunch does not work with MSBuild.Sdk.Extras based project.

    Hi, thanks for sharing this problem. Please note that right now Xamarin is not a supported platform under NCrunch (for building or test environments). We have performed no testing or integration in this area - [url=https://www.ncrunch.net/support/frameworks]https://www.ncrunch.net/support/framew…

    20 Nov 2018 20:18 UTC

  13. Grid Node - AccessViolationException - Protected Memory Issue

    [quote=MatthewSteeples;12831] An acceptable workaround for us is to declare the T4MVC.cs file as exempt from coverage. Is there an easy way to do that not using comments? Reason I'm asking is that the .cs file is autogenerated from a .tt file, so if we make the change manually it'll get overwritten…

    20 Nov 2018 01:17 UTC

  14. System.Runtime 4.1.2.0

    I can confirm that in this case, the problem and fix for the problem were both in the NCrunch codebase. A recent VS release (I think it was 15.7?) introduced a new build-time redirection system to try and retroactively add support for .NET Standard 2.0 in earlier versions of the .NET Framework. …

    20 Nov 2018 01:14 UTC

  15. Grid Node - AccessViolationException - Protected Memory Issue

    Hi, thanks for sharing this issue. It's interesting that this code is reporting an exception on line 0. I can see how that would lead to problems with coverage tracking. Do you know how this is happening? Are there compiler declarations in place in your generated code to redirect the line re…

    19 Nov 2018 20:04 UTC

  16. System.Runtime 4.1.2.0

    I think I may have managed to pin this down. Would you like to try the build below to see if this solves the problem for you? Note that you'll need to update both the clients and grid nodes. [url=https://s3.amazonaws.com/downloads.ncrunch.net/NCrunch_Console_3.23.0.4.msi]NCrunch_Console_3.23.0.…

    18 Nov 2018 22:52 UTC

  17. Resource Assembies from Referenced Assemblies are not loaded

    When the 'Copy Referenced Assemblies to Workspace' setting is enabled for a project, NCrunch will always copy its references to the project build output directory. This means that TheLibrary.dll lands inside NCrunchNETCoreLocalizationTests\bin\Debug\netcoreapp2.1, and its satellite assemblies are a…

    16 Nov 2018 02:00 UTC

  18. System.Runtime 4.1.2.0

    Thanks for these extra details. We're doing some testing here to see if we can find a way to reproduce this issue. I'll let you know as soon as we have more information.

    15 Nov 2018 23:04 UTC

  19. Resource Assembies from Referenced Assemblies are not loaded

    Thanks for sharing this problem. This looks to be a classic case of framework code assuming that dependency DLLs are collocated with the project's output assembly. Turning on the 'Copy referenced assemblies to workspace' seems to resolve this problem. The root of the issue is that the Resourc…

    15 Nov 2018 22:58 UTC

  20. Type mismatch on test parameter 2 (parameter should not be null)

    Hi, thanks for sharing this issue. I've reproduced it exactly as described. This looks like an edge case where NCrunch's emulator just doesn't match the same behaviour. I've noted this down to be fixed in the next release.

    15 Nov 2018 00:31 UTC