Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. Autofixture tests intermittently fail when using NCrunch

    [quote=royboy23;9230] Now I don't know where to look next. This could be an NCrunch, an NUnit, Autofixture or (though unlikely) even a Moq problem. Or it could be a combination of these. I was wondering if you have any idea how to proceed here.[/quote] Sorry. Unless you're able to provide me wi…

  2. NCrunch configuration wizards gets hidden under VS window

    Make sure you've removed the .ncrunchsolution file and the .ncrunchsolution.user file. With these gone, NCrunch should show the wizard automatically when you enable it on the solution. You can also trigger the wizard manually through the NCrunch menu.

  3. Can not run test on Grid Node Server

    [quote=Allnext;9225]Thanks a lot![/quote] Can you confirm that this was the problem? If so, I might take a look at how it's being handled.

  4. Autofixture tests intermittently fail when using NCrunch

    Hi Adrian, Thanks for sharing this problem! NCrunch won't run tests concurrently within the same process, but with parallel execution enabled it can run them in parallel across multiple processes. This means that if your code under test is interacting with something outside the test process, …

  5. NCrunch configuration wizards gets hidden under VS window

    I'm having trouble reproducing this problem. Are you running on VS2015? Do you have any other software on your machine that uses modal dialogs? If so, can you make it behave the same way the NCrunch modal dialogs are behaving for you? I'm wondering if this might be some kind of system-level pr…

  6. NCrunch configuration wizards gets hidden under VS window

    Hi, thanks for sharing this problem! What you've described is defective behaviour. Normally, the modal should stay on top of VS at all times. If you select VS or click any window in VS, the modal should be brought to the front. The modal should also show on the taskbar. Can you confirm whic…

  7. Can not run test on Grid Node Server

    Hi, thanks for sharing this issue. It looks to me as though you have a project in your solution that isn't fully loaded by NCrunch. Do you have any load errors showing in the NCrunch Tests Window?

  8. Memory Leak in Large Project

    Interesting. It's definitely a leak then, not simply high memory consumption. Let me know if you find a way to reproduce. It would be great if you could also keep an eye on your overall memory consumption across sessions to see if this increases over time. I'm wondering if somehow stale covera…

  9. Upgrading ncrunch console tool broke content files copy to output folder

    Hi, thanks for sharing this issue. I believe this is the same problem as described by Mike Ward here - [url=http://forum.ncrunch.net/yaf_postst1939_Haven-t-been-able-to-upgrade-since-2-23-2.aspx]http://forum.ncrunch.net/yaf_postst1939_Haven-t-been-able-to-upgrade-since-2-23-2.aspx[/url]. Recen…

  10. code coverage shows all black... but that isn't right...

    Thanks for the extra details. To me, it looks like NCrunch isn't detecting your tests. Can you check in the NCrunch Tests Window to see if you have any build errors showing? Do you have any tests at all showing in this window? Does NCrunch work for you if you try creating a new empty solution …

  11. Running my test through nCrunch fails to display value of variable in foreach loop

    Hi, thanks for sharing this issue. This problem is being caused by a debug scope issue when NCrunch instruments the assembly on disk. Basically, a method can contain multiple scopes (usually identified by the braces '{ }'). Each scope contains variables. If more than one scope within a method …

  12. Memory Leak in Large Project

    Hi, thanks for sharing this issue. 10GB is rather extreme, I haven't heard of the engine reaching so high before. Can you give me any more statistics on on your solution in terms of code count, number of tests, and code coverage density? Try deleting the NCrunch cache file to see if this re…

  13. All tests being ran on solution open (using engine mode 3)

    Hi, thanks for sharing this issue. Although I realise this is far from ideal, the problem you've described is by design. When NCrunch is offline, it isn't able to track changes that are made to your solution. To be safe, it assumes that all tests are impacted as soon as it initialises as it c…

  14. code coverage shows all black... but that isn't right...

    Does the test have a little '>' arrow marker on its first line? Do you get any coverage if you run the test manually? Are the tests listed correctly in your Tests Window? Do you have any data showing in the Metrics Tool Window? Which engine mode are you using? Can you confirm whether the…

  15. ncrunch server versioning... backward compat?

    Hi, The client and grid node software needs to be kept more or less in sync. Sometimes with smaller releases it isn't necessary to upgrade the grid node - this is indicated at the top of the release notes for each build. If your local machine can't use the grid node without upgrading the grid…

  16. code coverage shows all black... but that isn't right...

    Hi, thanks for sharing this issue. There are many reasons why the markers could be black. If you haven't already checked it, I do recommend having a look through this documentation page - [url=http://www.ncrunch.net/documentation/troubleshooting_missing-code-coverage]http://www.ncrunch.net/documen…

  17. Cecil failure during test project build

    [quote=brunellus;9195]This is something that started to appear with growth of the test project. For the record, we use VS 2015, the test library is for .NET Framework 4.5.2. There is no IL postprocessing, I think. There are lots of methods that throw NotSupported and few that throws NotImplemented.…

  18. Unable to run tests for Orleans

    My best guess here is that the problem is being caused by an implicit dependency between two assemblies that don't actually reference each other. For example, consider the following scenario: - You have two projects that share the same build output directory (project A and project B) - Neither …

  19. Insight on what qualifies as an "Impacted" test

    Hi, thanks for posting! NCrunch's impact detection is currently very basic. If a test covers a line of code in a changed file, the test is considered impacted. There are many edge cases where a test can be impacted by a change but not detected by the engine. Likewise the design is such that …

  20. Haven't been able to upgrade since 2.23.2

    Is it perhaps possible to build a sample solution that can fail to copy these files? If you can duplicate the structure in a sample, I should easily be able to troubleshoot it. If the sample code works as expected, then you may have something to test your current structure against to find the poin…