Skip to main content



  • Andreas Willich

    Sure it is possible to use SpecFlow+ LivingDoc with .NET Framework.

    Was there somewhere information, that made that not clear?

  • Ilija Ivanovski

    I am trying to setup pipeline in Azure DevOps (Restore + Build + VsTest task + SpecFlow+ Living Doc task). However, I could not succeed so far.
    I tried to get some instructions using the following documentation:
    and I noticed that I haven't considered so far the Step 3: Install the SpecFlow+ LivingDoc CLI, so then I visited the following documentation: , where it says that the CLI requires .NET Core. But when setting in Azure DevOps pipeline, is that step even requirement?
    If it's not required then my doubt is if the Visual Studio Test task returns the TestExecution.json correctly.

  • Andreas Willich

    Ah, we should remove the instructions from the old blog post. In the last months, the setup changed a little bit.

    You can find the up-to-date instructions for SpecFlow+ LivingDoc for Azure DevOps at

    The CLI is only needed when you are using the SpecFlow+ LivingDoc Generator. For SpecFlow+ LivingDoc for Azure DevOps, it is not needed.

  • Ilija Ivanovski

    Hi Andreas,

    I have managed to configure the pipeline following the link that you have sent to me, thank you.

    However, I have another issue perhaps you can help me again :D
    The test results are not synced in AzureDevOps LivingDoc even though I have crosschecked that the TestExecution.json file generated in the artifacts is correct. What could be the issue?

    p.s. In the Living Doc section I also noticed:
    "Warning: The given test results could not be fully matched to the feature files. Please make sure that the correct locations were defined."
    I have checked the locations of the feature files, they seem fine to me.

  • Viktor Nemes

    You see this warning because you have not used your Test Project Root as the Feature folder.

    If you want to see the Test Execution results, you have to provide the Test Project Root folder and not a subfolder (e.g. not the Features folder).

    We are going to update our documentation to make this more clear.

  • Ilija Ivanovski

    Yes, that solved my problem.
    Thank you Andreas and Viktor!

  • Gagneet Singh


    Facing a similar issue, but we have multiple VSTests@ tasks in the Azure pipeline build YAML file. SpecFlow picks up only the last run and not all the tasks report. Is it overwritten by the next task?

    What can be done to get a consolidated report across all the tasks?


  • Jonathan Pereira

    I'm facing the same issue as Gagneet Sigh, is there a solution to consolidate the VSTests Tasks?

  • Andreas Willich

    Gagneet Singh & Jonathan Pereira

    When you have multiple VSTest tasks, you need to adjust the filename which is used for the TestExecution.json. You can do that via specflow.json ( I would go with "TestExecution_{ProcessId}_{ThreadId}.json". This should be different for every execution of the VSTest task.

    The LivingDoc Task or the CLI accepts multiple TestExecution.jsons and is merging automatically (



Please sign in to leave a comment.

Powered by Zendesk