Steps are displayed as binded while there is no step definition exist when using Scenario Outline

[okyrylenko]

SpecFlow Version:

• [ ] 3.0
• [ ] 2.4
• [X] 2.3
• [ ] 2.2
• [ ] 2.1
• [ ] 2.0
• [ ] 1.9

Used Test Runner

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

Version number:

Visual Studio Version

• [ ] VS 2019
• [X] VS 2017
• [ ] VS 2015
• [ ] VS 2013

Are the latest Visual Studio updates installed?

• [ ] Yes
• [X] No

.NET Framework:

• [X] >= .NET 4.5
• [ ] before .NET 4.5
• [ ] .NET Core 2.0
• [ ] .NET Core 2.1
• [ ] .NET Core 2.2
• [ ] .NET Core 3.0

Test Execution Method:

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

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

<specFlow>
        <runtime stopAtFirstError="false" />
        <stepAssemblies>
            <!-- This attribute is required in order to use StepArgument Transformation as described here; 
                https://github.com/marcusoftnet/SpecFlow.Assist.Dynamic/wiki/Step-argument-transformations
            -->
            <!-- This attribute is required in order to use StepArgument Transformation as described here; 
    https://github.com/marcusoftnet/SpecFlow.Assist.Dynamic/wiki/Step-argument-transformations  -->
            <stepAssembly assembly="SomaAssembly.Core" />
            <stepAssembly assembly="SomeAssembly.Pages" />
            
        <stepAssembly assembly="SpecFlow.Assist.Dynamic" /></stepAssemblies>       
        
    <!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- For additional details on SpecFlow configuration options see http://go.specflow.org/doc-config --><!-- use unit test provider SpecRun+NUnit or SpecRun+MsTest for being able to execute the tests with SpecRun and another provider --><unitTestProvider name="SpecRun" /><plugins>
      <add name="SpecRun" />
    </plugins></specFlow>

Repro Project

Issue Description

When I use scenario outline, the steps are displayed as binded when there is no step definition exist, the test is skipped when trying to execute because no step definition found warning. Also getting no step definition found message when attempting to navigate to the step from a feature file pressing F12

Steps to Reproduce

[SabotageAndi]

probably duplicate of https://github.com/techtalk/SpecFlow/issues/1486

[okyrylenko]

@SabotageAndi you are referring to this defect in your previous comment. This is defect 1486

[okyrylenko]

there is a workaround for this defect. The user still can generate step definitions and steps in feature file link to them. It is not a show stopper but may be confusing when user experience this issue the first time.

[SabotageAndi]

sorry, I used the wrong number. It's https://github.com/techtalk/SpecFlow/issues/498