Test case naming changes after SpecFlow → Reqnroll migration break test ID mapping

[krishnaduvey]

Problem

After migrating from SpecFlow to Reqnroll, scenario outline test cases are being generated with different parameter indices, breaking all existing test case mappings and statistics in Azure DevOps/TFS.

The extra index parameter is being inserted into test names, causing scenarios to be counted as new tests rather than updates to existing ones.

Example

SpecFlow (Old):

FeatureFile1.TC_1.1("8722","501","Failed to initiate...",null)
FeatureFile1.TC_1.2("8722","502","Failed to initiate...",null)

Reqnroll (New):

FeatureFile1.TC_1.1("8722","501","Failed to initiate...",1,null)
FeatureFile1.TC_1.2("8722","502","Failed to initiate...",2,null)

Notice: Extra 1 and 2 parameters inserted, breaking test ID consistency.

Root Cause

The example index is being appended to the test parameters, changing the method signature and test identity.

Configuration Attempted

• Investigated reqnroll.json settings for scenarioOutlineParamStyle
• Parameter injection appears unavoidable in current version
• No documented way to preserve SpecFlow naming format

Business Impact

• Years of test statistics and metrics are now invalid — each test appears as a new one
• Cannot maintain test history/traceability — existing Azure DevOps test cases cannot map to new tests
• Large projects face significant overhead — manual remapping of thousands of test cases
• Internal tools for statistics collection broken — rely on consistent test IDs

Questions / Feature Request

1. Is there a configuration option to preserve original SpecFlow test naming?
2. Can scenario outline parameter generation be customized or disabled?
3. Would a migration guide or mapping tool be helpful for existing SpecFlow users?
4. Could Reqnroll provide a backward-compatibility mode for test naming?

Environment

• Reqnroll version: 3.3.4
• Test framework: NUnit
• Azure DevOps integration with internal statistics tools
• Large legacy project with thousands of existing test cases

Workarounds Needed

Since this impacts production test tracking, knowing any available workarounds would help:

• Custom test naming strategies?
• Any way to preserve the same scenario outline param style which used by specflow?
• Migration scripts from community?

Additional Context

This is a breaking change from SpecFlow that significantly impacts large enterprises relying on historical test data and Azure DevOps integration.

[304NotModified]

Now duplicate of https://github.com/orgs/reqnroll/discussions/1086