make MenuFlyoutItem.Click working

[pkar70]

GitHub Issue (If applicable): #227

PR Type

What kind of change does this PR introduce?

• Feature

What is the current behavior?

MenuFlyoutItem.Click is not fired.

What is the new behavior?

MenuFlyoutItem.Click is fired.

PR Checklist

Please check if your PR fulfills the following requirements:

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)

Other information

Re-created PR#1779, code change and tests in single commit.
Test is somehow based on Jerome Laban idea from 1779.

Still trying to create test, as it seems that MenuFlyout is not rendered.

Internal Issue (If applicable):

[pkar70]

How to make CI run again? It failed:
Using element matching Marked("runButton").
Tapping coordinates [ 32, 76 ].
then
Query for Marked("failedTests")
But this is not my test (not test from this PR), as I don't use such names.

[pkar70]

how to check WHICH test is failing? It seems that fails not test in my PR, but some other..

[carldebilly]

/azp run

[pkar70]

Please be more specific...
I mean rerun tests not on my PC, but on 'your' github/azure.

I checked source files for other platforms. And my PR can probably be extended to iOS (MenuFlyout.iOS7.iOS.cs and MenuFlyout.iOS8.iOS.cs files), but not for WASM. As I cannot in any way test iOS change on my side, should I try to make change for iOS, with hope that my UI test on azure will be sufficient?

[gitpod-io]

[jeromelaban]

@pkar70 I'm taking a look at why your changes are not passing.

[pkar70]

Did you find cause of error?

[jeromelaban]

Not really. It's not your PR, it's the same issue from Java.exe that will probably get fixed when we'll update the CI servers.