Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Error StackTrace is not navigatable when instrumentation is off

    Hi Konstantin, I'm afraid not. The instrumentation contains an important step that rewrites the assembly's debug information so that source lines point back to the foreground solution (instead of the workspace). Without this step, NCrunch won't be able to reconcile the physical navigation entri…

  2. Grid node server "Not connected"

    Hi, thanks for posting. Can you confirm whether the NCrunch engine is running while you're doing this? NCrunch always disconnects from the nodes while the engine is disabled. It will attempt to connect when the engine is switched on.

  3. Problem with Fakes

    Thanks for sending through the bug report. The report contained a couple of very interesting errors: MS Fakes configuration file for assembly 'DSF.Service.CPS.TerminalId.Contrat' was not found. Module information will be unavailable in generated collection plan file MS Fakes configuration file…

  4. Using Catagories

    [quote=Aidan;7086]If I use the resync button then that should only run tests filtered by the Engine Mode selected right?[/quote] That's correct. If you have an active engine mode filter that should prevent these tests being run, and they are queued when you reset the engine, then it's a bug .. a…

  5. Problem with Fakes

    Ok - I'm wondering if you could check something for me. We need to know whether NCrunch is attempting to load the profiler by setting the COR_PROFILER environment variable. Can you open up a debug session into one of the failing tests? Once you're stopped on a line of code, open up the immediat…

  6. Using Catagories

    Hi, thanks for sharing this. There were problems in earlier versions of NCrunch where it was possible for tests to land in the queue when they were supposed to be excluded using the engine mode. Can you confirm which version you're running? The engine mode automatic execution filter will only…

  7. Problem with Fakes

    Hi, thanks for sharing this issue. Do you receive this exception on all the code that uses shims? Is there any chance you can provide me with the full exception message? The first thing to establish here is whether the profiler is being correctly loaded by NCrunch. Cheers, Remco

  8. NCrunch doesn't recognise new tests

    Thanks. The next time this starts desynchronising for you, I'm wondering if you would be able to check the following: - Can you right click on the project that is desynchronised (in the NCrunch Tests Window), then go to Advanced->Browse to workspace. This will allow you to inspect the workspace…

  9. NCrunch + NUnitAttribute "TestCaseSource"

    Hi, This is caused by a limitation in which tests identified by TestCaseSource need to have unique names when represented to NCrunch. Because the tests being generated in this instance have no way for NCrunch to tell them apart, it bundles them together. It is unfortunately impossible to fix …

  10. NCrunch doesn't recognise new tests

    Thanks for the bug report and the extra details. I'm wondering if you could confirm something for me. Do any of the projects in your solution have their output assemblies installed in the GAC? For example, for sharepoint integration testing?

  11. Building C++/CLI project is very slow

    [quote=openshac;7071]I tried specifying the condition you mentioned however it didn't change the behaviour. And it would also mean the additional include directories would get omitted if [b]$(NCrunch) == '1'[/b], but I guess that modification was just to test things.[/quote] Yes. Sorry ... it's …

  12. Thread Aborted and Timeout of 60000 Expired Exceptions

    Hi, thanks for sharing this. This is behaviour as designed. NCrunch enforces a default timeout for all tests to prevent them from hanging up the pipeline. It's very configurable - [url=http://www.ncrunch.net/documentation/concepts_test-timeouts]see here for more information[/url].

  13. How to clear failed tests/ i.e. remove the last build status?

    [quote=dariusdamalakas;7067]Thanks for the tip, that will do! If I may to suggest, then i'd actually do a full cleanup when i resync/initialize NCrunch, instead of remembering state[/quote] Sorry - I'm not sure if you're suggesting NCrunch should behave this way ... I'll answer as though y…

  14. How to clear failed tests/ i.e. remove the last build status?

    Hi, This option doesn't exist at the moment. The quickest and easiest way to do this is to just change the name of the tests, then change them back again. NCrunch will discard all state and treat them as new tests. If there are heaps of tests and it isn't sensible to rename them individually…

  15. Building C++/CLI project is very slow

    Interesting ... It must be the case that MSBuild is automatically resolving these dependencies during the NCrunch load, then reporting them to NCrunch as being files inside the project. If this is indeed the case, it may be possible to work around this by hiding them from the NCrunch load. Insid…

  16. Some projects show "Not built"

    The relative reference to 'Program Files' needs to be corrected - this likely won't work properly inside the NCrunch workspace and it's also dangerous to have this in case the project files are ever moved or checked out to a different location. References to program files SDKs should be specified a…

  17. Building C++/CLI project is very slow

    [quote=openshac;7056]When you say "referencing the library files" what exactly do you mean? The Boost header files are currently "referenced" from the C++/CLI files using [b]#include[/b] statements. [/quote] Sorry, I often have my head stuck in C# land :) It may be enough to simply adjust …

  18. Some projects show "Not built"

    Hi, thanks for sharing this issue. The most likely reason I can think that a project would be stuck in 'Not built' status is if a dependency was unable to build. What can you tell me about the projects in this solution? Is there a pattern as to which projects NCrunch isn't detecting? Have an…

  19. Building C++/CLI project is very slow

    This makes sense. Copying 38,000 files into each workspace will make a difference in build time. I can suggest a solution to this, although it isn't a tidy one ... basically it involves referencing the library files using absolute file paths and removing them from the 'Additional files to includ…

  20. Building C++/CLI project is very slow

    Hi, thanks for sharing this issue. The first thing I'd try is turning off the 'Instrument output assembly' setting for this project. C++ projects aren't properly supported for NCrunch instrumentation anyway, so this isn't likely to have any downside .. and it will reduce the amount of processing…