On Android API < 30 and API > 31 have absolutely different code for handling keyboard. We constantly run tests for API=28, but since we have conditional code for API 30+ it would be better to include the code for that platform too.
In this PR I added this ability 😎
Also I re-worked approach and now building and testing apk has different jobs on CI (in order not to do the same work n-times).
📢 Changelog
CI
added matrix strategy (test on API 28 and 31);
split Android e2e job into building step and then run e2e tests from a given apk;
E2E
scrollDownUntilElementIsVisible starts a gesture from the middle;
move e2e_emulator assets to e2e_emulator_28 folder;
created e2e_emulator_31 assets;
added script for running separate tests;
🤔 How Has This Been Tested?
Tested on CI.
📸 Screenshots (if appropriate):
📝 Checklist
[x] CI successfully passed
[x] I added new mocks and corresponding unit-tests if library API was changed
📜 Description
Run e2e tests on Android 12.
💡 Motivation and Context
On Android API < 30 and API > 31 have absolutely different code for handling keyboard. We constantly run tests for API=28, but since we have conditional code for API 30+ it would be better to include the code for that platform too.
In this PR I added this ability 😎
Also I re-worked approach and now building and testing apk has different jobs on CI (in order not to do the same work n-times).
📢 Changelog
CI
E2E
scrollDownUntilElementIsVisible
starts a gesture from the middle;e2e_emulator
assets toe2e_emulator_28
folder;e2e_emulator_31
assets;🤔 How Has This Been Tested?
Tested on CI.
📸 Screenshots (if appropriate):
📝 Checklist