Reqnroll Version
3.2.1
Which test runner are you using?
NUnit
Test Runner Version Number
5.1.0.0
.NET Implementation
.NET 8.0
Test Execution Method
Azure DevOps Pipeline Task – PLEASE SPECIFY THE NAME OF THE TASK
Content of reqnroll.json configuration file
No response
Issue Description
After upgrading from Reqnroll 2.4.1 → 3.x, generated test methods for Scenario Outline Examples now include an additional index parameter.
This changes the method signature and breaks our Azure DevOps test mapping, which relies on the previous parameter order.
This behaviour does not appear in the migration guide or release notes.
Method that used to be this:
ValidateZeroInputForAgeLimit("Over","-10","The specified condition was not met for 'Age Limits'.", null)
Now includes an index, which breaks mapping to Azure Devops:
ValidateZeroInputForAgeLimit("Over","-10","The specified condition was not met for 'Age Limits'.","1", null)
Steps to Reproduce
Create any scenario outline with multiple Examples and build.
Upgrade to 3.2.1 and build.
Compare the generated test names in Test Explorer.
Link to Repro Project
No response
Reqnroll Version
3.2.1
Which test runner are you using?
NUnit
Test Runner Version Number
5.1.0.0
.NET Implementation
.NET 8.0
Test Execution Method
Azure DevOps Pipeline Task – PLEASE SPECIFY THE NAME OF THE TASK
Content of reqnroll.json configuration file
No response
Issue Description
After upgrading from Reqnroll 2.4.1 → 3.x, generated test methods for Scenario Outline Examples now include an additional index parameter.
This changes the method signature and breaks our Azure DevOps test mapping, which relies on the previous parameter order.
This behaviour does not appear in the migration guide or release notes.
Method that used to be this:
Now includes an index, which breaks mapping to Azure Devops:
Steps to Reproduce
Create any scenario outline with multiple Examples and build.
Upgrade to 3.2.1 and build.
Compare the generated test names in Test Explorer.
Link to Repro Project
No response