Specflow: Execution is not stopping at Debug point when running in Debug mode

[zeeshankhan0330]

SpecFlow Version:

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

Used Test Runner

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

Version number:

Project Format of the SpecFlow project

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

.feature.cs files are generated using

• [ ] 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

• [x] Enabled
• [ ] Disabled

Are the latest Visual Studio updates installed?

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

.NET Framework:

• [ ] >= .NET 4.5
• [ ] before .NET 4.5
• [ ] .NET Core 2.0
• [ ] .NET Core 2.1
• [x] .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

When running the code in Debug mode and put a debug point on Feature file, on Step definition file, on Methods being called from stepdefiniton files, Execution is not stopped at any of the debug point and it executed completely.
Specflow Specrun version - 3.0.352

Steps to Reproduce

1) Put a debug point on Feature file, step definition, method callled from step definiton.
3 places of a single test case.
2) Run test case in debug mode

Actual Result:
Execution completed without being stopped at debug point

Expected Result:
Execution should be stopped at debug point

[SabotageAndi]

@zeeshankhan0330
Can you provide a small project where you can reproduce the issue. I wasn't able to reproduce it. Thanks!

[zeeshankhan0330]

@SabotageAndi Sorry for the delay in response.
Please find link to a project where I am able to replicate it.
Link: https://github.com/zeeshankhan0330/IssueReporting_SpecflowDebugNotWorking

I tried to put debug point at feature file, step definition and a method that sits in 'utility' class which is being called in Step definition file.
But it did not stop at any Debug point.

Let me know if anything else if required from my end.

[SabotageAndi]

@zeeshankhan0330 This will be an interesting issue.
Debugging is working in VS2019, but not in VS2017. No idea why, because both have the same binaries.

[zeeshankhan0330]

let me check with vs2019 and confirm.

• Cant confirm now as I am not able to install 2019 due to some system issues.

[SDETLD]

Will there be a fix for this issue for Visual Studio 2017? Not being able to debug is a pretty critical issue.

[SabotageAndi]

We are working on getting it to work again.

It's a really strange issue. We can debug everything, so the test adapter itself, additional processes, the SpecFlow plugin, but not the test assembly.
PDBs are loaded for the test assembly, but the debugger doesn't step into it.
And in VS 2019 everything is working.

[kpughconsult]

I'm having the same issue with Visual Studio 2019 Version 16.6.2 and SpecFlow 3.3.30, SpecRun.SpecFlow 3.3.17. The project is just the example project in the distribution. Setting a breakpoint in the stepdefs or the calculator does not stop anything. Writing to Debug does not produce any output. I added another Test project to the solution with just an MSTest. Breakpoints and Debug writing work with that test.

[SabotageAndi]

Ok, that it is not working Visual Studio 2019 is new. I will have a look at it.

[SabotageAndi]

@kpughconsult I tried it with our Bookshop example (https://github.com/SpecFlowOSS/SpecFlow-Examples/tree/master/ASP.NET-MVC/BookShop) in Visual Studio 16.6.3 and it worked.
Sorry, I can't reproduce your issue.

[sudgarre]

@SabotageAndi : Is there a plan to fix this issue for VS2017 any sooner ?

[SabotageAndi]

@sudgarre the problem with this issue is, that we have no idea why it is not working.
I think we already invested a work month of time into this without any progress. Debugging is working perfectly fine in VS2019, but simply doesn't work in VS2017.
And in both versions, the same code is executed.