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.22k stars 752 forks source link

Error during binding discovery #2688

Open mrKilljoy opened 1 year ago

mrKilljoy commented 1 year ago

SpecFlow Version

3.0.213

Which test runner are you using?

SpecFlow+ Runner

Test Runner Version Number

3.0.213

.NET Implementation

equal or greater .NET Framework 4.6.1

Project Format of the SpecFlow project

Sdk-style project format

.feature.cs files are generated using

SpecFlow.Tools.MsBuild.Generation NuGet package

Test Execution Method

Visual Studio Test Explorer

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

No response

Issue Description

When I try to launch project tests via context menu item, the next message appears in the output window:

Warning: AndDiscoveryProviderSucceed: Error during binding discovery. Command executed: C:\Repos\SpecFlow_OldCSProj_FeatureInSubfolder\ClassLibrary1\bin\Debug> c:\users\Админ\appdata\local\microsoft\visualstudio\17.0_79fda9b8\extensions\d235fk3u.1av\Connectors\V1\specflow-vs.exe discovery C:\Repos\SpecFlow_OldCSProj_FeatureInSubfolder\ClassLibrary1\bin\Debug\ClassLibrary1.dll "" Exit code: 3 Message: Exception in:SpecFlow.VisualStudio.SpecFlowConnector.Discovery.SpecFlowV30Discoverer Error: Cannot find method CreateGlobalContainer on type TechTalk.SpecFlow.Infrastructure.ContainerBuilder Exception: System.ArgumentException StackTrace: at SpecFlow.VisualStudio.SpecFlowConnector.ReflectionExtensions.ReflectionCallMethod[T](Object obj, String methodName, Type[] parameterTypes, Object[] args) in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector\ReflectionExtensions.cs:line 30 at SpecFlow.VisualStudio.SpecFlowConnector.ReflectionExtensions.ReflectionCallMethod[T](Object obj, String methodName, Object[] args) in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector\ReflectionExtensions.cs:line 8 at SpecFlow.VisualStudio.SpecFlowConnector.Discovery.RemotingBaseDiscoverer.GetBindingRegistry(Assembly testAssembly, String configFilePath) in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector.V1\Discovery\RemotingBaseDiscoverer.cs:line 39 at SpecFlow.VisualStudio.SpecFlowConnector.Discovery.BaseDiscoverer.DiscoverInternal(Assembly testAssembly, String testAssemblyPath, String configFilePath) in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector\Discovery\BaseDiscoverer.cs:line 52 at SpecFlow.VisualStudio.SpecFlowConnector.Discovery.RemotingBaseDiscoverer.Discover(String testAssemblyPath, String configFilePath) in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector.V1\Discovery\RemotingBaseDiscoverer.cs:line 12 at SpecFlow.VisualStudio.SpecFlowConnector.Discovery.DiscoveryProcessor.Process() in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector.V1\Discovery\DiscoveryProcessor.cs:line 16 at SpecFlow.VisualStudio.SpecFlowConnector.ConsoleRunner.EntryPoint(String[] args) in D:\a\1\s\Connectors\SpecFlow.VisualStudio.SpecFlowConnector\ConsoleRunner.cs:line 31 Cannot deserialize: Warning: AndDiscoveryProviderSucceed: The project bindings (e.g. step definitions) could not be discovered. Navigation, step completion and other features are disabled. Please check the error message above and report to https://github.com/SpecFlowOSS/SpecFlow.VS/issues if you cannot fix.

I used the the sample project found in this topic since I have a similar problem but with a newer version of Specflow (3.9.8 + NUnit3) in a different IDE (Jetbrains Rider). However, in the latter case I see no such messages: the Test Explorer is empty, as with this sample project.

Do you know what might cause this issue?

Steps to Reproduce

1) Clone the project 2) Build the solution 3) Select "Run Tests" from the context menu. 4) Find the results on "Output" tab choosing "Specflow" as the source

Link to Repro Project

No response

mrKilljoy commented 1 year ago

Not sure whether it is related to this tool or Specflow.VS, though.