Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Support for detecting test failing because of concurrent test problems

    Thanks for the suggestion. Dealing with randomly failing tests is definitely a source of frustration with NCrunch (it affects me too), and I've been trying to think of ways to sort this out. The difficulty in reconstructing a full test run and test set up state is that when executing tests concu…

  2. AnalysisTask ERROR

    Hi, Thanks for sharing this issue. It looks to be a clash between NCrunch's performance analysis instrumentation and a particular IL arrangement or CLR security feature that applies to this specific situation. To work around this issue, set the [url=http://www.ncrunch.net/documentation/refere…

  3. VS2008 crashes when debugging

    Hi Sam, NCrunch itself doesn't tinker with the debugger outside of its own debug actions (i.e. when you instruct it to debug or break into a test), so as you've mentioned that this only started after NCrunch was installed, this leads me to suspect one of the following: - The installation of NC…

  4. NCruch crashes (instead of failing) when test code contains stack overflows

    Brilliant! Thanks for sharing that link, I think that many people will find it helpful. I will also continue with trying to implement a proper solution. Cheers, Remco

  5. Avoid creation of the *.ncrunchsolution.* files

    Hi, In theory, these files don't need to exist until NCrunch is enabled for the solution that's been opened. Thanks for reporting this .. I'll see if I can get it fixed. Cheers, Remco

  6. NCruch crashes (instead of failing) when test code contains stack overflows

    Hi, thanks for posting! Yes - this is a current limitation within the NCrunch environment. NCrunch does not handle stack overflows. One of the motives behind moving to use hosted task environments with NCrunch was specifically to handle this issue. Unfortunately, the approach doesn't seem to…

  7. VS2008 crashes when debugging

    Hi Sam - Thanks for sharing this issue. Unfortunately, because of the number of components and variables involved, this may be a tough one to isolate. I'm wondering if you might be able to help by answering the following questions: - Does this happen only when you debug using NCrunch? Or wh…

  8. "Timeout of 60000 expired" is misleading

    Thanks for reporting this. I'll take a look and will see if a fix is possible. Cheers, Remco

  9. Nunit theory and autofixture problems

    Thanks for the reproduction - this made it much easier to identify the problem. Basically, this code is relying on dynamic test cases that make use of parameters of a random nature. NCrunch discovers and executes tests in separate physical steps, which means that the test names are not the same …

  10. Nunit theory and autofixture problems

    Hi, thanks for posting! Do you have a small code sample you can share that describes the structure of this test? Also, does changing the [url=http://www.ncrunch.net/documentation/reference_solution-configuration_framework-utilisation-types]framework utilisation type[/url] for NUnit make any di…

  11. Support for NUnit's ISolutionBuilder and TestSuite

    Awesome! Thanks for taking the time to provide the sample solutions .. this always makes life so much easier. I'm glad we could get this to work for you, and thanks for compliment! Cheers, Remco

  12. Support for NUnit's ISolutionBuilder and TestSuite

    I just stopped to have a think about the behaviour you're describing and what you've mentioned as being your approach to the test naming (i.e. using a generated number). I wonder if the generated number is causing the test names to get out of sync between the discovery of the tests and their exec…

  13. Support for NUnit's ISolutionBuilder and TestSuite

    Thanks. Do you see any obvious symptoms when they go red? I.e. is there any exception showing in the test output? Or any information in the Processing Queue window?

  14. Support for NUnit's ISolutionBuilder and TestSuite

    Hi Fabio - Great that it's working! I'm afraid the rules around FullName are fairly scattered between NCrunch and NUnit, so it isn't easy to put them together. My recommendation is to simply identify which patterns work for you deductively and then run with those. As the names are normally d…

  15. Support for NUnit's ISolutionBuilder and TestSuite

    Thanks Fabio. It looks as though this is now failing because NUnit is reporting two tests as existing with the same name (NUnit.Core.Test.TestName.FullName). This causes NCrunch to blow up, as it can't tell the tests apart when it feeds them into NUnit during runtime. I'm not sure if there's mu…

  16. Roadmap

    Hi, no news on this yet. Most likely it will be post V2.

  17. Support for NUnit's ISolutionBuilder and TestSuite

    Great to hear! If you can provide me with a demo of the 'Running' issue, I'll see if I can get to the core of this one too. Cheers, Remco

  18. Project slow to analyse and test

    The test execution behaviour of NCrunch vs Resharper is very, very different. Resharper constructs a single test process and application domain, then runs through ALL tests sequentially until its hits the bottom. NCrunch will break up all the tests into a number of different tasks, then each t…

  19. Realtime console output?

    Hi Darren - Thanks for the suggestion! There is a goal to move towards this. The main reason it hasn't been done yet is because is greatly increases the volume of internal messaging, slowing down the engine. I think that we would likely be able to invest more in getting here in a later versi…

  20. Support for Visual Studio's Profiler

    Hi Rodney, Sorry, after looking into this, it looks like a huge amount of work that would be hard to justify relative to the value of the feature. I don't see NCrunch going down this path. Cheers, Remco