Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. NCRUNCH code coverage markers are all white after changing output path of project under test

    NCrunch struggles with [url=http://www.ncrunch.net/documentation/considerations-and-constraints_absolute-file-references]absolute file references[/url], because they usually cause code to break the isolation of the sandbox (workspaces) NCrunch constructs to build your code and execute your tests. …

  2. NCRUNCH code coverage markers are all white after changing output path of project under test

    Hi Dave, This approach cannot be made to work with NCrunch, because it relies on implicit behaviour describing the references between projects. NCrunch works by shadowing projects individually and separating them from their parent solution. In the workspaces that NCrunch constructs, the proje…

  3. MSpec and IAssemblyContext

    Yes. NCrunch does support IAssemblyContext, and I'm fairly certain it should also support ICleanupAfterEveryContextInAssembly, assuming that these features are provided by MSpec itself. NCrunch calls into MSpec and uses it as a provider to execute tests, so in theory any features implemented (ot…

  4. v2.4.0.2 - Build takes long time to process.

    Hi Jason - Aaron Job has a useful article that you might want to have a look at - [url=http://blog.gravypower.net/ncrunch-sharepoint-and-microsoft-fakes/]http://blog.gravypower.net/ncrunch-sharepoint-and-microsoft-fakes/[/url]. Basically, there is a way you can improve the performance of NCrun…

  5. Tests ignored with RegexTestSelector are being executed since upgrade to NCrunch 2

    Hi, Make sure that when making changes to configuration, you do so to the PROJECT.v2.ncrunchproject file. v1.48 used a different name for this configuration file - PROJECT.ncrunchproject NCrunch automatically migrates the configuration over to the V2 file when you first use V2 on a solution. …

  6. Test Icons not updating

    Hi Aaron - Thanks for sharing this issue. Can you confirm what the processing queue is showing you when this happens? Are there any tasks that have errored or are still marked as in progressed?

  7. Unicode issues

    Excellent. Thanks! :)

  8. Unicode issues

    Thanks. I've managed to reproduce this issue and have arranged a fixed build. Would you like to give it a try? [url=http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.9.msi]http://downloads.ncrunch.net/NCrunch_GridNodeServer_2.5.0.9.msi[/url] [url=http://downloads.ncrunch.net/NCrunch_Gr…

  9. v2.4.0.2 - Build takes long time to process.

    Hi, thanks for sharing this issue. The first thing to confirm is which project is responsible for the long build time. I recommend watching the processing queue when you make a change. Is there a particular project that takes a long time to build compared with others? If you have a project t…

  10. Avoiding huge workspaces

    Hi Jeremy, thanks for posting! You have a couple of options on how you can solve this issue. The first one is to reduce the number of workspaces by adjusting the engine's configuration. If you set the [url=http://www.ncrunch.net/documentation/reference_global-configuration_max-number-of-proce…

  11. Unicode issues

    The reason it will work with UI culture change in V1 is because the localised characters inside the exception strings have a tendency to cause the richedit view corruption. As soon as the UI culture is set to english, the characters are gone and the problem is gone with them. NCrunch should be a…

  12. Unicode issues

    Excellent - thanks for confirming that so quickly. I'll see if I can reproduce+fix - will let you know how it goes :)

  13. Unicode issues

    Can you guys confirm if the error navigation works when the test's current UI culture is set to English? I'm wondering if the localisation is messing with the exception parsing. The file links in the exception traces should be hyperlinks - there has been no change to the design (although much of t…

  14. Tests that use RazorEngine get odd exception when NCrunch is the runner.

    I regret that this problem cannot be solved within NCrunch. NCrunch defines the System.Runtime.CompilerServices.ExtensionAttribute to work around a compiler issue that results from needing to have backwards compatibility with older toolsets. Removing the declaration simply isn't possible without…

  15. mscorlib recursive resource lookup bug

    Thanks for sharing these details. I've managed to reproduce the issue and have identified its cause. Basically, there is a sequencing issue inside the engine that is causing it to double-queue some tests in certain situations. When the Web project is built, the engine automatically queues up an…

  16. NCrunch says lines aren't covered when they are

    Thanks for the report. I've had a good look through it, but as far as I can tell, the engine itself seems to be functioning normally. Do you, by chance, have a coverage filter set up on your engine mode? Does changing your current engine mode make any difference? I may need to ask for a code…

  17. Unicode issues

    Thanks for checking this out. I'm glad the issue is finally fixed. I'm really sorry but there's no way I can back port this to V1. It was a massive piece of work, and pushing it backwards would likely destabilise V1.

  18. Unicode issues

    Hi - I've finally managed to replace the RichEdit control that's been responsible for all of this mess. The new control is currently in a development build. I'm hoping to push it out with the next minor release of NCrunch (v2.5). Would you be interested in giving it a try? I'm very interest…

  19. mscorlib recursive resource lookup bug

    Would you be able to tell me a bit more about the structure of your solution? Do you have multiple test projects? What are the normal execution times for these 71 tests?

  20. mscorlib recursive resource lookup bug

    It's physically possible for tests to exist in the queue multiple times, but only if at least one of the instances is already being executed. Normally the pipliner should pull out any existing matching tests within the processing queue when it tries to add new ones. So if those first three sets …