Skip to main content

Azure DevOps SpecFlow+LivingDoc publish report from TestExecution.json




  • Andreas Willich

    Can you post the livingdoc cli call that runs in your docker container? Because the TestExecution.json is generated by the LivingDoc SpecFlow plugin and not the cli tool. So I am a little bit unsure what is really happening.

  • Domenico Del Vecchio

    Hi Andreas.

    These are the steps we run inside the container.

    TestExecution.json is generated (in fact, the html report can be generated in the same way) and then it is copied outside the container with a COPY command.

    We can see the generated TestExecution.json file on the build agent, so it is available for the Azure DevOps pipeline task.

    RUN dotnet add package SpecFlow.Plus.LivingDocPlugin

    RUN dotnet build "<our project file>" -c Release -o /app/build

    # run tests on docker build

    RUN dotnet test

    #SpecFlow LivingDoc generation

    RUN dotnet tool install --tool-path ~/bin SpecFlow.Plus.LivingDoc.CLI

    RUN ~/bin/livingdoc feature-folder "Features" --output /src/livingdoc/TestExecution.json
  • Daniel Melao


    I'm facing a similar situation. Can you confirm it's possible to generate the TestExecution.json (inside the container where tests run) and then export it so that it's available in the Azure DevOps pipeline?

    This way the json is not being generated by the plugin, but by the living doc cli inside the container. So I'm not sure this will work. At the moment I'm getting the same error described in the initial post (TargetInvocationException and NullReferenceException).



  • Andreas Willich

    Domenico Del Vecchio & Daniel Melao

    The TestExecution.json is generated by the SpecFlow.Plus.LivingDocPlugin NuGet package. And only by that.

    It is never generated by the LivingDoc CLI tool.

    The TestExecution.json is always an input for the livingdoc CLI. The parameter for this is "-t". You can't use it as output.

    Also the folder has to be the root folder of your project. Not the folder of your feature files. If this is not correct, we don't can match the test results to the correct scenario.


    What you want is to generate a FeatureData.json, that can then be used in the Azure DevOps task.

    The parameter for it is --output-type JSON. This json-file includes everything. You can copy it then out of the container.

  • Domenico Del Vecchio

    Thanks Andreas. It is working now.

  • Andreas Willich



Please sign in to leave a comment.

Powered by Zendesk