Capgemini / Capgemini/powerapps-specflow-bindings
Populating and asserting boolean fields on forms does not allow use of labels instead of True/False
- 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
In some instances when populating a boolean field on a form the requirement of using True/False instead makes the test not very readable, for example when the True/False labels for the field are now something completely different, and not positive/negative values.
## Describe the solution you'd like
It would be good to allow this step to accept the field labels for the fields rather than just the true/false values, as in this example, it is impossible to know whether true maps or "Red" or "Blue":
```
When I enter 'true' into the 'new_redorblue' boolean field on the form
```
## Additional context
This feature is applicable for both below steps:
```
When I enter 'true' into the 'new_redorblue' boolean field on the form
Then I can see a value of 'true' in the 'new_redorblue' boolean field
```
Contributor guide
Assessment
This issue has not been assessed yet.