Update Appium dependency version to 1.20.2

[fluiddot]

gutenberg PR: WordPress/gutenberg#28890

Description

Appium dependency has recently included a fix for preventing an error when using NPM version 7 so it would be nice to update it.

To test:
Appium is only used for running the end-to-end tests so we need to verify that they work as expected. It should be enough by verifying that the PR checks pass and by running them locally with the following commands:

1. npm run test:e2e:ios:local for iOS
2. npm run test:e2e:android:local for Android

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

[dcalhoun]

🟢 Changes look good to me.
🟢 iOS e2e tests passed locally.
🟡 Android e2e tests had oddities locally.

The gutenberg-editor-audio tests hang indefinitely for me. I waited several minutes for them to fail, but they never did. I ultimately canceled the run. I asked @jd-alexander and he had not encountered this before. I suppose since this passes on the CI, this should not be a blocker. May just be a local environment issue.

Audio block hang

audio-block-test-hang.mov

The gutenberg-editor-paste passes on my emulator device, but fails on my physical Samsung S20 5G SE device. I'm wondering if this is something specific to (A) my local setup, (B) Samsung devices, or (C) using a physical device in general. I suppose since this passes on the CI, this should not be a blocker.

Paste test failure

android-paste-samsung-failure.mp4

@fluiddot did you encounter anything like this when running the Android e2e tests locally? If not, then it's likely just my local environment.

[ockham]

👋 @fluiddot @dcalhoun It seems that this is blocking WordPress/gutenberg#28890 in the Gutenberg repo, which in turn is required for npm 7 to work with GB. Any chance we'll be able to unblock things anytime soon? 😊 🙏

(edit, wrong PR)

[dcalhoun]

As we discussed in Slack, I think the e2e test oddities I encountered locally are likely not of consequence. The CI suite is succeeding and that should give us confidence.

[fluiddot]

As we discussed in Slack, I think the e2e test oddities I encountered locally are likely not of consequence. The CI suite is succeeding and that should give us confidence.

Yeah, I'm going to run a last test on Android just to verify there's no issue locally and then merge it, thanks!

[fluiddot]

Android e2e tests had oddities locally.

The gutenberg-editor-audio tests hang indefinitely for me. I waited several minutes for them to fail, but they never did. I ultimately canceled the run. I asked @jd-alexander and he had not encountered this before. I suppose since this passes on the CI, this should not be a blocker. May just be a local environment issue.

I also experience this issue the first time I ran them, in my case the audio block was not included in the inserter menu and it was failing. I managed to fix it by uninstall the Gutenberg app from the emulator and run the command again, I think in some cases the command doesn't install a fresh build.

The gutenberg-editor-paste passes on my emulator device, but fails on my physical Samsung S20 5G SE device. I'm wondering if this is something specific to (A) my local setup, (B) Samsung devices, or (C) using a physical device in general. I suppose since this passes on the CI, this should not be a blocker.

I haven't checked e2e tests with a real device locally, I'm wondering if the issue is related to these changes, have you run e2e tests on a device previously?

[dcalhoun]

I haven't checked e2e tests with a real device locally, I'm wondering if the issue is related to these changes, have you run e2e tests on a device previously?

@fluiddot no, I have not run the e2e tests on a physical device prior to this PR. I can attempt to do so on develop and see what occurs. I'll report back.

[dcalhoun]

@fluiddot after running the develop branch e2e tests on a physical device, I can confirm that the paste tests fail in develop as well. This should provide additional confidence in merging this PR.

[fluiddot]

As we discussed, since the CI suite is succeeding, it should be safe to merge it, thanks for the review @dcalhoun !

If we spot new issues regarding the e2e tests we'll address them in new PRs (like the one when testing with physical device).

[ockham]

Thanks a lot, folks! ❤️