Ronaldo Peres

icon indicating a website link https://www.linkedin.com/in/ronaldoperes/ icon indicating an email [email protected]

icon company Dell Technologies icon location Brazil icon location Hi, I am a backend developer, mainly working with Dotnet C# for more than 10 years., Also, I use other technologies like RabbitMq, MongoDb, NodeJs, React etc

Results 4 comments of Ronaldo Peres

About arrange instances and mocks in Constructor Test classes

> I prefer to avoid using the constructor to setup and teardown tests, and tend to keep everything required by the test defined in the test itself. Otherwise it can...

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

I got same problem, but after I updated the project to dotnet 8. I updated Visual Studio to version 17.10.0 and specflow extension: ![image](https://github.com/SpecFlowOSS/SpecFlow.VS/assets/8013864/e9f2dc7c-0b45-4804-9d34-cef3b155586b) After I build the project, got...

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

> I found a root cause of an issue, that should be fixed by SpecFlow plugin owner. The problem is in that, here: C:\Users\MyUserName\AppData\Local\Microsoft\VisualStudio\17.0_c987e58d\Extensions\SomeHash\Connectors\specflow-vs.runtimeconfig.json there is a missing runtime option,...

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

> Installing the extension from the releases and not from the marketplace fixed the issue for me. I also upgraded my project to .net8. https://github.com/SpecFlowOSS/SpecFlow.VS/releases/tag/v2022.1.93-net8 I installed it over the...