Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Cleanup during NCrunch process exit?

    Hi, Unfortunately, there isn't a reliable way to do this, as NCrunch terminates its processes externally (by the engine itself). In earlier versions, the process was responsible for terminating itself in response to requests from the engine, but this proved problematic as sometimes user code w…

    20 Apr 2016 22:39 UTC

  2. .NET Framework 4.6.2 FSharp Analysis Failure

    Hi, Thanks for sharing this issue. As 4.6.2 is still in a preview state, it isn't yet supported by NCrunch. A targeted task runner will be introduced for this version of the framework when it is officially released.

    20 Apr 2016 12:25 UTC

  3. Possible bug with XML results output

    I'll see if I can squeeze it into the 2.21 release due this week.

    20 Apr 2016 12:21 UTC

  4. Possible bug with XML results output

    Interesting, thanks for letting me know about this one. I'll make a note to get it fixed.

    19 Apr 2016 11:05 UTC

  5. NCrunch Tests Window - Run All Tests Disabled

    Hi Bob, These two toolbar options are dependent on the selected item in the Tests Window. In this situation, you have no tests selected, so the toolbar options are disabled. Try turning on the green checkmark so that your passing tests are visible, then try selecting a test. The buttons sh…

    19 Apr 2016 04:10 UTC

  6. Grid Node + MSBuild 14 detection

    Hi, thanks for sharing this issue. NCrunch searches for MSBuild through the presence of the "Microsoft.Build, Version=14.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a, processorArchitecture=MSIL" assembly inside the GAC. If NCrunch can't find this file in the GAC, it won't be able to r…

    19 Apr 2016 04:08 UTC

  7. NCrunch Tests Window - Run All Tests Disabled

    Hi Bob, Sorry - for some reason, the image you've linked to doesn't seem to open for me (access denied perhaps)? Are you able to access these options via context menu? Can you submit a bug report? I wonder if something is going wrong under the hood.

    19 Apr 2016 00:11 UTC

  8. Re-running failed tests via NCrunch grid and TeamCity

    Your understanding is correct - the IsFailing flag should be the only one you need. I've just done some testing on my side with the same scenario, as I personally haven't tested these features used together in quite the same way as you're running them right now. The engine functioned largely as …

    18 Apr 2016 00:26 UTC

  9. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    MbUnit seems to have frozen in time, but Xunit is being actively worked on at the moment. Xunit doesn't suffer from this problem because it uses algorithmically generated IDs for each test (I've been suggesting the same approach to the NUnit developers). I expect that this problem will eventuall…

    15 Apr 2016 22:42 UTC

  10. Re-running failed tests via NCrunch grid and TeamCity

    [quote=Phonesis;8606] Thanks Remco, much appreciated. Will try this. In your link, it mentiones the path must be relative to the solution? Can I do something like: <NCrunchCacheStoragePath>C:\NCrunchCacheFiles\</NCrunchCacheStoragePath> [/quote] Yes! That should work correctly. The c…

    15 Apr 2016 11:57 UTC

  11. Listed tests that cover code not correct

    Hi, thanks for sharing this code sample. In this instance, the code coverage data shown by NCrunch is physically correct, because it represents the true path of execution of each test. Note that the ClassInitialize attribute doesn't work when applied on base classes under MSTest, so it is not …

    15 Apr 2016 05:56 UTC

  12. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    [quote=jnm236;8600] What is your opinion on using the test name rather than the ID? That includes the parameter and is required to be unique. There's also a huge plus with using the name. Even if names aren't unique, humans will not care if you switch tests results with the same name because that'…

    15 Apr 2016 05:39 UTC

  13. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    Thanks for sharing the code sample, this really makes things much easier to understand. I can see what's happening here now. As mentioned earlier, NUnit uses sequential IDs to identify tests internally. This doesn't work well for NCrunch, because NCrunch needs to be able to correlate test resul…

    14 Apr 2016 23:54 UTC

  14. Re-running failed tests via NCrunch grid and TeamCity

    Hi, thanks for posting. Most likely this is caused by a lack of cached test results on the TeamCity controller. When NCrunch shuts down or completes a run of the console tool, it will store all results (including code coverage and timing information) inside a .cache file underneath an _NCrunch…

    14 Apr 2016 23:22 UTC

  15. NCrunch cannot load project when using VLC binaries

    Hi Thomas, Thanks for sharing this issue. This problem looks to be caused by a bad evaluation sequence in NCrunch's interaction with MSBuild during project load. The VLC targets file includes a property that is evaluated before NCrunch sets the $(SolutionDir) property, and this causes the eva…

    14 Apr 2016 07:06 UTC

  16. UI does not reflect changed NUnit TestCaseSource data, leading to running the wrong tests

    Hi, thanks for sharing this issue. NUnit internally uses sequential IDs to identify tests. This creates problems for NCrunch in identifying the tests between changed assemblies, so NCrunch instead uses test names for identification. However, it still needs to feed the sequential IDs into the te…

    13 Apr 2016 22:49 UTC

  17. Integration Testing with EF Code First and Migrations

    Hi Chuck, The numbered names of the NCrunch workspaces are just sequentially generated - they don't have a direct relationship with the processes used to run your tests. If your tests are set up to run in parallel (which yours are), you'll likely observe many test runner processes sharing the sa…

    13 Apr 2016 12:43 UTC

  18. Can't go to selected Test from NCrunch Tests Tool Window in VS 2015 CTP5

    Thanks for your help here. I've now managed to reproduce this issue. I can confirm this is a regression in 2.20. It impacts ALL Xunit v1 theories, regardless of custom attributes, autofixture, etc. Xunit v2 is not affected by this problem. A fix will be out for this in the next release of…

    13 Apr 2016 05:02 UTC

  19. Integration Testing with EF Code First and Migrations

    Hi Chuck, Thanks for posting! The answer to your question is a bit complicated, depending upon how much effort you want to invest into your testing system. My assumption is that at the moment, this test is designed to run synchronously, with no parallel execution. You can read more about paral…

    12 Apr 2016 23:26 UTC

  20. Parallel test case execution

    [quote=salma;8580]Thanks for the quick response. I deleted cache file and i rerun the test. Out of 16 tests it runs only 2 tests in parallel. For each test it creates a job my DB. I can see only 2 jobs instead of 16 jobs. [/quote] If you delete the cache file, this will happen. NCrunch needs t…

    12 Apr 2016 23:06 UTC