Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. 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…

  2. 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.

  3. 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…

  4. 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…

  5. 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…

  6. 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…

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

    Yes! This is exactly the plan ;)

  8. 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

  9. 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…

  10. "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 :)

  11. 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…

  12. "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 …

  13. 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…

  14. 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 :)

  15. 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…

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

    Yes - this is true. One way I'm thinking about trying to make this more obvious would be to have a different shade of red for situations where the number contains failing tests that are not current. Do you think this would work for you? Or do you have any other ideas?

  17. Add Pin/Unpin tests on assembly level

    This seems like a reasonable request - and it would work well with the tests window structure. I'll see what I can do.

  18. Cannot build VB.Net projects. Get error vbc, NCRUNCH; ^^ ^^ ' is not valid: Character is not valid.

    Hi Graham, Thanks for posting and I'm glad you like the tool :) I've done some more digging and I've managed to find a workaround for using DefineConstants on VB.NET projects. Depending upon the number of projects in your solution, there may be some effort involved. Basically, NCrunch is m…

  19. Results/ Coverage reporting

    Thanks for posting your thoughts on this. The ability to report code coverage stats is one of the most single requested features on this forum, so you can bet it will be happening in a future release :)

  20. "Build in progress" for extended periods?

    I was originally thinking to push 1.38b out around the middle of next month, but I may need to bring the release forward as this is quite a serious issue. I'll keep you posted.