Forum member

Remco NCrunch Developer

7611 posts

Posts by Remco

  1. How can I check if the grid nodes are being used in a console test run?

    Hi Sam, The 'Applies To' setting controls where the reference to the grid node is stored. If the grid node is applied to the computer, it will be available for every solution you open on that computer. If it's applied to the solution, it will be available only for that solution. Basically this…

    24 Mar 2016 22:31 UTC

  2. Exception message column hides the critical part of the contents

    [quote=jnm236;8485] What's the risk? Worst case, the column is unusable. But the column wasn't available in the first place.[/quote] The data you're asking for isn't sitting in the UI where it can be easily obtained. It would need to be extracted and parsed at test runtime because it relies o…

    24 Mar 2016 22:13 UTC

  3. NUnit3 on distributed nodes or multiple threads unstable

    Thanks, that does narrow it down a bit. One unfortunate problem with having the issue appearing on the remote node is that the local bug report log file likely won't be able to tell us much of use. I think our best chance here would be to try and extract a log from the grid node when it fails. …

    23 Mar 2016 21:20 UTC

  4. How can I check if the grid nodes are being used in a console test run?

    Hi Sam, When the tests are run on a remote node, NCrunch always places a small message at the top of the log for the test telling you that it was executed on a remote node (along with the name of the node). Basically, when looking at the test results in the HTML log, this should be obvious. If …

    23 Mar 2016 21:14 UTC

  5. NUnit duplicate name warning without duplicate names

    Hi, thanks for sharing this issue. I've been in discussions with Charlie about changes to NUnit to better handle test identification between discovery and execution sessions. The consensus we've arrived at is that test cases making use of user defined type parameters are likely to continue to be…

    23 Mar 2016 21:01 UTC

  6. NUnit3 on distributed nodes or multiple threads unstable

    Thanks for the extra details. Would you be able to try working with the grid node disconnected for an hour to confirm 100% that it is the grid processing that is causing the problem? Also, can you confirm that you've also updated the grid node to 2.20? It would be great if you could submit a bu…

    23 Mar 2016 11:44 UTC

  7. NUnit3 on distributed nodes or multiple threads unstable

    Hi, Could you confirm whether this issue exists for you with the latest version of NCrunch (v2.20)? If so, do you notice any pattern as to which tests are causing this problem? Are you making use of any of NUnit3's parallelization features?

    23 Mar 2016 11:04 UTC

  8. NCrunch holds open handles to nuget package folders

    Hi Tim, Yes, sadly, this is normal behaviour. NCrunch needs to watch the directories of all dependencies to pick up on file system changes .. and this has a side-effect of locking them at root. Best practice is to always disable NCrunch when performing Nuget updates. This is because the way …

    22 Mar 2016 23:02 UTC

  9. Approvals and Distributed Processing

    [quote=JayBazuzi;8466] What I mean is: if I have my sources at C:\Projects\Foo on my local machine, that NCrunch puts that at C:\Projects\Foo on the node. [/quote] Oh, sorry .. I misunderstood. No, it doesn't do this. Such an approach wouldn't work outside a very narrow use case, as the nodes…

    22 Mar 2016 04:52 UTC

  10. Approvals and Distributed Processing

    [quote=JayBazuzi;8464]What if NCrunch recreated the original solution at the original path on the node? Since it would match the local machine, things would just work, right?[/quote] It already does :) NCrunch transfers the entire known solution to the grid node before it begins any processing…

    22 Mar 2016 03:11 UTC

  11. Exception message column hides the critical part of the contents

    I know it looks easy, but of course, there's always hidden bits. Trust me. It isn't as simple as you think it is. I would need to see solid demand for such a feature to warrant implementing it.

    21 Mar 2016 23:53 UTC

  12. Exception message column hides the critical part of the contents

    Hi, Thanks for the feedback on this. Unfortunately, this is now becoming much more complicated, as NCrunch now needs to pick apart exception data to try and construct this report. There are also edge cases to consider (i.e. what about aggregate exceptions that have their own physical type des…

    21 Mar 2016 21:46 UTC

  13. Runs distribution among NCrunch grid nodes

    Hi Sheryl - If the grid nodes have their capacity configured correctly, there shouldn't be a significant increase in time for the test execution, unless we're measuring very short periods of time (ms). You'll notice that in the Processing Queue, NCrunch will tend to group tests together in bat…

    21 Mar 2016 21:41 UTC

  14. Approvals and Distributed Processing

    Hi Max, We will need some feedback from Llewellyn on how to tackle these issues. As NCrunch is only a base runner calling into user code, it isn't able to change any of the behaviour you've just described (this is effectively handled further up the tool stack in Approvals itself). Being able to…

    21 Mar 2016 21:23 UTC

  15. Running tests manually while engine mode is in Impacted does not run all tests

    [quote=nrjohnstone;8453] Although, we have around 16000 tests across 100+ projects in our solution, and when you hit the "run all" button it has a noticable hang in VisualStudio now for around 10-15 seconds[/quote] Is this a new issue that's just appeared with 2.20? Can you confirm that its VS …

    21 Mar 2016 02:47 UTC

  16. Running tests manually while engine mode is in Impacted does not run all tests

    [quote=nrjohnstone;8451]actually... I can't test it as I've just gotten a message that our licence key is now 1 year out of date... that's a bit harsh isn't it? Not being able to manually run the tests reliably is a show stopper, should I really have to purchase a new licence for this Remco ??[/quot…

    21 Mar 2016 02:32 UTC

  17. Sharing test case source between tests

    v2.20 has just been released, including a fallback system for deriving the test name to remove internal ambiguity in situations like this. I'd suggest giving it a try and seeing if it solves this problem for you - [url=http://www.ncrunch.net/download]http://www.ncrunch.net/download[/url].

    21 Mar 2016 02:22 UTC

  18. Parameterized TestFixtures not fully recognized anymore with NUnit3

    For anyone interested, this issue has been resolved in the just released v2.20 - [url=http://www.ncrunch.net/download]http://www.ncrunch.net/download[/url].

    21 Mar 2016 02:17 UTC

  19. NCurnch does not recognize MSpec tests with Behavior when Behavior is defined in a separate assembly

    For anyone interested, this issue has been resolved in the just released v2.20 - [url=http://www.ncrunch.net/download]http://www.ncrunch.net/download[/url].

    21 Mar 2016 02:17 UTC

  20. Framework461

    For anyone interested, a release build containing the above fix (v2.20) has just been published - [url=http://www.ncrunch.net/download]http://www.ncrunch.net/download[/url].

    21 Mar 2016 02:16 UTC