Specflow: Azure Devops Plugin Path in Quotes

Created on 22 Apr 2021  Â·  4Comments  Â·  Source: SpecFlowOSS/SpecFlow

SpecFlow Version

3.7.38

Which test runner are you using?

SpecFlow+ Runner

Test Runner Version Number

3.7.38

.NET Implementation

.NET Core 3.1

Project Format of the SpecFlow project

Classic project format using <PackageReference> tags

.feature.cs files are generated using

SpecFlow.Tools.MsBuild.Generation NuGet package

Test Execution Method

TFS/VSTS/Azure DevOps – Task – PLEASE SPECIFY THE NAME OF THE TASK

SpecFlow Section in app.config or content of specflow.json

{
  "livingDocGenerator": {
    "enabled": true,
    "filePath": "{CurrentDirectory}\\TestExecution.json"
  }
}

Issue Description

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.

Steps to Reproduce

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

Link to Repro Project

_No response_

Bug SpecFlow+ easy high

All 4 comments

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.

Was this page helpful?
0 / 5 - 0 ratings