specflowoss/specflow.vs issues and pull requests

#174 - Test Discovery Fails: Could not load file or assembly 'System.Runtime, Version=8.0.0.0

Issue - State: open - Opened by DDSGooch 9 days ago - 2 comments

#173 - Parameters are shown properly, even though the formatting is not correct

Issue - State: open - Opened by SebastianStehle 3 months ago

#172 - Warning: AndDiscoveryProviderSucceed: The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by Awukam 3 months ago - 8 comments

#171 - Error after installing Specflow extension in VS 2022 (17.10.5)

Issue - State: open - Opened by gopalverma 4 months ago - 6 comments

#170 - .feature file is not opening

Issue - State: open - Opened by Sehedi2014 4 months ago

#169 - Upgraded to Dotnet 8.0 , sdk 8.0.303 and SpecFlow version 3.9.74

Issue - State: open - Opened by AniketWadkar78 4 months ago - 7 comments

#168 - After update SpecFlowNunit and SpecFlow versions to 3.9.74 .feature.cs files are not generated any more and it causes to not find the tests in Test Explorer

Issue - State: open - Opened by onurtarar-bt 4 months ago - 1 comment

#167 - Latest version not available in Microsoft Marketplace

Issue - State: open - Opened by sebastiankahlsh 4 months ago - 2 comments

#166 - Unable to use SpecFlow in Visual Studio Professional 2022

Issue - State: open - Opened by himanshu-cbre 4 months ago

#165 - The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by 11khugener 5 months ago - 3 comments

#164 - Error from Generating Step Definitions in .NET 8 vsix

Issue - State: open - Opened by stevenmolencsat 5 months ago

#163 - After updating Visual Studio 2022 to latest version getting Error

Issue - State: open - Opened by somnath0991 5 months ago

#162 - The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by SerhiiPolehenko 7 months ago - 13 comments

#161 - SpecFlow Visual Studio Extension failing when loading any project in VS

Issue - State: open - Opened by jos-01-02 7 months ago - 5 comments

#160 - Visual studio 2022 enterprise Specflow extension failing to load

Issue - State: open - Opened by veeresh-bikkaneti 7 months ago - 1 comment

#159 - Are Visual Basic Step Definitions supported in the VS2022 Extension

Issue - State: open - Opened by buzzer70 7 months ago

#158 - data table colouring when some lines are commented out

Issue - State: open - Opened by mumaguma 8 months ago

#157 - Getting "Operation cannot be completed" popup when tryingt o create a feature file in VS2022

Issue - State: open - Opened by Mahmoods 8 months ago

#156 - Inserting pipe symbol in Examples table cancels multi-cursor editing

Issue - State: open - Opened by ramiabughazaleh 9 months ago

#155 - Navigation, step definition disabled

Issue - State: closed - Opened by leibson 9 months ago - 1 comment

#154 - Fields of specific type break the extension.

Issue - State: open - Opened by algirdasN 10 months ago

#153 - Specflow is not working

Issue - State: open - Opened by sankarnarayanan100895 10 months ago - 8 comments

#152 - Severity Code Description Project File Line Suppression State Warning The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled. 0

Issue - State: open - Opened by Jankita31 11 months ago - 3 comments

#151 - Release Version Mismatch

Issue - State: open - Opened by alexwiese 11 months ago

#150 - PresentationFramework.dll fails to load in projects using .NET 8.0, xUnit, and WPF

Issue - State: open - Opened by rkttu 11 months ago

#149 - Step Definition is not working

Issue - State: open - Opened by HingminSon7 12 months ago - 8 comments

#148 - The project bindings (e.g. step definitions) could not be discovered.

Issue - State: open - Opened by gauravi555 12 months ago - 4 comments

#147 - "Unit test Provider already set" error when I added reference of one SpecFlow project to another SpecFlow project

Issue - State: open - Opened by MarichkaOK 12 months ago - 2 comments

#146 - Update to .NET 8

Pull Request - State: closed - Opened by marcel-tatasteel about 1 year ago - 16 comments

#145 - Step navigation stopped working when updated to .NET 8

Issue - State: open - Opened by marcel-tatasteel about 1 year ago - 12 comments

#144 - When a project is migrated from Visual Studio 2019 to 2022, Go to definition stops working for referenced project

Issue - State: closed - Opened by marhyno about 1 year ago - 1 comment

#143 - System.TypeLoadException : Could not load type 'OpenQA.Selenium.PhantomJS.PhantomJSOptions' from assembly 'WebDriver, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null'.

Issue - State: closed - Opened by wahidhaabduljabbar07 about 1 year ago - 1 comment

#142 - Seeing issue Cannot create an instance of Microsoft.VisualStudio.TestTools.UnitTesting.TestContext because it is an abstract class.

Issue - State: open - Opened by agspep over 1 year ago

#141 - The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by Prabhu-Kumara over 1 year ago

#140 - Bump NuGet.CommandLine from 5.11.3 to 5.11.5 in /SpecFlow.VisualStudio.Package

Pull Request - State: open - Opened by dependabot[bot] over 1 year ago
Labels: dependencies

#139 - Bump NuGet.CommandLine from 5.11.3 to 5.11.5 in /Tests/Connector/SpecFlow.VisualStudio.SpecFlowConnector.Tests

Pull Request - State: open - Opened by dependabot[bot] over 1 year ago
Labels: dependencies

#138 - Bump NuGet.CommandLine from 5.11.3 to 5.11.5 in /Tests/SpecFlow.SampleProjectGenerator

Pull Request - State: open - Opened by dependabot[bot] over 1 year ago
Labels: dependencies

#137 - Bump NuGet.CommandLine from 5.11.3 to 5.11.5 in /Tests/SpecFlow.VisualStudio.Specs

Pull Request - State: open - Opened by dependabot[bot] over 1 year ago
Labels: dependencies

#136 - Bump NuGet.CommandLine from 5.11.3 to 6.0.5 in /Tests/Connector/SpecFlow.VisualStudio.SpecFlowConnector.Tests

Pull Request - State: closed - Opened by dependabot[bot] over 1 year ago - 1 comment
Labels: dependencies

#135 - Bump NuGet.CommandLine from 5.11.3 to 6.0.5 in /SpecFlow.VisualStudio.Package

Pull Request - State: closed - Opened by dependabot[bot] over 1 year ago - 1 comment
Labels: dependencies

#134 - Bump NuGet.CommandLine from 5.11.3 to 6.0.5 in /Tests/SpecFlow.SampleProjectGenerator

Pull Request - State: closed - Opened by dependabot[bot] over 1 year ago - 1 comment
Labels: dependencies

#133 - Bump NuGet.CommandLine from 5.11.3 to 6.0.5 in /Tests/SpecFlow.VisualStudio.Specs

Pull Request - State: closed - Opened by dependabot[bot] over 1 year ago - 1 comment
Labels: dependencies

#132 - Goto step definition not available from context menu

Issue - State: closed - Opened by emnu1971 over 1 year ago - 2 comments

#131 - Find Step Definition Usages does not always work

Issue - State: open - Opened by jrod567 over 1 year ago - 3 comments

#130 - Add new table will update all .cs files with new variable names

Issue - State: open - Opened by FinnKjar over 1 year ago

#129 - Broken suggestion for generic step argument

Issue - State: open - Opened by qrjo over 1 year ago

#128 - Project created with the "SpecFlow Project" template produces compiler error CS8630: Invalid 'nullable' value: 'Enable' for C# 7.3.

Issue - State: open - Opened by icnocop over 1 year ago

#127 - "Go To Test" navigates to the generated code-behind file and not the scenario in the feature file in Visual Studio 2022 17.5.0

Issue - State: open - Opened by icnocop over 1 year ago - 13 comments

#126 - Specflow extension does not detect StepDefinitions in other assembly

Issue - State: open - Opened by informatorius almost 2 years ago - 2 comments

#125 - Specflow extension no longer automatically detects changes in steps definition

Issue - State: open - Opened by Gwarion almost 2 years ago - 1 comment

#124 - SpecFlow error after build Could not load file or assembly Microsoft.Extensions.Features

Issue - State: open - Opened by vivere-dally almost 2 years ago - 2 comments

#123 - The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by TroyPalmerNZ almost 2 years ago - 13 comments

#122 - Specflow nUnit tests do not run in Visual studio 2022

Issue - State: open - Opened by VijayaSree2019 almost 2 years ago - 4 comments
Labels: bug

#121 - Step Argument color

Issue - State: open - Opened by AlessandroMinunnoNOV about 2 years ago
Labels: bug

#120 - Specflow feature file functionality not working.

Issue - State: closed - Opened by ahmadk almost 2 years ago - 2 comments

#119 - 'Go to Test' from Test Explorer window opens the auto-generated C# backing file instead of the .feature file

Issue - State: closed - Opened by mattrenshaw94 almost 2 years ago - 2 comments

#118 - Bump Newtonsoft.Json from 13.0.1 to 13.0.2 in /Connectors/SpecFlow.VisualStudio.SpecFlowConnector.V1

Pull Request - State: open - Opened by dependabot[bot] almost 2 years ago
Labels: dependencies

#117 - SpecFlow extension not available in Visual Studio 17.4

Issue - State: open - Opened by samyamit almost 2 years ago - 5 comments

#116 - Add arm64 support for the Specflow plugin in Visual Studio 2022

Issue - State: open - Opened by MartijnSips almost 2 years ago - 2 comments

#115 - Add .NET 7 support

Issue - State: closed - Opened by LeftTwixWand about 2 years ago - 14 comments

#114 - The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by payalpatil about 2 years ago - 7 comments

#113 - Adds Arm64 VS Extension support

Pull Request - State: closed - Opened by snickler about 2 years ago - 1 comment

#111 - Error during binding discovery - Could not load file or assembly 'Microsoft.Extensions.Configuration.UserSecrets, Version=6.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'

Issue - State: open - Opened by CKAWLS about 2 years ago

#110 - SpecFlow throws exception when inheriting from System.ServiceModel.ClientBase<T>

Issue - State: open - Opened by mnemcik-visma about 2 years ago

#109 - Could not load file or assembly 'MyStepAssembly' if step assembly only targets the x86 platform

Issue - State: open - Opened by icnocop about 2 years ago - 1 comment

#108 - Bump NuGet.CommandLine from 5.11.2 to 5.11.3 in /Tests/SpecFlow.SampleProjectGenerator

Pull Request - State: closed - Opened by dependabot[bot] about 2 years ago
Labels: dependencies

#107 - Bump NuGet.CommandLine from 5.11.2 to 5.11.3 in /Tests/SpecFlow.VisualStudio.Specs

Pull Request - State: closed - Opened by dependabot[bot] about 2 years ago
Labels: dependencies

#106 - Bump NuGet.CommandLine from 5.11.2 to 5.11.3 in /SpecFlow.VisualStudio.Package

Pull Request - State: closed - Opened by dependabot[bot] about 2 years ago
Labels: dependencies

#105 - Bump NuGet.CommandLine from 5.11.2 to 5.11.3 in /Tests/Connector/SpecFlow.VisualStudio.SpecFlowConnector.Tests

Pull Request - State: closed - Opened by dependabot[bot] about 2 years ago
Labels: dependencies

#104 - The type initializer for 'AutoTests.Framework.Logging.Log' threw an exception.

Issue - State: open - Opened by sam22blr about 2 years ago

#103 - The file is not a valid VSIX package

Issue - State: closed - Opened by Hexzhe about 2 years ago - 1 comment

#102 - Rename Step Errors in Some Visual Studio 2022 Projects

Issue - State: open - Opened by CRohm42 about 2 years ago - 5 comments

#101 - Ambiguous steps displayed in Visual Studio 2022 when Specflow.Autofac higher than 3.9.58 is referenced

Issue - State: open - Opened by vikingkom over 2 years ago - 9 comments
Labels: bug

#100 - Error during binding discovery - when using System.Windows.Media.Media3D in step files

Issue - State: open - Opened by cyclingJW about 2 years ago

#99 - Error during binding discovery - Cannot find reference assembly 'System.Runtime.Intrinsics.dll' file

Issue - State: open - Opened by Naweap about 2 years ago - 3 comments

#98 - Method not found: 'Int32 System.Text.Encodings.Web.TextEncoder.FindFirstCharacterToEncodeUtf8(System.ReadOnlySpan`1<Byte>)'.

Issue - State: open - Opened by stegander about 2 years ago

#98 - Method not found: 'Int32 System.Text.Encodings.Web.TextEncoder.FindFirstCharacterToEncodeUtf8(System.ReadOnlySpan`1<Byte>)'.

Issue - State: open - Opened by stegander about 2 years ago

#97 - Parameter issue while defining steps

Issue - State: open - Opened by polatsbf over 2 years ago

#96 - System.InvalidOperationException: Cannot find reference assembly 'System.Core.dll' file for package System.Core

Issue - State: open - Opened by nforss over 2 years ago - 1 comment

#95 - Unable to install the IDE Integration package

Issue - State: closed - Opened by Fakhraei-m over 2 years ago - 3 comments

#94 - Incorrect Visual Studio design time error 'invalid parameter count' when using optional capturing regex groups

Issue - State: open - Opened by williamfigtree over 2 years ago - 6 comments
Labels: bug

#93 - The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled.

Issue - State: open - Opened by priyankakote over 2 years ago - 22 comments

#92 - Spec flow step definition creation issue

Issue - State: open - Opened by srilathavanukuri over 2 years ago - 1 comment

#91 - Ambiguous steps displayed in Visual Studio 2022 when Specflow.Autofac higher than 3.9.58 is referenced

Issue - State: open - Opened by vikingkom over 2 years ago

#90 - Adding Azure.Identity project reference crashes the generic discovery connector

Issue - State: open - Opened by RemyBoyer over 2 years ago - 1 comment

#89 - Warning: AndDiscoveryProviderSucceed: Error during binding discovery.

Issue - State: open - Opened by Vagunas over 2 years ago

#88 - Bump NuGet.CommandLine from 5.11.0 to 5.11.2 in /SpecFlow.VisualStudio.Package

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago
Labels: dependencies

#87 - Bump NuGet.CommandLine from 5.11.0 to 5.11.2 in /Tests/Connector/SpecFlow.VisualStudio.SpecFlowConnector.Tests

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago
Labels: dependencies

#86 - Bump NuGet.CommandLine from 5.11.0 to 5.11.2 in /Tests/SpecFlow.SampleProjectGenerator

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago
Labels: dependencies

#85 - Bump NuGet.CommandLine from 5.11.0 to 5.11.2 in /Tests/SpecFlow.VisualStudio.Specs

Pull Request - State: closed - Opened by dependabot[bot] over 2 years ago
Labels: dependencies

#84 - Added templates

Pull Request - State: closed - Opened by marcosikkens over 2 years ago - 5 comments

#83 - Unable to Regenerate Feature.cs file VS 2022 when we migrate Feature files that are written VS 2015.

Issue - State: open - Opened by ChaithraParameshwar over 2 years ago - 1 comment

#82 - Unable to jump to the step definition. Invalid source file or file position.

Issue - State: open - Opened by icnocop over 2 years ago - 4 comments

#81 - Fix for missing output path problem

Pull Request - State: closed - Opened by gasparnagy over 2 years ago - 1 comment

#80 - Error during binding discovery

Issue - State: open - Opened by djvandijk over 2 years ago

#79 - .runsettings not loading in VS 2022

Issue - State: open - Opened by lalberto8085 over 2 years ago - 1 comment

#78 - Ambiguous step definition with new VS 2022 extension 2022.1.56.32801

Issue - State: open - Opened by DomZZ over 2 years ago - 1 comment

#77 - Unable to jump to the step definition. No source location detected.

Issue - State: open - Opened by bastarnae over 2 years ago - 40 comments

#76 - Opening feature file in VS 2022 --> Errors

Issue - State: closed - Opened by Klarahov over 2 years ago - 5 comments

#75 - System.IO.FileLoadException: System.IO.Abstractions

Issue - State: open - Opened by p07r0457 over 2 years ago

GitHub / specflowoss/specflow.vs issues and pull requests