Specflow Tests are visible and Steps are bind but steps are not executed

[anandprasathm]

Specflow Tests are visible, steps binded but steps are not executed

SpecFlow Version:

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

Used Test Runner

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

Version number:

Project Format of the SpecFlow project

• [X] Classic project format using packages.config
• [ ] Classic project format using <PackageReference> tags
• [ ] Sdk-style project format

.feature.cs files are generated using

• [X] SpecFlow.Tools.MsBuild.Generation NuGet package
• [ ] SpecFlowSingleFileGenerator custom tool

Visual Studio Version

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

Enable SpecFlowSingleFileGenerator Custom Tool option in Visual Studio extension settings

• [ ] Enabled
• [X] Disabled

Are the latest Visual Studio updates installed?

• [X] Yes
• [ ] No, I use Visual Studio version <Major>.<Minor>.<Patch>

.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

Repro Project

Issue Description

Hi,

I am facing the below issue while debugging/run my Specflow test using Visual Studio Test Explorer.

Specflow Tests are

• Visible in Visual Studio Test Explorer

• Steps are having binding that we could see on Feature file but if we execute/debug the steps, the test is keep on running but doen't reaches the debug point.

I am using MsTest as the UnitTestrunner.

Could any one please help me on this?

Steps to Reproduce

[SabotageAndi]

Does this happen also in the example from us? You can find them at https://github.com/SpecFlowOSS/SpecFlow-Examples

[SabotageAndi]

Closed because of inactivity

[github-actions[bot]]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.