SpecFlow.VisualStudio icon indicating copy to clipboard operation
SpecFlow.VisualStudio copied to clipboard

Step Definitions Missing in Feature Files

Open yoyo-array0825 opened this issue 7 years ago • 3 comments

Issue Description

Hi.

Following a recent update, my step definition references are missing from my feature files. 'Go to Definition' at the step level throws the dialog in below screenshot. The step definitions have not moved or been modified, and tests are running as expected.

Steps in external file(s).

Things Already Tried

  • Updated VisualStudio
  • Deleted "spec*" files from %TEMP% directory
  • Disabling, re-enabling SpecFlow add-ons

Other Things of Note

  • Other users on same source code not experiencing this issue
  • Issue comes and goes but is currently persisting through steps that previously worked to correct it

SpecFlow Version:

  • [x] 2.4
  • [ ] 2.3
  • [ ] 2.2
  • [ ] 2.1
  • [ ] 2.0
  • [ ] 1.9

Used Test Runner

  • [x] SpecFlow+Runner
  • [ ] MSTest
  • [ ] NUnit
  • [ ] Xunit

Version number: 1.8.2

Visual Studio Version

  • [x] VS 2017
  • [ ] VS 2015
  • [ ] VS 2013

Are the latest Visual Studio updates installed?

  • [x] Yes
  • [ ] No

.NET Framework:

  • [x] >= .NET 4
  • [ ] before .NET 4

Test Execution Method:

  • [x] Visual Studio Test Explorer
  • [ ] TFS/VSTS – Task – PLEASE SPECIFY THE NAME OF THE TASK
  • [ ] Command line – PLEASE SPECIFY THE FULL COMMAND LINE

<SpecFlow> Section in app.config

  <specFlow>
    
    <stepAssemblies>
      <stepAssembly assembly="WebIZ.Test.Specflow" />
    </stepAssemblies>
    <unitTestProvider name="SpecRun" />
    <plugins>
      <add name="SpecRun" />
    </plugins>
  </specFlow>

Repro Project

screenshot-08y0yu9ui0

Steps to Reproduce

No idea

yoyo-array0825 avatar Sep 27 '18 18:09 yoyo-array0825

Are the steps in the external step assemblies?

SabotageAndi avatar Oct 01 '18 12:10 SabotageAndi

Yes.

yoyo-array0825 avatar Oct 01 '18 15:10 yoyo-array0825

The VS Integration has problems with the syntax highlighting when external step assemblies are used. That's a known issue. Sadly we never found the time to have a look at it.

SabotageAndi avatar Oct 02 '18 12:10 SabotageAndi