Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Tried creating a no-contract build configuration for ncrunch, ncrunch can't build anymore

    It looks to me like there is probably more than one thing that's gone wrong here. I hope you don't mind me asking a few questions to better identify what has happened: - Do your msbuild .proj files build successfully via the command line? (i.e. run MSBuild against the project files individually …

    04 Apr 2012 06:17 UTC

  2. NUnit Random Test Inputs Break Ignored

    You're welcome! It seems there is a bug in the dynamic analysis here. Thanks for letting me know.

    03 Apr 2012 22:25 UTC

  3. Instrument Output Assembly + PostBuildEvent

    Does it make any difference if you set your 'process pool size' to 0 in your NCrunch global configuration?

    03 Apr 2012 22:25 UTC

  4. NUnit Random Test Inputs Break Ignored

    Hi, thanks for posting! Do you notice any difference if you change the framework utilisation type for NUnit? (this can be found in your NCrunch solution configuration).

    03 Apr 2012 21:21 UTC

  5. Incorrect file extension: crunchsolution.cache instead of ncrunchsolution.cache

    This is correct. The file should be named using a similar convention to the other configuration files. However, because the file was so close to the convention when the configuration file names were changed, it was kept the same in order to save time. Renaming files can actually be a non trivial …

    03 Apr 2012 21:20 UTC

  6. Lines covered by only passing tests should be unmarked, not marked green

    Hi, thanks for posting! The usage of the green coverage markers is very much down to how you see your code and how you use NCrunch. I'm aware that some users prefer to set the green colour to the same as their editor background colour (so that they don't see the green markers). At this stage I …

    03 Apr 2012 21:18 UTC

  7. Skip unnecessary costly build steps (code analysis / code contracts static checker) when possible

    This makes sense. NCrunch will need to put out a warning letting people know that it won't be doing any code contracts checking though. Meanwhile, if you want to work around this, there is a blog post from someone that has disabled these build steps for their NCrunch - you may be able to make use …

    03 Apr 2012 21:15 UTC

  8. Instrument Output Assembly + PostBuildEvent

    Thanks for sending through the bug report. I'm currently working to reproduce the problem and will update you as soon as I have a workaround.

    03 Apr 2012 10:14 UTC

  9. Instrument Output Assembly + PostBuildEvent

    Hi Bernhard, Thanks for posting and I'm glad you're enjoying NCrunch! NCrunch only instruments an assembly AFTER the entire build process has finished (including all build events), so I'm wondering if the file lock may be the reverse of what you've described (SheepAOP holding a lock for a shor…

    02 Apr 2012 21:33 UTC

  10. Very High Memory Usage

    Thinking this through, I suspect that the processes running with high memory usage are likely to be the processes used to execute builds. I'll have a look to see if I can do anything about this, but meanwhile you can probably work around the issue by just punching the NCrunch 'reset' button every f…

    02 Apr 2012 21:30 UTC

  11. feature suggestion: discover/recognise NUnit's TestCase attributes

    Thanks, this helps a lot. I'll take a look :)

    02 Apr 2012 21:03 UTC

  12. Can't install VS2010 version

    Ok, this makes sense now. Microsoft are quite big on making sure that extensions such as NCrunch are not supported by VS Express - likely because it undermines their pricing structure. I'm afraid that there is nothing I can do to make NCrunch work for your version of Visual Studio short of encou…

    01 Apr 2012 20:59 UTC

  13. Very High Memory Usage

    Hi Mark, When reading your thoughts about lots of console output, the first thing that this brings to mind is that you may be experiencing problems with heap fragmentation. NCrunch tends to store the console output for tests that have just been executed - in large chunks of allocated memory (if …

    01 Apr 2012 20:56 UTC

  14. feature suggestion: discover/recognise NUnit's TestCase attributes

    Hi Tom - The behaviour of TestCase attributes is determined very much by the 'Framework utilisation type' you are using for NUnit. This is configurable in your NCrunch solution settings. If the utilisation type is set to 'StaticAnalysis', NCrunch will take a shortcut approach in its support f…

    01 Apr 2012 20:50 UTC

  15. Test category not working with MSTest

    Hi Tom, Thanks for reporting this. Would you be able to share a code sample for the above? I can't reproduce this problem for NUnit. Cheers, Remco

    01 Apr 2012 20:47 UTC

  16. Double Clicking Failed Test Results in Test Off Screen

    Hi Mark, Thanks for posting! NCrunch has two known limitations around the test navigation at the moment: 1. NCrunch doesn't yet track the locations of the method signatures in your codebase (only the lines they contain), so navigation is always to the first line of executable code within a me…

    31 Mar 2012 21:18 UTC

  17. NCrunch with external dependencies

    Thanks for the info - I'll have a bit of a think about this one, as it seems quite SQL-CE specific .. maybe I'll add a warning for when the project has a pre/post build step that NCrunch has deactivated.

    31 Mar 2012 21:15 UTC

  18. Pause builds when solution is building

    Hi Daniel, Thanks for the suggestion - this seems very sensible. I'll look into it! Cheers, Remco

    31 Mar 2012 02:05 UTC

  19. Share NCrunch configuration with team

    Hi David - There are some long term goals to better enable this sort of thing, though it requires quite a bit of investment .. so it's a bit far down my list at the moment. However, something you may find useful is that NCrunch stores the custom engine modes in the .ncrunchsolution file, which i…

    31 Mar 2012 02:04 UTC

  20. Click on NCrunch button when build fails

    Thanks :) I usually suggest for people to use the tests window instead of the processing queue wherever possible - as the processing queue can contain a lot of information (which causes the UI to slow down while it is open). The tests window is also better for getting a filtered view of the most re…

    31 Mar 2012 02:00 UTC