SpecFlowOSS / SpecFlow.VS

The next version of the Visual Studio extension for SpecFlow
MIT License
36 stars 10 forks source link

Find Step Definition Usages does not always work #131

Open jrod567 opened 1 year ago

jrod567 commented 1 year ago

Used Visual Studio

Visual Studio 2022

Are the latest Visual Studio updates installed?

Yes

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

{ "$schema": "https://specflow.org/specflow-config.json", "livingDocGenerator": { "enabled": true, "filePath": "JLivingDoc\LivingDoc_[{now:MM-dd-yyyy_HH.mm.ss}].json" } }

Issue Description

Find Step Definition Usages does not always work and can lead to users believing a step definition isn't used anywhere. When the feature doesn't work, it shows which is completely misleading: image

The SpecFlow output log shows: image

In this particular case, I know this is false and the step definition belongs to several feature files. Whenever the SpecFlow output shows "Found 0 usages in 0 feature files", I know this is not working correctly - as such we have to use this as an indicator on whether or not to trust the result.

This is arguably one of the most important features with this VS add-in and it really needs to work 100%

Steps to Reproduce

This is the problem - it works sometime and others not. We have many different repos and each one may or may not work at seemingly random times. This affects multiple users for same and different repos and has always been an issue.

Are there additional debug logs we can enable for the extension to get more info to you?

Visual Studio v17.5.2 SpecFlow extension v2022.1.91.26832

Link to Repository Project

No response

CRohm42 commented 1 year ago

I have experienced this issue too and would appreciate a fix. Thanks!

browste commented 1 year ago

I have been impacted as well! Would love a fix!

joeschmidtJHA commented 1 year ago

Yes. I'm hoping someone can please get this fixed.