3.7.38
SpecFlow+ Runner
3.7.38
.NET Core 3.1
Classic project format using <PackageReference> tags
SpecFlow.Tools.MsBuild.Generation NuGet package
TFS/VSTS/Azure DevOps – Task – PLEASE SPECIFY THE NAME OF THE TASK
{
"livingDocGenerator": {
"enabled": true,
"filePath": "{CurrentDirectory}\\TestExecution.json"
}
}
The Azure Devops plugin for creating the Living Doc does not wrap the path to the Living Doc CLI dll in quotes. If you have a build agent installed on a machine that has spaces in the path, the command fails with the error:
Could not execute because the specified command or file was not found.
Possible reasons for this include:
* You misspelled a built-in dotnet command.
* You intended to execute a .NET Core program, but dotnet-C:\Azure does not exist.
* You intended to run a global tool, but a dotnet-prefixed executable with this name could not be found on the PATH.
Run the step on a build agent that is installed in a path that has quotes in it. For reference the one we're using that breaks is installed in:
C:\Azure Pipelines Agent
_No response_
I could reproduce this issue, it will be fixed in the next LivingDoc release.
@jlbeard84, we released a new version with the fix, please update, and try it! Hopefully we can close this issue.
This looks good on our end now, thanks for the quick turnaround!
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.