SpecFlowOSS / SpecFlow

#1 .NET BDD Framework. SpecFlow automates your testing & works with your existing code. Find Bugs before they happen. Behavior Driven Development helps developers, testers, and business representatives to get a better understanding of their collaboration
https://www.specflow.org/
Other
2.25k stars 754 forks source link

Editing feature file inside Azure DevOps results in error #2210

Closed godrose closed 3 years ago

godrose commented 3 years ago

SpecFlow Version:

Used Test Runner - Not applicable

Version number:

Project Format of the SpecFlow project

.feature.cs files are generated using

Visual Studio Version

Enable SpecFlowSingleFileGenerator Custom Tool option in Visual Studio extension settings - Not applicable

Are the latest Visual Studio updates installed?

.NET Framework:

Test Execution Method:

<SpecFlow> Section in app.config or content of specflow.json - Not applicable

Issue Description

Trying to edit a feature file using SpecFlow.Plus.LivingDoc displays an error

Steps to Reproduce

Go to LogoFX.Cli.Dotnet project. Try to edit a feature file

https://dev.azure.com/LogoFX/cli-dotnet/_apps/hub/techtalk.techtalk-specflow-plus.techtalk.specflow.plus.hub#/document/5bb3f19342d19b83be9e90b2afaadc21fe8d5209/feature/bf5df97f82ec8a9beb1755b0e3e20384/scenario/fb3abcc8d298f53b03bedadaa0c0477c

Expected: An editor opens Actual: Error is displayed:

https://techtalk.gallerycdn.vsassets.io/extensions/techtalk/techtalk-specflow-plus/0.6.465/1602161629439/src/Hubs/LogoFX/cli-dotnet/tree/feature/specflow-plus-pipeline/specs/LogoFX.Cli.Dotnet.Specs.Features/Service%20Generation.feature

Repro Project

https://dev.azure.com/LogoFX/cli-dotnet

alexandrafung commented 3 years ago

We will analyze the issue and let you know if it has been fixed.

godrose commented 3 years ago

@alexandrafung Hi, any update?

SabotageAndi commented 3 years ago

@godrose We found out that it has to do with GitHub. This worked in the past. Looks like something changed and we didn't notice it until now.

nemesv commented 3 years ago

@godrose The "Open Editor" feature was only intended to work when the source code is hosted in Azure Devops (git or TSVC), so in the latest release we hide the "Open Editor" button if the source code is not hosted in Azure Devops to avoid the confusion.

If you still need this feature please add it to our Feature Request list in our community forum: https://support.specflow.org/hc/en-us/community/topics/360000519178-Feature-Requests

github-actions[bot] commented 3 years ago

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.