Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. exception when using Code Contracts

    I'm not sure if there's much that can be done about this. Code contracts wasn't written with the idea of continuous testing in mind. Mechanically the way it works is actually quite evil - it infers logic across output assemblies being in the same directory, which requires NCrunch to force itself…

    16 Nov 2011 22:01 UTC

  2. exception when using Code Contracts

    Excellent thanks - I'll take a look at the sample and will get back to you.

    14 Nov 2011 09:02 UTC

  3. Indicators in status bar

    Yes - this is coming :) It's the single most requested feature, and I want it too ... so it's coming!

    11 Nov 2011 08:32 UTC

  4. Issue with linking to libraries which aren't built by solution and aren't in GAC

    It looks as though the COM registration step for your output assembly is unable to deal with NCrunch's workspace build wiring. My guess would be that the UnmanagedRegistration step doesn't consider the same workflow for assembly resolution as other areas of MSBuild, or this may be something to do w…

    10 Nov 2011 21:36 UTC

  5. Unable to enable NCrunch for new install

    Hi John, I had a look through this one yesterday, and I've confirmed what seems to be causing it. Something in your development environment (VCS software perhaps?) is setting a read-only lock on the .crunchsolution.local.xml file. This causes the engine to fail when it attempts to write setti…

    10 Nov 2011 20:55 UTC

  6. exception when using Code Contracts

    Does it make any difference if you turn on the 'CopyReferencedAssembliesToWorkspace' option for your tests project?

    10 Nov 2011 20:52 UTC

  7. Unable to enable NCrunch for new install

    Good to hear :) Do let me know if it happens to you again.

    10 Nov 2011 04:16 UTC

  8. Impossible pass AND fail?

    Sorry for the delay in looking at this issue. I've confirmed that this is an NCrunch defect triggered by the use of the quotation __ syntax in MSpec. Basically, any MSpec tests that are named using this syntax will pass abnormally. A fix will be in the next NCrunch revision.

    05 Nov 2011 04:04 UTC

  9. Test projects with question marks

    Is it possible to build the failing project using MSBuild from the command line? This will help to identify whether the problem is being caused by complex or IDE dependent build configuration. Also - would you be able to submit a bug report after this load failure? I may be able to use this to yi…

    02 Nov 2011 02:51 UTC

  10. Test projects with question marks

    Hi Simon, Thanks for posting! The question marks indicate projects that cannot be built because a project they depend on is experiencing a build/load issue. Can you give me any more information about the assembly load errors you're experiencing? Is there anything different/unique about these r…

    31 Oct 2011 20:18 UTC

  11. TestCase attribute messing up NCrunch entirely

    Thanks for reporting this one. This is a problem caused by the instrumentation messing with named attribute parameters (i.e. the 'Result' named attribute parameter on TestCase), and is on the list of known issues to be fixed in a future version. If you're having trouble getting NCrunch to run qu…

    27 Oct 2011 13:12 UTC

  12. Alternatives for coverage indicators

    Thanks for the tip. This was something I looked at while the markers were in their very early stages, but it simply wasn't powerful enough to do what I needed it to do. There was also the issue that a huge range of plugins make use of their own glyphs, which would result in some interesting clashe…

    26 Oct 2011 16:43 UTC

  13. Any docs for NCrunch's AppDomain setup? (Ref running tests in Medium Trust from BoxBinary.com)

    Thanks, I'd like to hear how you get on with this. I've made a note to have a deeper look into making this possible with NCrunch, though it's hard to make any commitments on whether I'll be able to do so at this point in time :) Cheers, Remco

    25 Oct 2011 08:16 UTC

  14. Impossible pass AND fail?

    Hi, thanks for posting! I'll take a look at the code you've posted and will get back to you on the pass/fail issue. If you haven't already, would you be able to submit a bug report the next time you see a build failing when it isn't supposed to? This will provide a bit more information to help cre…

    24 Oct 2011 21:08 UTC

  15. Any docs for NCrunch's AppDomain setup? (Ref running tests in Medium Trust from BoxBinary.com)

    Cross appdomain/process tests do generally tend to suffer from the fact that NCrunch artificially wires together its test domains from files that can exist in separate locations. There is some [url=https://www.ncrunch.net/documentation/troubleshooting_test-and-runtime-related-issues]documentation…

    24 Oct 2011 21:08 UTC

  16. Issues with NUnit TestCaseSource

    I'm always on the lookout for good test solutions, so that would really be useful. Is there is a specific revision number/id that I can grab which is unfixed?

    21 Oct 2011 06:18 UTC

  17. Issues with NUnit TestCaseSource

    Sorry - I haven't had much exposure to TestCaseSource in the past, so it's a learning experience for me :) I've had a deeper look at how NUnit behaves in this situation and I'm afraid I can't give a simple solution to this problem. Essentially, NCrunch uses static metadata in order to locate t…

    20 Oct 2011 20:19 UTC

  18. Issues with NUnit TestCaseSource

    Hmmm... What kind of result would you normally expect from a name mismatch in the test case data?

    20 Oct 2011 08:19 UTC

  19. Issues with NUnit TestCaseSource

    Hi Jon, Thanks for posting. The problems you're describing are caused by NCrunch's inability to determine (and display) a difference between an inconclusive test result and a genuine failure. Right now (for the sake of simplicity) NCrunch doesn't have an 'inconclusive' status, so the UI simply …

    20 Oct 2011 06:49 UTC

  20. There is not enough space on the disk

    Hi Rudi - This is a good suggestion. Restricting the engine from building new workspaces when it needs them will reduce efficiency, but right now there isn't really any decent handling of situations where the drive runs out of space. The workspacing code was introduced before the discovery of u…

    20 Oct 2011 06:33 UTC