Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
    Christian Johansen
    @cjjohansen_twitter
    What I mean is XML format that xbehave markdown report can parse.
    Adam Ralph
    @adamralph
    @cjjohansen_twitter right, so at the moment, that would be the XML that xunit.console.exe produces
    if you can match that, then xBehaveMarkdownReport should work just fine
    Christian Johansen
    @cjjohansen_twitter
    I downgraded to v. 2.3.0 to use dotnet xunit. That works.
    But I'm still curious to how I could make dotnet test produce the same xml output. Maybe I should ask in xunit forum .
    Thx @adamralph
    Adam Ralph
    @adamralph
    you're welcome @cjjohansen_twitter
    ben-foster-cko
    @ben-foster-cko
    Hi all, trying out XBehave for the first time as a potential replacement for NSpec
    How can I get the BDD output when running dotnet test?
    It must be possible as the VS Code runner is doing it. However, even with that I don't get the name of the steps in the output:
    image.png
    Adam Ralph
    @adamralph
    @ben-foster-cko in all cases, all the various runners see are xunit tests, one for each step. Those tests are contained with xunit test cases, one for each scenario. Some runners, like ReSharper, respect that
    Others don't.
    The vs test explorer kind of respects it. It shows the test cases in the tree vir
    Sorry, on phonr
    ben-foster-cko
    @ben-foster-cko
    since I've never dived this deep into test runners/XUnit before, are you able to point me in the right direction/source code
    just having this output with dotnet test would be enough to be honest
    I don't really care about the VS tooling
    Adam Ralph
    @adamralph
    dotnet test is rather primitive in this respect
    ben-foster-cko
    @ben-foster-cko
    what I get with NSpec for example (has its own runner):
    Adam Ralph
    @adamralph
    But you may have some mileage with
    ben-foster-cko
    @ben-foster-cko
    describe AuthorizationProcessor
  when processing
    given authorization request is null
      throws ArgumentNullException (6ms)
    given acquirers is null
      throws ArgumentNullException (0ms)
    given no acquirers are provided
      throws ArgumentException (0ms)
    given one acquirer is provided
      and the acquirer declines the payment
        is not approved (2ms)
      and the acquirer throws
        is not approved (0ms)
      and the acquirer approves the payment
        is approved (0ms)
    given multiple acquirers are provided
      and the first acquirer approves the payment
        is does not cascade (0ms)
      and the first acquirer declines the payment
        and the response code can not be cascaded
          is does not cascade (0ms)
        and the response code can be cascaded
          cascades to the next acquirer (0ms)
    Adam Ralph
    @adamralph
    dotnet test - -verbosity=normal
    Yeah, xbehave has no runner. It just runs with anything that can run xunit. I guess that's an advantage in some ways but disadvantage in others
    ben-foster-cko
    @ben-foster-cko
    do you know where the source code is for the XUnit runner that is ultimately executed by dotnet test?
    is it https://github.com/xunit/xunit/tree/master/src/xunit.console?
    Adam Ralph
    @adamralph
    No, that is the xunit console exe I think.
    Farhad Taran
    @ftaran
    Hello, is there anyway to generate a text report automatically whenever the tests are run locally by devs?
    Adam Ralph
    @adamralph
    @ftaran take a look at https://github.com/appccelerate/xBehaveMarkdownReport