Open ikbendruk opened 4 years ago
Interesting issue.
We recommend putting parameters of your steps in single quotes '
. This makes it easier for a human and also our logic to recognize what are parameters in the step.
So your step would look like Given '5' <= '<x>'
So your step would look like
Given '5' <= '<x>'
Thanks for the tip!
Unfortunately, this does not work very well for me since my steps look more like:
Then parameter <Parameter> value remains equal to or less than <Value> for <Timeout> seconds
The idea was to make these steps shorter and more readable with <=, >=.
I also tried special symbols ≤, ≥. They work perfectly fine with SpecFlow but are not properly displayed in the console output. So this option does not help either.
SpecFlow Version:
Used Test Runner
Version number: 3.8.1.0
Project Format of the SpecFlow project
packages.config
<PackageReference>
tags.feature.cs files are generated using
SpecFlow.Tools.MsBuild.Generation
NuGet packageSpecFlowSingleFileGenerator
custom toolVisual Studio Version
Enable SpecFlowSingleFileGenerator Custom Tool
option in Visual Studio extension settingsAre the latest Visual Studio updates installed?
<Major>.<Minor>.<Patch>
.NET Framework:
Test Execution Method:
<SpecFlow> Section in app.config or content of specflow.json
Repro Project
Issue Description
When executing the following scenario outline
with the following step implementation
SpecFlow generates the following NUnit code
Parameter x is not parsed properly that's why the test fails.
Steps to Reproduce