Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
Zwuai opened this issue Apr 7, 2022 · 0 comments
Labels
enhancement New feature or request

Comments

@Zwuai
Copy link

Zwuai commented Apr 7, 2022

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
@Zwuai Zwuai added the enhancement New feature or request label Apr 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant