Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I've had a look at this one in detail and I think it's because of read-only file locking problems. Are you using TFS?

  2. problem with app.config file

    Hi 4rchie, Thanks for posting. NCrunch should resolve your app.config file in the same way that other test runners do. Do you have any interesting build steps (i.e. a post build event?) that may be needed as part of preparing this config? Note that you can have a look at the workspace NCrunch …

  3. NullReferenceException building test project

    For anyone experiencing the above issue - I've had a look at this in detail and unfortunately it isn't an easy one to fix. One common cause of the issue stems from the use of COM interfaces in assemblies that NCrunch is attempting to instrument. If you are unlucky enough to have this problem, th…

  4. Set of Tests listed twice in the NCrunch Processing Queue

    Believe it or not, this is actually normal behaviour :) NCrunch will not remove tests from the queue while they are still executing, so if your tests were still running at the time your project was changed, then a new (often identical) task would be queued next to the old one. It's important t…

  5. System.UnauthorizedAccessException

    Thanks for reporting this one - I've had a couple of bug reports come through with a similar thing (I think one of them was yours). My best guess at the moment is that TFS is setting read-only locks on the files in your solution, and these read-only flags are being copied into the workspace by NCru…

  6. Unable to get NCrunch running due to absolute output paths

    Hi Daniel - Thanks for posting! Using an absolute output path isn't recommended as NCrunch needs to be able to build your solution without interference from other activities that may be going on in the output path (i.e. if you were running your application). My suggestion would be to change you…

  7. Incorrectly reporting MSpec test results and icons stay black

    Hi guys - thanks for posting. I think you're both experiencing different issues here. Simon, your issue sounds like an assembly resolution problem - perhaps related to how your project is referencing the MSpec assembly. Richard, I think your issue may be related to the version of MSpec you'…

  8. NCrunch with Moles

    I think that the general idea behind using DI for a situation like this would be to try to author the tests in a way that would allow you to comfortably test private methods through the public interface. DI proponents would argue that if the private method is complex enough to warrant being isolate…

  9. Always black dots

    Interesting - Is there any chance you'd be able to share the source code of your test project with me? I'd like to know why it didn't work for you in the smaller solution. Personally I use NUnit - not because I think it's necessarily better, but because I'm a bit old-school and when I first star…

  10. NUnit - Parameterised / Generic Test Fixtures show black indicators

    Hi, thanks for posting! Yes - NCrunch does not yet have full support for all of NUnit 2.5's features. Improvements in this area have been heavily requested (you'll probably see a number of similar posts in this forum), so it won't be far away :) Cheers, Remco

  11. Always black dots

    Thanks for sending the bug report. Looking through it, it seems that NCrunch isn't finding the tests at all ... are you sure they're showing in the tests window? Also, are you able to run tests using any other test runner (i.e. MSTest)?

  12. Always black dots

    I think there is something unusual happening under the hood - caused by some kind of environment issue most likely. Would you be able to submit a bug report using the NCrunch menu? This will send through a log file so I can see what's going on :)

  13. Always black dots

    Hi, thanks for posting! Are you trying out NCrunch in a test solution, or a real world one? Are your tests showing in the NCrunch tests window?

  14. What does the Risk/Progress window indicate?

    I've had a huge number of requests for a corner status indicator, so I think I'd be crazy not to put it in there at some stage. I have to admit I've been avoiding it so far because of the usual VS integration nightmares, though it definitely doesn't require much imagination to see how useful it cou…

  15. Issue with NUnit SetUpFixtureAttribute

    Actually don't worry about the bug report - this was pretty easy to reproduce. Fix will be in 1.35b.

  16. Unable to enable NCrunch for new install

    Hi John, I've had a good go at reproducing this problem but have had no luck in doing so. It looks to me as though there is some strange behaviour inside your VS process around the UI message queues. Do you ever experience any unusual behaviour in VS? I'm wondering if it may be worth trying …

  17. Issue with NUnit SetUpFixtureAttribute

    Ok - that's bad! Can you submit a bug report after this has happened to you? I'd like to take a look at the log file.

  18. InvalidProgramException on certain tests in solution

    Hi Brendan, This sounds like an instrumentation problem. There's been a few of these floating around. Usually this is caused by interesting/rare IL arrangements that get messed up when NCrunch processes an assembly after it's been built. You'll probably find that there's one method that is c…

  19. NCrunch 1.33b occasionally fails to build an assembly, but provides no error information

    I did get that one! Thanks for kicking it though. I've dropped it on my list of things to take a look at :)

  20. What does the Risk/Progress window indicate?

    Hi Peter, Thanks for posting! I wrote up a wiki page [url=https://www.ncrunch.net/documentation/concepts_risk-and-progress-bar]describing how this indicator works[/url]. I hope this should answer your questions :) Cheers, Remco