Capgemini / Capgemini/powerapps-specflow-bindings

Assertion failure information for "then I can see form notification" does not show actual issue

Open
#113 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

## Describe the bug
If the text passed to Then I can see a form notification stating x step does not match the actual notification, an unhelpful error is displayed:
e.g.
`Expected collection {Error: Field Name : Required fields must be filled in.} to have an item matching ((Convert(formNotification.Type) == 2) AndAlso (formNotification.Message == value(Capgemini.PowerApps.SpecFlowBindings.Steps.EntitySteps+<>c__DisplayClass28_0).message)).`

## To reproduce
Use the Then I can see form notification step with text that doesn't match the actual form notification and run the test.

## Expected behaviour
This error should match the expected error reporting that shows the two strings being compared, rather than the object names.
e.g. Expected notification to be "Test Input" but does not match "Error: Required fields must be filled in". Differs near 'E'.

## Screenshots

## Environment (please complete the following information):
- Test framework - NUnit
- Browser - Chrome
- Version - 0.14.3
- Power Apps environment version 9.2.22032.00145

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.