Spec flow oss#2571

[clrudolphi]

This PR resolves SpecFlow#2571 in which Scenario Outline parameters are not handled properly when the parameter identifier is nested within outer angle brackets. The defect report provided a sample of XML demonstrating the problem. The regex used in the ScenarioPartHelper captures all text between the first open bracket and the first close bracket. This might include additional opening brackets in between. var paramRe = new Regex(@"\<(?[^>]+)>"); This regex was changed such that the captured 'param' would not include any opening bracket character.

Added a unit test for ScenarioPartHelper to confirm that the generated code Statement properly recognizes parameters within embedding brackets and generates the proper code expression. Added a feature file in Specs.Features.RegressionTests that demonstrates the fix operating end-to-end.

Types of changes

• [x ] Bug fix (non-breaking change which fixes an issue).
• [ ] New feature (non-breaking change which adds functionality).
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
• [ ] Performance improvement
• [ ] Refactoring (so no functional change)
• [ ] Other (docs, build config, etc)

Checklist:

• [x ] I've added tests for my code. (most of the time mandatory)
• [ ] I have added an entry to the changelog. (mandatory)
• [ ] My change requires a change to the documentation.
• [ ] I have updated the documentation accordingly.

I'm new to this - not sure how or where you'd want me to update the changelog. Chris

[SabotageAndi]

Somehow VS deleted not the other files, so I did it now.

Thanks for your contribution to SpecFlow. Please submit your contributions to our SpecFlow Community Heroes program at https://specflow.org/community/submit-a-contribution/