Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

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

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

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

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

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

  6. 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)?

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

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

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

  10. Issue with NUnit SetUpFixtureAttribute

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

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

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

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

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

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

  16. Alternatives for coverage indicators

    It's alright :) I've had to point it out to a few people .. I think it's not in an obvious place... something that I intend to fix :)

  17. Alternatives for coverage indicators

    I like your agile story telling approach :) You can change the colour of the coverage markers in your global config settings. Right now you can't really turn off certain parts of the indicators ... I guess you could set the green markers to be the same as your background colour in VS - this wo…

  18. coverage on conditional statements

    In concept the marker should really be split down the middle (half green, half black). In practice this is much harder to do, as it means more granular instrumentation and a bigger performance hit on the code while it executes. I've noted this one down as something to look at, though I'm not sure …

  19. Unable to enable NCrunch for new install

    Hi John, Thanks for posting. I received a bug report about the same thing (perhaps from you?), and it looked like an internal problem. I'll see what I can do about sorting it out in the next release - Sorry that I don't yet have enough information to provide a workaround. Cheers, Remco

  20. NCrunch with StyleCop

    Hi Mike, Thanks for posting! NCrunch does its best to pick up file dependencies for projects, but there are still a few things it's missing .. I think that task binaries are one of them. When in doubt, just use the AdditionalFilesToInclude setting to make sure you have the dependencies included.…