Forum member

sferencik

16 posts

Posts by sferencik

  1. display NUnit test description on failure

    Hi, yes, it's like extra info (in addition to the test name) about the test. The displaying on failure is (I believe) the main reason to prefer Description over a comment: /// bla bla [Test] public void TestBla() {} vs. [Test(Description = "bla bla")] public void TestBla() {} Thank…

    01 Aug 2013 13:13 UTC

  2. display NUnit test description on failure

    When an NUnit test has a description ([Test(Description = "...")]), it would be nice if this was displayed (probably in the output window) in the case of failure. R# does this, and I believe that so does NUnit plain. (Or is it displayed and I'm missing it?) Thanks, Samjavascript:__doPostBack(…

    31 Jul 2013 12:53 UTC

  3. Assemblies are being referenced from the build output directory of other projects in this solution

    Remco, Yes, it worked; thanks. This is probably the best-supported third-party product I've ever worked with. (That includes the forum, the email comms, and the online documentation.) Thanks, Sam

    17 Jul 2013 15:57 UTC

  4. Assemblies are being referenced from the build output directory of other projects in this solution

    I do have it in a file (the 800k one I mentioned) but it seems to be doing the right thing: Primary reference "Rhino.Mocks, Version=3.6.0.0, Culture=neutral, PublicKeyToken=0b3305902db7183f". Resolved file path is "c:\p4_ws\ThirdParty\vc8-win32\RhinoMocks-3.6.0\Rhino.Mocks.dll". R…

    17 Jul 2013 13:35 UTC

  5. Assemblies are being referenced from the build output directory of other projects in this solution

    I've upgraded from RhinoMocks 3.0.1 to RhinoMocks 3.6.0 and started getting this warning: [quote]QattHarnessTests: Assemblies are being referenced from the build output directory of other projects in this solution ... The following assembly references have triggered this warning: C:\p4_ws\fer…

    17 Jul 2013 12:25 UTC

  6. NUnit version

    Oops, I missed your response! The goal is that developers using NUnit via NCrunch have the same version of it as the ones using NUnit directly. In our case that means 2.5.10. It seems the best solution is to make both 2.6.2, rather than trying to make NCrunch use 2.5.10. Thanks, Sam

    17 Jul 2013 09:15 UTC

  7. NUnit version

    In [url=http://forum.ncrunch.net/yaf_postsm4066_disable-timeouts-when-debugging.aspx]this post[/url] you mentioned that NCrunch bundles NUnit. Can I configure NCrunch to use another version of NUnit, one that the rest of the team use?

    03 May 2013 07:46 UTC

  8. disable timeouts when debugging

    AFAIK, newer versions of NUnit disable the TimeoutAttribute when an interactive debugger is attached. http://xunit.codeplex.com/workitem/9823 https://bugs.launchpad.net/nunitv2/+bug/543517 Is this something that NCrunch should be able to do? Or does this depend on the NUnit that NCrunch uses?…

    25 Apr 2013 12:49 UTC

  9. thank you

    Hi Remco, Three weeks into running NCrunch and I'm hooked. Well done; it's a fantastic product. Thanks, Sam

    25 Apr 2013 12:47 UTC

  10. VS2008 crashes when debugging

    Thanks for the tips. I'm inclined to blame memory issues. I haven't had a crash for 2 days now. I will report back if/when I know more. Thanks, Sam

    24 Apr 2013 15:14 UTC

  11. VS2008 crashes when debugging

    Hi Remco, I use VS2008 with ReSharper 6.1 on Windows 7 64-bit. Intel Xeon X5650, 6 GB RAM. Admittedly, I went low on memory a couple of times over the past few days (the days when I had the crash). I'll try to watch out for a correlation. I have seen this happen when triggering the debugger fr…

    23 Apr 2013 14:29 UTC

  12. VS2008 crashes when debugging

    VS2008 sometimes crashes when I debug (NUnit) tests. This started happening after my recent installation of NCrunch, making NCrunch the prime suspect. The crash ("VS stopped working") happens as I trigger the debugging of the test. The debugger doesn't even get as far as the first line of the test. …

    22 Apr 2013 09:09 UTC

  13. "Timeout of 60000 expired" is misleading

    I have an NUnit test with a TimeoutAttribute. NCrunch correctly respects this time-out limit but still writes "Timeout of 60000 expired" when the time-out happens. The value of 60000 is incorrect as my time-out value is different. To reproduce, use [Timeout(1)] on an NUnit test. The test should t…

    22 Apr 2013 06:30 UTC

  14. Unable to find sn.exe for signing an instrumented assembly

    Yes, it did help. I copied HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v7.0\InstallationFolder (which contains the correct path to the SDK but is being ignored by NCrunch) to HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v7.0A\InstallationFo…

    12 Apr 2013 13:56 UTC

  15. Unable to find sn.exe for signing an instrumented assembly

    Hi Remco, Thanks for the reply. It did help. I have the following registry keys: A) HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0 B) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microsoft SDKs\Windows\v7.0 C) HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Microso…

    10 Apr 2013 13:22 UTC

  16. Unable to find sn.exe for signing an instrumented assembly

    Some of my projects are strong-signed and I'm getting the following error: NCrunch: If you are experiencing problems in getting this project to build, have a look at http://www.ncrunch.net/documentation/troubleshooting_project-build-issues#0 System.ApplicationException: [h]Unable to find sn.exe …

    04 Apr 2013 13:53 UTC