Forum member

mschinzpb

7 posts

Posts by mschinzpb

  1. ScenarioContext.Current.Pending() in SpecFlow tests

    Hey Remco, That all makes perfect sense, so for my use case the link you provided is going to be enough. Thank You for your fast reply, I really dig the speed of your forum replies!

  2. ScenarioContext.Current.Pending() in SpecFlow tests

    Hello, NUnit runners in Resharper as well as in team city seem to be smart enough to figure out a special return type from the spec flow framework when steps have not been implemented yet for certain features. These will be displayed as inconclusive (the same level as ignored) in the reports. The s…

  3. Dot in function name confuses test window

    When naming a function with a dot, the test overview window displays the test twice and reports a failure on the outer scope. An example is here: https://github.com/thinktainer/ncrunch-dot-in-functionname

  4. FSharp Xunit tests in module without traits stuck in pipeline

    Hey Remco, Thank You for your supporting this issue. I'm quite a bit embarrassed, as I have had a filter for category unit in my settings. Consider this as resolved, and please accept my apologies, Martin

  5. FSharp Xunit tests in module without traits stuck in pipeline

    Hey Remco, managed to squeeze 15 min today, so here is the repo with the sample: https://github.com/mschinz/xunitncrunchtest.git Let me know if you can reproduce there. Cheers, M

  6. FSharp Xunit tests in module without traits stuck in pipeline

    Hey Remco, Thanks for getting back about this. I'm a bit swamped atm, but I should have a demo solution with you after the weekend. To answer your question: Run all tests automatically default engine.

  7. FSharp Xunit tests in module without traits stuck in pipeline

    The problem I am seeing is that after upgrading to version 2.5.0.12 there is a change in behaviour in regards to running xunit facts. It used to be possible to just add the attribute to any method and this would be picked up by ncrunch and run fine. The behaviour I am seeing after the upgrade is th…