Forum member

Micah71381

27 posts

Posts by Micah71381

  1. NCrunch 1.11 and XUnit 2

    All fixed, thanks!

    27 Dec 2014 07:36 UTC

  2. NCrunch 1.11 and XUnit 2

    The update appears to have fixed "break into a debugger" but it does not appear to have done anything for "show coverage for covering tests" or "show exception details". Note: I can hover my mouse over the red X and see partial exception details, but left clicking does not do anything despite wha…

    27 Dec 2014 05:37 UTC

  3. NCrunch 1.11 and XUnit 2

    Forgot to mention, I am running: Microsoft Visual Studio Professional 2013 Version 12.0.31101.00 Update 4 Microsoft .NET Framework Version 4.5.51650

    27 Dec 2014 01:26 UTC

  4. NCrunch 1.11 and XUnit 2

    1. Done. 2. Initially experienced it in a project I am working on. Switched over to a test solution/project (class library I keep handy for reproducing bugs for report) to reproduce the problem. Deleted all but one test in test project/solution and the problem persists. 3. Changing the Engine ho…

    27 Dec 2014 01:25 UTC

  5. NCrunch 1.11 and XUnit 2

    Show coverage for starting tests only also does not appear to work.

    27 Dec 2014 00:48 UTC

  6. NCrunch 1.11 and XUnit 2

    In hopes of being able to use NCrunch with xUnit v2 I downloaded NCrunch 1.11.0.10 today to try out the xUnit 2 support. Two big problems: 1. I am unable to debug tests. Right-click debugging from the NCrunch Tests window appears to do nothing and right clicking on a code coverage line and ch…

    27 Dec 2014 00:40 UTC

  7. Testing code that creates application domains.

    Sorry about the bug, I refactored out PathPointsAtFile before pushing it, just put in the parameters backwards (fixed now). I think writing my own GetAllAssemblyLocations is the right way for me to go. I agree, relying on it in the path doesn't work since me and my co-workers don't always have t…

    12 Dec 2014 21:02 UTC

  8. Testing code that creates application domains.

    The code in [url=https://github.com/Zoltu/NCrunch.StackOverflow.ReproCase]Zoltu/NCrunch.StackOverflow.ReproCase[/url] reproduces the issue. This worked in older versions of NCrunch (perhaps circa 2.4 or 2.6, hard to remember exactly) but does not work now. The reason for it is obvious and easy t…

    12 Dec 2014 17:24 UTC

  9. Testing code that creates application domains.

    A while back I wrote a library that did some AppDomain creation. I wrote tests for it and set them up to work with NCrunch by following the guide here: [url=http://www.ncrunch.net/documentation/troubleshooting_tests-that-build-their-own-appdomains]troubleshooting_tests-that-build-their-own-appdoma…

    12 Dec 2014 01:24 UTC

  10. Disabling JustMock Integration

    For anyone who removes it and can't remember what to set it back to, this is what it defaults to for me: C:\Program Files (x86)\Telerik\JustMock\Libraries\

    24 Oct 2014 21:02 UTC

  11. NCrunch and xUnit Theory Display

    I have an xUnit 1.9.2.1705 PropertyData Theory that contains a dozen or so test cases. NCrunch is able to run the theory and all of the tests, but they all show up as a single test in NCrunch, rather than a dozen or so separate tests. When I click on the test in the NCrunch Tests window, I see all…

    10 Sep 2014 17:06 UTC

  12. XUnit 2 tests are not picked up by NCrunch.

    Reproduction steps: [list=1][*]New Project > Class Library [*]Go through NCrunch setup (next, parallel, next, next, Let my tests run, next, finish) [*]Manage NuGet Packages... [*]Include Prerelease [*]Online > nuget.org [*]Search Online > xunit [*]Select xUnit.net > Install [*]Add using Xuni…

    12 Jul 2014 21:39 UTC

  13. Disabling JustMock Integration

    Figured it out, the trick was to set the Wow6432Node version of that key since Visual Studio and NCrunch TaskRunner run as 32-bit processes. The key can be found at HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Telerik\JustMock\BinaryPath. I did receive an error from Visual Studio when I launched it…

    23 Jun 2014 16:22 UTC

  14. Disabling JustMock Integration

    I set the registry key you mentioned (HKEY_LOCAL_MACHINE\SOFTWARE\Telerik\JustMock\BinaryPath) to an empty string but it appears NCrunch was still able to find Just Mock. I'm guessing it has some fallback code to check the default install path if the registry key isn't found (restarted VS after the…

    23 Jun 2014 16:18 UTC

  15. Disabling JustMock Integration

    TL;DR: * Having a code-injecting profiler attached slows down process cold-start times, even if the profiler doesn't inject any code. * I want a way to see which tests are still utilizing the Just Mock Profiled Mocking features and which are utilizing the regular mocking features. The long ve…

    21 Jun 2014 04:08 UTC

  16. Disabling JustMock Integration

    Visual Studio 2013 Just Mock 2014.1.1623.1 NCrunch 2.7.0.5 Currently, NCrunch is running with the Just Mock Profiler as seen here: http://snag.gy/04kqj.jpg The instructions found here ([url=http://www.telerik.com/help/justmock/integration-ncrunch.html]http://www.telerik.com/help/justmock/int…

    20 Jun 2014 16:14 UTC

  17. Improve Code Coverage Markers to be on par with Visual Studio 2013

    Visual Studio 2013 Ultimate's Code Coverage markers are more accurate than NCrunch's markers. In this simple example, you can see that NCrunch says that I have 100% code coverage of MyMethod while Visual Studio more correctly shows me that I have not covered all code paths. This encourages me to g…

    12 Mar 2014 00:36 UTC

  18. Test fails in NCrunch and passes in other runners.

    In my troubleshooting I was running the NCrunch instrumented assemblies under NUnit (I dug into NCrunch temp files for them). The key difference though was that NUnit is run on CLR 2 which doesn't have the GC changes you referred to, even if you install .NET 4.5. The GC changes to CLR 4 were shipp…

    28 Jan 2014 00:33 UTC

  19. Test fails in NCrunch and passes in other runners.

    Nevermind to the above question, it is because NUnit is build against .NET 3.5 which runs on the 2.0 CLR, so it doesn't have the change you are referring to (which is for the 4.0 CLR).

    28 Jan 2014 00:15 UTC

  20. Test fails in NCrunch and passes in other runners.

    Thanks for the quick reply! Do you know why the instrumented assembly runs green in NUnit but not NCrunch? I have NUnit GUI set to Framework 4.5 and I load the assembly that I believe NCrunch is using (found in %appdata%\..\Local\NCrunch\####\#\bin\MyAssembly.dll). When I look at that assembly …

    27 Jan 2014 23:50 UTC