Forum member

abelb

155 posts

Posts by abelb

  1. Processing queue often empty, but *something* is running

    I often find myself wondering whether something is happening or not, esp. on those projects that are (extremely) slow at times. One way to find out what's going on is to go to the process queue, but that is mysteriously empty. Not always, but just in the case that there seems to be a delay with buil…

    18 Sep 2017 20:14 UTC

  2. NCrunch does not honor the max timeout and runs tests forever

    Some tests do not finish when run in parallel, or even synchronously, after one another, but they do finish when run independently. I have yet to find the source of this issue, which is why I'm turning to you for help. I am not certain whether this is caused by NCrunch or the complex settings of thi…

    18 Sep 2017 17:28 UTC

  3. Async build and build in general is a lot slower on VS 2017 Preview 4

    Just a follow-up, at this moment the speed is still relatively good. I disabled subtest testing (most of my tests include some two dozen variants for edge cases, so essentially, a run of one test runs 20 or so tests). Since most of the issues with the subtests have been resolved, I think it's enough…

    18 Sep 2017 17:19 UTC

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

    Yes, I do receive the notifications (which is why I saw this notification). Well, if you intend to update, you have my vote, I have grown accustomed to the ease of use of modern issue trackers, esp. the ones with easy responsive design. :).

    28 Aug 2017 06:47 UTC

  5. A comma in the test name appears with a backslash in the test report

    I agree, because then you'd create a discrepancy between how NUnit reports tests and classes. I'll see if I can raise it there as a bug report.

    28 Aug 2017 04:47 UTC

  6. A comma in the test name appears with a backslash in the test report

    And just in case Microsoft's compiler added it, this is what Reflector shows of the module (static class in C#): [img]https://i.imgur.com/cYL7wy1.png[/img]

    28 Aug 2017 04:02 UTC

  7. A comma in the test name appears with a backslash in the test report

    You were quick to reply! I just ran it in the NUnit GUI runner, latest beta version. It shows the same backslash there, so it is possibly a bug with NUnit itself.

    28 Aug 2017 03:58 UTC

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

    I was on a holiday, so I missed your update, but I can confirm that the fix works! I just installed it, I removed the work-around code, and no problems anymore. BTW: may I ask you how I can view all my topics in this forum? I had a hard time finding back my own reported topics or issues (and I'm …

    28 Aug 2017 03:55 UTC

  9. A comma in the test name appears with a backslash in the test report

    When you have a comma in a test module name it appears as an escaped (with backslash) comma in the test window. I.e.: [quote]Tests.QNameFunctions.fn:QName-against-empty\, for generic-comparison[/quote] Screenshot: [img]https://i.imgur.com/ryUWS83.png[/img] Not a big bug of any kind, just…

    28 Aug 2017 02:55 UTC

  10. Impacted tests are not always marked impacted and therefore not run

    I'm reported this "in general". I would assume this is a very complex feature and basically I'm wondering if there are known limitations. What I've seen over the past few years (and not always consistently) is: [list][*]Change in an inlined method that is used by a test does not always trigger Im…

    20 Aug 2017 07:40 UTC

  11. Async build and build in general is a lot slower on VS 2017 Preview 4

    Just a follow-up. It seems like performance is generally back to normal, with using 15.3.1.0 Preview 1 now (VS release from yesterday, and also using your latest version). Some things are sluggish, but they are not related anymore to NCrunch. [quote] [quote] Because currently, if I meanwhile c…

    20 Aug 2017 07:28 UTC

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

    Thanks for getting back at me and finding the issue so quickly! Something similar to your analysis was what I suspected, indeed.

    29 Jul 2017 13:59 UTC

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

    Here's a repro with C#. [code=csharp]using System.Collections.Generic; using NUnit.Framework; namespace SomeClassLib { class CSharpTests { static IEnumerable<string> source { get { var temp = System.IO.File.ReadAllLines("…

    28 Jul 2017 12:08 UTC

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

    [quote]Something over the course of your test execution is changing the current directory. It's possible that this is happening somewhere indirectly (i.e. inside NUnit), though if this were the case I'd expect it to be more consistent.[/quote] I don't think so. The tests run consistent in TeamCit…

    28 Jul 2017 11:46 UTC

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

    The set of tests have been stable for a few days. But what might have happened is that to create a repro for this report ([url=http://forum.ncrunch.net/yaf_postst2217_Current-dir-is-different-during-test-creation-than-during-test-execution.aspx]Current-dir-is-different-during-test-creation-than-…

    28 Jul 2017 11:35 UTC

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

    In this solution with 2450 tests, all tests succeed. however, after failing a few of them (to test the previous post on NCrunch using two "current directories"), and in general, while I am working and some tests are failing, then when the test window updates, the results are displayed incorrectly. …

    28 Jul 2017 00:04 UTC

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

    PS: using the workaround causes a different issue, NUnit itself can crash on it, esp. when used at init time, with the infamous SocketException as explained here: https://github.com/nunit/nunit/issues/1834. The fixes for that error don't always work. I have currently worked around that by adding a "…

    27 Jul 2017 18:18 UTC

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

    NCrunch, at least the most recent few versions, start from a current dir that is equal to its installation directory, and later seems during test execution to the actual execution dir as current dir. In many situations this wouldn't be a problem, but it becomes a problem when you are loading your…

    27 Jul 2017 18:12 UTC

  19. Async build and build in general is a lot slower on VS 2017 Preview 4

    > I think we need to address your build times. I have just installed P6, let's see if that changes anything. It may well be caused by VS, there have been several reports on performance with the new preview releases and some of those maybe resolved in P6. It's too late (or early) now, but I'll gi…

    27 Jul 2017 03:49 UTC

  20. Async build and build in general is a lot slower on VS 2017 Preview 4

    Hi, I have read this post (http://forum.ncrunch.net/yaf_postst2170_Visual-Studio-2017-Preview-15-3.aspx) which made me understand it is next to impossible to keep up with the quick release cycle of preview versions of Visual Studio. However, I decided to report this anyway in case it may help you…

    24 Jul 2017 15:50 UTC