Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. System.UnauthorizedAccessException

    Hi Rodney, NCrunch will spawn as many test and build runners as necessary to meet its parallel execution needs. This is controlled by the [url=http://www.ncrunch.net/documentation/reference_global-configuration_max-number-of-processing-threads]Max number of processing threads[/url] configuration…

  2. Coverage markers going missing partway through methods

    Hi, thanks for posting! This looks like a mapping/sync issue between the coverage information and the source file. A known bug exists in 1.44 (and prior) which can cause an issue like this. A fix is pending in the upcoming 1.45 release. Does a reset (disable/enable) of the engine fix up th…

  3. Coverage information for Automatic Properties

    Hi Bob, Thanks for posting! Auto-properties do not have debugging information generated for them by the compiler (i.e., you'll notice that you can't set breakpoints on them). Because of this, it's impossible for NCrunch to instrument them to retrieve code coverage information. NCrunch will…

  4. Xunit tests won't runwhen you have them in a nested class

    Hi, thanks for posting! This issue is caused by a limitation in the Gallio adapter NCrunch is using to discover Xunit tests. Basically, the adapter doesn't search nested Xunit classes for tests when using Static Analysis. A workaround is to set the '[url=http://www.ncrunch.net/documentation/ref…

  5. Code coverage indicators not appearing

    Hi Jon, Thanks for posting! Generally this problem stems from a bug in Visual Studio that corrupts the adornment layer used by NCrunch to display coverage markers. The bug can be triggered by VS package install/reinstall/uninstall actions, NCrunch upgrades, etc. Forcing Visual Studio to prope…

  6. NotImplementedException building one project

    Hi, This is an exception thrown by a library that NCrunch uses to perform its instrumentation. You somehow seem to have discovered a primitive type or IL sequence that this library hasn't been designed to handle. Can you tell me a bit more about this project? Is it written in C#? Are there …

  7. Does Ncrunch support Shim scope

    Hi, thanks for posting! Right now NCrunch doesn't yet support working with MS Fakes Shims, as these rely on a certain profiler to be loaded into the test environment. Support is [url=http://www.ncrunch.net/support/frameworks]currently planned for NCrunch Version 2[/url]. Cheers, Remco

  8. XBehave support

    I believe so :) Cheers, Remco

  9. Tests fail due to NCrunch internal conditions

    Nice work in figuring out what was happening. Running a parallel test runner on tests within an inherited codebase can often bring up obscure problems, and I'm glad you managed to find the root cause of the problem. It is particularly abnormal behaviour for a test to modify the config file of its …

  10. Content files not copied

    Thanks Peter! Because of the way NCrunch's build optimisations work, the 'Copy referenced assemblies to workspace' setting is needed for any project to copy assemblies or content files from a referenced project. This is behaviour by design - I'll quickly explain why this is the case. Let's ju…

  11. Supplement the Solution Explorer

    I find this idea particularly interesting because behind it there is a perspective of what automated tests should be, rather than what they actually are. By programming in any language, we're always bound by the constraints of this language. Learning to write automated tests in classes in separa…

  12. Stacktrace issues with code contracts on abstract methods

    After running through this again and making some modifications to the code, this suddenly started happening for me. I'm not sure why it wasn't surfacing before - perhaps there is an intermittent element? Anyway, after reproducing the issue, I can confirm that this is being caused by NCrunch's in…

  13. Code coverage flakiness

    Thanks for sharing the details about this. I've uncovered a mapping problem that can cause code coverage instability and code coverage loss in a similar way to what you describe. It occurs when an unopen code file is changed on disk before more work is done (and tests are run) using NCrunch in t…

  14. Code Coverage not respecting ExcludeFromCodeCoverage

    Hi, I can't give any firm plans on when this will be added. It may be in the 1.45 release, although I recommend not holding out for it. For the time being, try using [url=http://www.ncrunch.net/documentation/concepts_code-coverage-suppression]code coverage suppression[/url] instead. Cheers…

  15. Stacktrace issues with code contracts on abstract methods

    Thanks for sending through the solution. I've tested against it, but even when using the same version of NCrunch on this solution, the stacktrace still shows the correct references for me. This suggests that the problem is being triggered by something in your environment. Do you have access to …

  16. Supplement the Solution Explorer

    Hi John, Thanks for posting! I'm glad you're enjoying NCrunch! This is an interesting request and I'm wondering if I could drill a bit deeper into your use cases to find out what you are trying to achieve. My first thought is that if you find the need to use the Tests Window to create test…

  17. Stacktrace issues with code contracts on abstract methods

    Hi, thanks for posting! There's quite a lot going on here. I've tried to build a sample solution to reproduce the issue you've described above, although unfortunately the stack traces seem to be correct for me. Do you have an example solution I could get hold of? I'd like to look at this issue…

  18. Ncrunch Build Server integration

    Hi Tom, Having a system in the CI that behaves like NCrunch (with workspacing etc) to validate the work of other team members is something I admit I hadn't really considered, but I can definitely see much value in. I'll have a bit of a think about way that this could be met with the future devel…

  19. Tests fail due to NCrunch internal conditions

    Hi, thanks for posting! My guess would be that this problem is being caused by tests changing files at runtime (i.e. the .config file?). Something that may be worth trying is to run a build of your solution, then go to the bin\Debug directory of your test project(s), and mark ALL the output file…

  20. Run Tests As Administrator

    Hi Rodney - Thanks for the suggestion. UAC is often a problem during development. NCrunch itself is developed on a system with UAC enabled for just this reason - stuff tends to go haywire unexpectedly when it hasn't been fully tested with the extra security constraints. Unfortunately setti…