specflow vs test explore show duplicated tests

[noone2454]

SpecFlow Version:

• 3.1
• 3.0
• 2.4
• 2.3
• 2.2
• 2.1
• 2.0
• 1.9

Used Test Runner

• 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
• Sdk-style project format

.feature.cs files are generated using

• SpecFlow.Tools.MsBuild.Generation NuGet package
• SpecFlowSingleFileGenerator custom tool

Visual Studio Version

• VS 2019
• VS 2017
• VS 2015

Enable SpecFlowSingleFileGenerator Custom Tool option in Visual Studio extension settings

• Enabled
• Disabled

Are the latest Visual Studio updates installed?

• 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
• .NET Core 2.2
• .NET Core 3.0

Test Execution Method:

• 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

{
    "bindingCulture":
    {
        "language" :"en-us"
    },
    "language":
    {
        "feature": "en-us"
    }
}

Repro Project

Issue Description

there is only one test scenario , but the test explore is showing as following

below are the screenshot of the packages used, the scenario and the test explorer

Steps to Reproduce

[SabotageAndi]

Duplicate of #1921
It's a bug in the NUnit3 Adapter

[Santjo]

Are you sure?
The error occurs with last SpecFlow version (3.1.89) only but not with the version before (3.1.86).

[goblinmaks]

@Santjo I am sure, because 3.1.89 use New nunit test generator

[noone2454]

will that be fixed?

[goblinmaks]

First of all if nunit/nunit#3285 will be implemented it will be good.
#1874

I hope yes =)

[SabotageAndi]

With 3.1.95 #1874 was reverted. This issue should be solved after updating.

[github-actions]

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.