Forum member

Inker

17 posts

Posts by Inker

  1. Test Fails in nCrunch but not VS Test Runner

    Thank you for taking a look. As per your advice, I have raised an issue with MS on the coreFX repo here: https://github.com/dotnet/corefx/issues/32688 Perhaps we can learn something there. Thanks again

    08 Oct 2018 09:26 UTC

  2. Test Fails in nCrunch but not VS Test Runner

    The following test fails when run via nCrunch, but succeeds (as it should) when run via the VS Test Explorer: [Quote] using Xunit; using System.ComponentModel.DataAnnotations; using System.Collections.Generic; namespace ncrunchRepo { public class Class1 { [Fact] …

    08 Oct 2018 07:41 UTC

  3. xUnit 2 beta 5 - support for ITestOutputHelper

    Just posting this for others here, there is "quick" workaround for this for people who have updated to beta 5 and still want to use nCrunch: Basically you can use conditional compilation when under NCrunch to manipulate the Testclass so that it looks like ITestOutputHelper is a ClassFixture. The…

    29 Nov 2014 05:39 UTC

  4. xUnit 2 beta 5 - support for ITestOutputHelper

    Hi, xUnit recently (some would say finally) added proper [url=http://xunit.github.io/release-notes/2014-11-19.html]support for writing output/debug messages [/url]during testruns. This is done via a constructor injected object. Unsurprisingly nCrunch currently does not understand this, and sim…

    29 Nov 2014 04:55 UTC

  5. xUnit2 - IClassFixture ctor called twice

    I think there is another problem here. I'm helping a colleague investigate this. Short explanation: I'm doing some integration tests, and part of the fixture is to host a socket server. Now I applied the little work around with static to ensure Fixture initialization is only ran once, but the …

    16 Oct 2014 07:53 UTC

  6. xUnit2 - IClassFixture ctor called twice

    Thanks for the confirmation. I think for most people actual tests most likely won't fail because of this, ClassFixtures are mostly used to avoid doing expensive setup work more often than needed, so the only real world problem is that things run a bit slower. Cheers

    10 Oct 2014 10:03 UTC

  7. xUnit2 - IClassFixture ctor called twice

    Hi, When an xUnit2 Testclass uses a ClassFixture, the expectation/requirement is that only one Fixture instance is created for all tests contained within it. nCrunch (v2.10.0.4) consistently calls the constructor twice, even if only one Test is actually present (but it should only be called once…

    10 Oct 2014 07:30 UTC

  8. Xunit 2 quirks

    Interesting idea, but it's just a small thing I noticed while using NCrunch. Not worth the hassle/effort to to create all those subclasses. No worries.

    18 May 2014 01:55 UTC

  9. Xunit 2 quirks

    Just wanted to let you know that I haven't found anything else. I didn't get to do a ton of work this week, but when I did, ncrunch worked fine. So thanks, great job. BTW: can ncrunch group parametrized tests in the test window somehow? R# does this nice thing where you have one more hierarch…

    17 May 2014 12:59 UTC

  10. Xunit 2 quirks

    Hi, This fixed the null bug (as I'm sure you already know). I'll test NCrunch again against our real solution over the next couple of days. I'll report back if I find anything else. Cheers

    13 May 2014 01:49 UTC

  11. Xunit 2 quirks

    Wow, that was quick, didn't expect that! Unfotunatly I don't have much time today, but I did a quick spin. I'm happy to report that all issues except for one seem to have been resolved. Unfortunatly the remaining issue is with null parameters (which is exactly the one I have a lot of in my r…

    12 May 2014 10:02 UTC

  12. Xunit 2 quirks

    I see, that explains a lot, thanks for the quick reply. 1) Using it like this is a bit of a pain, mostly due to a lot of my Tests/Theories having null as one of their BadInput parameter. I wouldn't mind if the test went red, but it aborts all other tests from running and never really recovers. 2…

    11 May 2014 02:08 UTC

  13. Xunit 2 quirks

    Ok, another thing, if you have custom ITraitAttributes (and ITraitDiscoverer) NCrunch crashes too (I would be fine if it couldn't resolve the Trait or whatever, but it just crashes). An error occurred while analysing this project after it was built: System.Reflection.TargetInvocationException: Ex…

    10 May 2014 18:14 UTC

  14. Xunit 2 quirks

    Hi again, I had a random test suddenly not execute right in Ncrunch. So I investigated, and found a few more quirks. I'm using Xunit 2 2650 (the latest)). While investigating a found a few smalish things: [list=1][*]DisplayName shows only characters after the 23rd characeter (yes I know it…

    10 May 2014 12:31 UTC

  15. NCrunch Servernode doesn't build correctly (x64/x86)

    Thanks, well CC is baked really deep into this solution, I have been using CC for a long time now. The runtime rewriter isn't too bad, it actually works remarkably well for me in combination with nCrunch. I do static analysis on some selected assemblies with a separate build config (that also …

    09 May 2014 11:41 UTC

  16. NCrunch Servernode doesn't build correctly (x64/x86)

    [quote=Remco;5830] I'm looking at revising the wording in this message to make its purpose clearer. There's nothing you need to do to correct the problem, as there is actually no problem at all :) [/quote] I see, well that's good then. Perhaps only output those messages if Logging is set to Deta…

    09 May 2014 11:14 UTC

  17. NCrunch Servernode doesn't build correctly (x64/x86)

    Hi, I'm running into some weird issues when building my projects on an ncrunch server node. My solution is configured for AnyCpu (for all projects) My dev. machine is Win8.1 x64 pro, locally everything works fine. The server node is a Win8.1 x86 machine. I installed VS2013 and all required SDK…

    09 May 2014 05:26 UTC