Specflow+ ignoring breakpoints when debuging tests

40 views
Skip to first unread message

Mark Lovell

unread,
Mar 10, 2020, 11:44:36 AM3/10/20
to SpecRun
Just upgraded a project in Visual Studio 2017 from Specflow to now use Specflow+Runner and when I debug a test from the Test Explorer none of the breakpoints are hit. This used to work on this project before I switched to Specflow+.
I have tried breakpoints in the feature file, the step definition file and C# classes and all are ignored.

I have the following Specflow packages installed - Specflow, Specflow.Tools.MsBuild.Generation & SpecRun.SpecFlow. No other test runners are installed. The project is using .NET Core 2.2. I'm also using the latest ReSharper 2019.

I can't seem to find any solutions online for this problem so any help would be most appreciated.


Andreas Willich

unread,
Mar 10, 2020, 12:19:59 PM3/10/20
to SpecRun
Hi Mark

This is an issue with Visual Studio 2017. Debugging works for Visual Studio 2019.
GitHub issue about this is here: https://github.com/SpecFlowOSS/SpecFlow/issues/1625

We didn't yet figure it out, why debugging isn't working in VS2017. It's really a strange behaviour.

Best regards
Andi


--
You received this message because you are subscribed to the Google Groups "SpecRun" group.
To unsubscribe from this group and stop receiving emails from it, send an email to specrun+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/specrun/b6870674-75aa-4506-b474-0fc90dbb1c64%40googlegroups.com.

Mark Lovell

unread,
Mar 10, 2020, 12:25:43 PM3/10/20
to SpecRun
OK, thanks for the reply. I will look to upgrade to VS2019.


On Tuesday, 10 March 2020 16:19:59 UTC, Andreas Willich wrote:
Hi Mark

This is an issue with Visual Studio 2017. Debugging works for Visual Studio 2019.
GitHub issue about this is here: https://github.com/SpecFlowOSS/SpecFlow/issues/1625

We didn't yet figure it out, why debugging isn't working in VS2017. It's really a strange behaviour.

Best regards
Andi


On Tue, Mar 10, 2020 at 4:44 PM Mark Lovell <mlov...@gmail.com> wrote:
Just upgraded a project in Visual Studio 2017 from Specflow to now use Specflow+Runner and when I debug a test from the Test Explorer none of the breakpoints are hit. This used to work on this project before I switched to Specflow+.
I have tried breakpoints in the feature file, the step definition file and C# classes and all are ignored.

I have the following Specflow packages installed - Specflow, Specflow.Tools.MsBuild.Generation & SpecRun.SpecFlow. No other test runners are installed. The project is using .NET Core 2.2. I'm also using the latest ReSharper 2019.

I can't seem to find any solutions online for this problem so any help would be most appreciated.


--
You received this message because you are subscribed to the Google Groups "SpecRun" group.
To unsubscribe from this group and stop receiving emails from it, send an email to spe...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages