Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Ncrunch died on me

    Good to hear :) Don't worry too much about the wider adoption issue. I'll include a fix in the 1.34b release due out for release within the next week.

  2. Ncrunch died on me

    Hi Darren, I had a look at the log file you sent through, and it looks like your rebuilt system has some interesting security configuration. NCrunch is falling over while trying to store data in C:\ProgramData. Does the account you're using have access to this area? If not, try running VS as a…

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

    1.33b introduced quite a critical change in the way that assembly references are resolved - Over the last week, I've noticed a number of problems in here myself... they are admittedly particularly frustrating, though so far I've only seen them when CopyReferencedAssembliesToWorkspace is used. Do yo…

  4. Icons are showing black

    Ok - I think we've nailed this one down then. 1.33b seems to have an issue with analysing tests that inherit cross-assembly. I've implemented a fix that will be out in the next revision. Thanks for your help :)

  5. Icons are showing black

    Is the parent or grand-parent test class for your database framework residing in a different project/assembly to the derived class holding the [TestFixture] attribute? I've done some tinkering here and this does seem to cause NCrunch to not find the inherited test.

  6. References from early adopters?

    I've tweeted out a request to see if anyone is keen to help post a few references here. Hopefully we'll get some posts soon - otherwise I'm going to feel very disappointed :) I'm not sure if it counts to have a reference from the author of the tool, but a commercial project I'm working on has li…

  7. Icons are showing black

    Thanks - I just saw the report come through. Nice amount of detail :) Can you give me a bit more information about the workings of your MakeAssertions() method? Does it use any features that are specific to NUnit 2.5? As this method doesn't use a [Test] attribute, how are you currently exposin…

  8. Build runner does not support inline dynamics e.g. var myObject = blah.MethodWhichReturnsDynamic()

    Hi Alex, I've been trying today to reproduce this issue so I can properly fix it, though it seems to have mysteriously disappeared for me. I'm wondering if you have any other way to reproduce it in v1.33b? I've tried using the code you've described above and also through manipulating a few thi…

  9. Icons are showing black

    Hi Daley, The first thing that comes to mind when I see a situation like this is that there is something about your larger solution that's causing NCrunch to throw an exception. Would you be able to submit a bug report using the NCrunch menu after this happens to you? This can help me to figu…

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

    I wonder if there are some characteristics to your solution that make this issue hit you particularly hard :) Is it a large solution? What is the rough specification of the system you're using? High-spec or slow-spec CPU?

  11. NCrunch Review in dotnetpro Magazine

    Hi Manuel - I saw a tweet about this one and got very excited about it. I'll be watching network traffic from Germany with great interest :) Thanks a whole lot for your support on the publicity front! Cheers, Remco

  12. unable to use configuration element with default values

    Thanks, this helps narrow things down a great deal. This result tells me that the problem is being caused by instrumentation removing some of the metadata that your tests are relying on. I'll see what I can do about implementing a fix. Sorry for the trouble.

  13. Tests in a separate solution

    I'm glad it's started working ... a little concerned about how it didn't work the first time.. The black dots identify lines that are not covered by tests. The issue you're seeing with the constructor may be because of a known problem where some IL configurations seem to prevent NCrunch from p…

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

    That's definitely not right. Have you had any luck in opening up your firewall for the bug reporter? If you manage to capture something like that with the reporter, the log file will be really useful.

  15. Tests in a separate solution

    When you created the new solution, did any of the projects contain project references to other projects that aren't in the solution? This tends to cause an interesting build situation that NCrunch can't handle at the moment. Still, I'd really like to have a look at the results of the engine when t…

  16. unable to use configuration element with default values

    Interesting ... do you still have this problem if you turn off instrumentation in the project file under test? (Note that turning off instrumentation will also stop NCrunch from finding tests in the built assembly, so you'll need to have your tests in a different project to try this).

  17. Tests in a separate solution

    This is an interesting arrangement ... Do you run your unit tests outside of Visual Studio? The best suggestion I can offer would be to add a specialised solution that contains both the testing projects and the projects under test. The current design of NCrunch doesn't allow real-time operation …

  18. Tests are not recognized

    Hi Blaz, Thanks for reporting this. Right now NCrunch has only limited support for many of NUnit 2.5's features. I'll put it on the list of things to address. Cheers, Remco

  19. Allow "Debug" runner mode by telling VS to attach to the test runner

    Funny you should suggest this ... as it exactly matches what I have planned for debugging support in future (the one-click break into a debug session thing that is, not the rewriting of VS tooltips - that's really hard!). I'm glad you really like the tool! No shares are up for grabs I'm afraid, b…

  20. NCrunch 1.33b crashes when test method contains neverending recursion

    You're right in that dealing with stack overflows isn't simple. A stack overflow will rip through any exception trap and will religiously take down the process executing the offending code. The key issue is that when the process runs out of stack, it often works its way into an invalid state. The…