Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

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

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

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

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

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

  6. Stack overflow / infinite runtime of a test causes NCrunch 1.33b to fail

    I believe even without the parallel execution, NCrunch should be able to recover from a stack overflow ... but the queue will likely seize up on the batch of tests that contains the offender. If you carry on coding (after fixing the stack overflow), everything should just carry on as usual. In fac…

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

    Thanks again for the report. I've updated the build issues page on the wiki to include a note for it, as it seems others are also being affected by it.

  8. Make NCrunch more keyboard friendly

    Makes sense - I'll see what I can do :)

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

    It sounds to me like some of the change messages are being skipped somehow. If you have it happen to you, changing the file affected should cause it to resync and carry on. I'll see what I can do about trapping the issue and figuring out what's going on. The bug reporter connects via http to ap…

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

    Hi Wojtek, Thanks for posting! Yes - stack overflows are tough to deal with. I have a plan that should allow NCrunch to tackle this tidily, though it will take a bit of work and fortunately these issues are relatively rare in a developer's workday (unless your writing some manically recursive…

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

    Interesting .. Were you doing any kind of bulk operations at the time that it failed? For example - a rename or refactoring of some kind?

  12. Build failure with extern alias

    Hi Mike - Thanks! I just saw your bug report go through ... will take a look.

  13. What steps are necessary to get NCrunch work with more exotic CLR languages?

    Ok - looks like the library NCrunch is using for instrumentation doesn't recognise the assembly output from the exotic compiler. There probably isn't much I can do about this in the short term. Still, if this is an open source solution, would you be able to leave me a link to it? I'd like to ke…

  14. Problem with MSTest

    Hi Tom, Thanks for posting. This does look like a bug in NCrunch. Something with your test configuration is triggering an extra build step that most likely has an extra file dependency not tracked by NCrunch. Would you be able to submit a bug report using the NCrunch menu after this happens …

  15. Switch / Case statements appear with black icon in MSTest

    Yes - there is a known issue in this area. The instrumentation doesn't deal properly with switch statements. The issue also shows its face sometimes with inline delegates. It's on the list for a future fix. Thanks for the post! :)

  16. NCrunch 1.32b fails to build projects that depend on NCrunch-instrumented projects

    Still too early for me to say I'm afraid. You can pay me with bug reports for now! :)

  17. Tests are not recognized

    The major focus of 1.33b was on support for new test frameworks, so NUnit didn't get as much love this round. I have both the parameterized tests and combinatorial tests on the list for future work in this area, alongside NUnit theories :)

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

    The best thing you can do is use the 'Submit Bug Report' option in the NCrunch menu as soon as you see this issue occur. The bug report contains a detailed log file containing the workings of the engine up until the point where you submit it, so it's the single best weapon I have for reproducing …

  19. What steps are necessary to get NCrunch work with more exotic CLR languages?

    In theory, if the language supports MSBuild alongside .PDB output and doesn't do anything too crazy, then it should be possible for it to work with NCrunch. The list of supported languages on the front page of this site is actually only the languages that have been properly tested and I can be ce…

  20. Bug: Double clicking "N/A" in the Risk/Progress Pane crashes VS 2010

    For anyone interested, this issue should be fixed in the recently released 1.33b.