Capgemini / Capgemini/powerapps-specflow-bindings

No table format step for "Then I can see a value of 'expectedValue' in the 'field' text field"

Open
#124 0 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C#
Stars
42
Forks
27
PR merge metrics
No merged PRs in 30d

Description

## Is your feature request related to a problem? Please describe
_A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]_

When asserting that fields on a form, the individual step has to be used many times, as there is no step accepting a table.

## Describe the solution you'd like
_A clear and concise description of what you want to happen._
There should be a step called Then I (can|cannot) see the following fields on the form which accepts a table and calls the individual

Then I can see following values on the form
| ExpectedValue | Field | FieldLocation |
| Brita Water | name| field |

## Additional context
na

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.