You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
support request => Please do not submit support request here, see note at the top of this template.
What is the current behavior?
Omitting paramNameRegex and paramValueRegex of specflow.stepArguments in allureConfig.json results in the following error if a step contains a two-column data table:
Feature: My featureScenario: My scenarioThen a step with a table
|a|b| |1|2|
The step definition:
usingAllure.Net.Commons;usingTechTalk.SpecFlow;namespaceClassLibrary2;[Binding]publicclassClass1{[Then("a step with a table")]publicvoidMyStep(Tabletable){}}
What is the expected behavior?
Tables with two columns should be either skipped (i.e., converted to attachments) or, probably, converted to step parameters according to the rules for horizontal data tables.
What is the motivation / use case for changing the behavior?
Some users might want to convert one-row tables to parameters while skipping all two-column tables with more than one row entirely.
Currently, there is no way of doing this. Users are forced to make up name and value patterns that don't match enything.
I'm submitting a ...
What is the current behavior?
Omitting
paramNameRegex
andparamValueRegex
ofspecflow.stepArguments
inallureConfig.json
results in the following error if a step contains a two-column data table:If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
allureConfig.json:
The feature file:
The step definition:
What is the expected behavior?
Tables with two columns should be either skipped (i.e., converted to attachments) or, probably, converted to step parameters according to the rules for horizontal data tables.
What is the motivation / use case for changing the behavior?
Some users might want to convert one-row tables to parameters while skipping all two-column tables with more than one row entirely.
Currently, there is no way of doing this. Users are forced to make up name and value patterns that don't match enything.
Please tell us about your environment:
The text was updated successfully, but these errors were encountered: