Forum member

Remco NCrunch Developer

7586 posts

Posts by Remco

  1. Microsoft Visual Studio is Busy. Forever.

    [quote=akvochick;10889]I also captured a dump file that's about 200MB 7zip'd. If you want that, let me know where to send it.[/quote] It would be very useful to see this dump. Unfortunately I don't have anywhere for you to easily send such a large file. Do you have a dropbox account or anywhere…

    29 Jul 2017 22:19 UTC

  2. NUnit Testoutput does not contain Lines Written by TestContext.WriteLine()

    [quote=Grendil;10885]My QA team would like to move to NCrunch when the dev team does, but they write a lot of slow running BDD's. The initial feedback I'm getting is having to wait until execution completes before seeing any of the trace output would be a showstopper. They have tests that might hang…

    29 Jul 2017 22:13 UTC

  3. Current dir is different during test creation than during test execution

    Thanks for the code sample. I've managed to reproduce the problem as you've described it. The problem exists because although NCrunch sets the current directory prior to running tests, it doesn't do this prior to discovering them (in the Analysis Tasks). The TestCaseSource code always runs du…

    29 Jul 2017 00:08 UTC

  4. NUnit Testoutput does not contain Lines Written by TestContext.WriteLine()

    [quote=Grendil;10880]I believe in NUnit 3 we've been asked to switch to use NUnit.Framework.TestContext.Progress.WriteLine(message) to ensure messages remain associated with their test thread. As I recall Debug.WriteLine leads to problems under NUnit parallelization. I realize NCrunch doesn't need N…

    29 Jul 2017 00:01 UTC

  5. It still happens that sometimes a root node is marked red, while its children are all green

    Under NCrunch, the fixture is considered to be a test result in itself. The failure result of a fixture will always be from the last time the fixture was executed. So you could have one call into the fixture for one of its child tests that passes, then have a later call into the fixture for a chil…

    28 Jul 2017 23:52 UTC

  6. The connection has been closed error

    After you unzipped the files, did you select all files in the installation and choose to 'unblock' them using windows explorer? Windows has a frustrating security feature that tags files downloaded from the internet and prevents them from being accessed by software until you perform a manual acti…

    28 Jul 2017 23:15 UTC

  7. The connection has been closed error

    Hi, can you confirm which version of NCrunch you're running? This problem is caused by the NCrunch .NET Core task runner failing to initialise, which is usually caused by dependency related issues, such as critical Nuget packages that are missing. If you're not running NCrunch v3.10, you'll also…

    28 Jul 2017 11:15 UTC

  8. It still happens that sometimes a root node is marked red, while its children are all green

    Hi, Are you certain that the last run of the fixture wasn't a valid failure? There are some valid scenarios where this can happen. For example, if the fixture has (or had) a failed test that is not showing in the list of tests because it's been removed from the test suite or isn't set to show i…

    28 Jul 2017 05:06 UTC

  9. Current dir is different during test creation than during test execution

    On initialisation of a test process, NCrunch will always set the current directory as equal to the test project's build output directory. This will be why resetting the engine or rerunning a test makes the problem temporarily go away, because doing either of these things will make NCrunch drop exis…

    27 Jul 2017 23:17 UTC

  10. EngineHost question about releasing memory?

    NCrunch's enginehost contains almost all memory allocated by the engine. This is to try and keep as much of NCrunch away from devenv.exe as possible. As such, the enginehost contains an extensive code model of your entire solution and of its tests. The largest area of memory consumption is usua…

    27 Jul 2017 22:47 UTC

  11. Client priority for node servers

    Hi, Presently it isn't possible to control this. The grid nodes operate on a round-robin type request system that treats every connected client equally. The only way to ensure priority for the build server given NCrunch's current feature set would be to set aside nodes specifically for the serv…

    26 Jul 2017 23:13 UTC

  12. Even the simplest .NET Core project fails to build under NCrunch

    Hi Tim, Thanks for sharing this problem. It shouldn't be required to create a unit test library using a VS template to run NCrunch on a .NET Core project, simply referencing a test framework package should be enough. I'm not sure what went wrong here, but I do have a theory. The synchronisatio…

    26 Jul 2017 23:11 UTC

  13. Grid Server keeps disconnecting

    The strangeness of this behaviour suggests a possibility that something is going wrong deep down in the stack. If you haven't already, I'd suggest making sure all the Windows updates and .NET Framework updates have been installed on the grid nodes that are showing the problem. The exception you'v…

    26 Jul 2017 23:07 UTC

  14. Couple of issues with solution with .NET Core project

    Hi, thanks for posting. [quote=kierenj;10854]Hi - first a quick note, my installation was somehow corrupted and I ended up doing a manual install. However, the "devenv /setup /novstemplates" step did not work (gave "Operation could not be completed") unless I ran with administrator privileges. It…

    26 Jul 2017 22:56 UTC

  15. AutoFixture Warning Incorrect

    [quote=ewinhong;10852] Just so you are aware of what I found in my investigation: I loaded an issue with Autofixture. https://github.com/AutoFixture/AutoFixture/issues/786 This is the probable cause to my issue. [/quote] Ouch, that's nasty. It's good that they've confirmed a fix is comin…

    26 Jul 2017 22:40 UTC

  16. Different IL when running under NCrunch runner

    Hi, thanks for posting. Yes, NCrunch does definitely modify the IL of an assembly. It does itself use a modified version of Mono.Cecil to do this. The modifications include instrumentation that is used to track code coverage and performance data, among other things. It's possible to turn this …

    26 Jul 2017 09:08 UTC

  17. Grid Server keeps disconnecting

    [quote=MatthewSteeples;10834]Just discovered that this problem is only on 2 of our 3 active grid nodes. Trying to work out what's different about the one that works[/quote] Thanks, I'd be really interested to know this. I'm still at a bit of a loss here on how to reproduce this problem. Any ext…

    25 Jul 2017 23:11 UTC

  18. InvalidCastException when building assembly containing xunit 2.2 tests for a ASP.NET Core 2.0

    Hi, thanks for sharing this issue. See here for more information about this - [url=http://forum.ncrunch.net/yaf_postsm10835_AutoFixture-Warning-Incorrect.aspx#post10835]http://forum.ncrunch.net/yaf_postsm10835_AutoFixture-Warning-Incorrect.aspx#post10835[/url]. This is caused by there being an…

    25 Jul 2017 23:06 UTC

  19. 3.10.0.20 nCrunch.TaskRunner40.x64.exe flagged as virus in AVG

    Thanks Ben. I've also issued a request to AVG and received a response claiming that it was a problem in the scanner and they will fix it in a future version.

    25 Jul 2017 23:02 UTC

  20. AutoFixture Warning Incorrect

    [quote=ewinhong;10835] I tried removing references and it appears that there is an underlying issue that another external library (specflow) does not work. I believe xunit.abstraction was the xunit library that was not the current version. [/quote] It's possible that the version of SpecFlo…

    25 Jul 2017 23:01 UTC