Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Run a single Ignored test

    The testing approach you've described is one that I'm also using myself for NCrunch. I have a number of very heavy integration tests that I often find better to kick off manually, and the new configuration feature in 1.38b was designed to handle exactly this situation. The nice thing that you ha…

    01 Mar 2012 20:51 UTC

  2. Visual Studio GUI random freezes/unresponsiveness?

    Thanks for the tip about email notifications - I was wondering if this was an isolated issue, but it seems something isn't right with the mail server ... Can you share any more details about the solution your working in? I.e: * How large is your codebase? (approx lines of code would be great)…

    01 Mar 2012 20:43 UTC

  3. Is VS 11 Beta supported?

    An update on this one: I've given the beta a spin and confirmed that it doesn't find the NCrunch package on initialisation. I'm working on a build right now to properly extend support to the Dev 11 beta, hopefully I'll have it ready soon :)

    01 Mar 2012 00:36 UTC

  4. Issue with similar assembly names

    Thanks for sending that through. I'll take a look and will follow up if I need any more information :)

    29 Feb 2012 22:27 UTC

  5. Issue with similar assembly names

    Hi Mark, Thanks for reporting this issue. I've heard reports that NCrunch has some issues with projects that have the exact same name, but this one does sound new to me. Would you be able to submit a bug report using the NCrunch menu? The attached log file should hopefully give me the informa…

    29 Feb 2012 21:06 UTC

  6. Is VS 11 Beta supported?

    Hi, thanks for posting and I'm glad you're enjoying NCrunch! As the beta is only just released, I haven't yet had time to assess it to find gaps in the support. My expectation would be that NCrunch likely wouldn't work - though I can't yet tell you to what extent :) If you already have the De…

    29 Feb 2012 20:02 UTC

  7. Collapsed regions

    Hi, thanks for posting! I've had a few requests for this, and I'd like to do it - the problem is that it's insanely hard to do, and I still need to figure out how! I'll take a note of it for further thought. Thanks for your feedback.

    28 Feb 2012 20:41 UTC

  8. Run a single Ignored test

    Yes, this is the expected behaviour. The idea behind the 'ignore tests' option was to give people a progressive approach to implementing NCrunch on large complex projects. I expect that as time goes by and NCrunch becomes more sophisticated, this feature will become less used. When 1.38b is rel…

    28 Feb 2012 20:39 UTC

  9. Visual Studio GUI random freezes/unresponsiveness?

    Hi, thanks for posting! Yes - NCrunch is not supposed to block the UI thread. However, it does have a big impact on your overall system load, so if you're running several big heavy tests in the background (perhaps that do a large amount of I/O or interact with locally hosted databases), responsi…

    28 Feb 2012 20:26 UTC

  10. Reflection type loading error

    Hi Chris, This method is incompatible with the way NCrunch constructs its testing application domain. As a workaround, you can use the NCRUNCH compiler condition to make a call to Type.GetType instead. This would mean your code will use Type.GetType when executed by NCrunch, and Type.Reflection…

    28 Feb 2012 20:19 UTC

  11. v1.37b - Debug variables

    I've had a good look at this issue in depth, and it seems to be caused by a mismatch between the expectations of the VS debugger and the structure of the code under test. It appears that Visual Studio has been programmed with some kind of algorithm that infers the local variables of the 'yield re…

    28 Feb 2012 00:16 UTC

  12. Recursive code being edited can sometimes cause NCrunch workers to die horriffically.

    Yes! This is exactly the plan ;)

    27 Feb 2012 19:49 UTC

  13. Hard Drive usage going up

    Hi Greba, I've been having a tough time this weekend trying to reproduce the above problem and I'm wondering if you would be able to send me your simple solution? Also ... do you have a custom workspace base path configured? Thanks! Remco

    25 Feb 2012 23:15 UTC

  14. System.OutOfMemory Exception

    Hi, The stack trace above indicates an exception thrown while logging data from the build process. Logging of build output is a normal operation and I think it's more likely to be the piece of straw that's broken the camels back as far as your memory usage is concerned. There are a few things…

    24 Feb 2012 21:05 UTC

  15. "Risk/Progress" - distinction beetwen "failed this run" and "failed last run"

    Maybe an option is best. I'll have a think about it - there are some other plans coming together in this area and maybe I can solve it all at once :)

    24 Feb 2012 09:44 UTC

  16. Add Pin/Unpin tests on assembly level

    Thanks for the feedback :) The pinned test status is stored in the .cache file, which should be local to every user. The upcoming 1.38b release will add a few feature where engine modes can be customised (i.e. you can set criteria for which tests you want run automatically), and I have a feeling…

    24 Feb 2012 09:43 UTC

  17. "Build in progress" for extended periods?

    I've now successfully implemented a fix for this problem. It's a bit of a mean one. Right now I'm doing my best to wind up the changes on 1.38b so I can kick it out for a release earlier than planned ... it won't be as feature-heavy as I wanted, but at least it should solve this problem. Current …

    24 Feb 2012 09:37 UTC

  18. Consume Diskspace without clean up

    Hi, thanks for posting! NCrunch should normally clean up after itself, though there is a reported problem in 1.36b and 1.37b where some files are being left behind. I'm currently working on a fix. For the time being, I suggest changing your workspace base path to be somewhere that you can easil…

    24 Feb 2012 09:29 UTC

  19. Add Pin/Unpin tests on assembly level

    Thanks - yes, this is one that I've also been looking at! It's good to see the pinned tests getting some use. I've seen limited feedback on them up until today, and I was wondering if most people didn't know about them :)

    23 Feb 2012 20:09 UTC

  20. attempts to run tests in class not marked with [TestFixture]

    Hi John - This isn't something that was obvious to many people (including myself at the time actually), but with the introduction of NUnit 2.5, NUnit will now run tests without a [TestFixture] attribute being present on the test class. So what you've described is actually the intended behaviou…

    23 Feb 2012 20:08 UTC