Forum member

larsw

15 posts

Posts by larsw

  1. NCrunch gone missing from VS 2017

    Sorry for the late reply; the manual installation procedure worked! Thanks

  2. NCrunch gone missing from VS 2017

    Sorry for the late reply, No, I don't have a Remco Software sub folder - most of them have jibberish names like e2dp3you.qw2. I don't have any previews installed of VS2017 either.

  3. NCrunch gone missing from VS 2017

    Hi again, Sadly, no positive result. Is there a log or something that I can try to generate to help diagnose the problem?

  4. NCrunch gone missing from VS 2017

    Hi, I'm currently running VS 2017 15.6.5 and have NCrunch 3.14 installed, but all NCrunch functionality have disappeared from VS. I've tried to both reinstall NCrunch and reset my VS settings, but it seems that the NCrunch extension doesn't get loaded. Any tips on how to diagnose and fix th…

  5. Can't get FsCheck-based property tests to work with NCrunch

    I can confirm that it works OK with 2.19.0.4 :-) --larsw

  6. Can't get FsCheck-based property tests to work with NCrunch

    open System.Linq open FsCheck open FsCheck.Xunit open Xunit [<Fact>] let ``ignore me``() = () [<Property>] let ``goes red``(xs:int[]) = Enumerable.SequenceEqual(Array.rev (Array.rev xs), xs) Tested with NCrunch 2.16.0.3

  7. Can't get FsCheck-based property tests to work with NCrunch

    Hi, I can't get property-based tests created with FsCheck/FsCheck.xUnit to work. (using the latest versions of xUnit, FsCheck and FsCheck.xUnit). It won't work in neither C# or F#-based test projects. I've seen that other people have referred to a trick to include an empty [Fact]-based tes…

  8. How do I tell NCrunch to ignore a project?

    Hi, I've tried to set up a custom engine mode and use "does not have categroy" = "Foo" - but it does not ignore tests (MSTest) marked with TestCategory("Foo"). Is this a bug, or am I doing it wrong? --alrsw

  9. NCrunch not showing correct color "balls" in the gutter

    Hi again Remco, Had a discussion with a colleague where he points out an interesting thing; in the example code above, if I had not split the chained statement over multiple lines (e.g. I had inlined it all on one line) the ball would go green, even though not all of the code had been exerci…

  10. NCrunch not showing correct color "balls" in the gutter

    Hi again, After a deeper investigation, it seems that it is my test rig that left out enumerating an input in a mock (e.g. I forgot to do something about the input, I only returned a mocked return value). Fixing that and the balls turned green :) --larsw

  11. NCrunch not showing correct color "balls" in the gutter

    Hi again Remco, I'm fully aware of the deferred nature of executing chained LINQ expressions on enumerables - but what my screenshot does not show (sorry for that), is that the enumerable is in fact iterated over further down in the code file, so the code is in fact run (I've also verified it …

  12. NCrunch not showing correct color "balls" in the gutter

    Hi and happy NY, Re. [img=http://i.imgur.com/SLp1i.png]NCrunch color problem[/img] Shouldn't all the lines for this statement be colored as green? Regards, Lars Wilhelmsen

  13. Nested xUnit tests ignored

    Hi, I'm experiencing this as well. Will you fix this in a later release? cheers, --larsw

  14. problem with app.config file

    Hi again, Ok, thanks for the feedback. For other people struggling with ConfigurationElement-derived classes; It's possible to override the InitializeDefault() method and set the default values there instead of using the named property DefaultValue on the ConfigurationProperty attribute.…

  15. problem with app.config file

    Hi, I'm experiencing the same problem - any progress on Named Parameters used in attributes? --larsw