[UI Tests] - Update Android emulator model and version#7454
Conversation
You can test the changes on this Pull Request by downloading an installable build, or scanning this QR code:
|
pachlava
left a comment
There was a problem hiding this comment.
Hi @jostnes 👋
This is a kind of PR for which it's enough to see that the execution on FTL is 🟢 - and it is 👍
Just curious - why didn't you go for API 32? The tests passed on it too, and the execution time is only 9 seconds slower. Is it because of the error seen in the log? Is this a persistent error?
Thanks!
|
Thanks for the review @pachlava !
I was thinking since Android 11 is the most used OS for the app right now, we can start with that first and do an incremental update. I also know most of our real device testing is done on Android 12 (API 31/32) and not Android 11 (API 30). I tested on API 32 to know that if we do decide to update it to that later, it will be an easy change. I'm going to sound terrible but I actually did not notice the error you shared 😬 |
Closes: #7447
Description
This PR updates the emulator version that the instrumented tests on FTL are running on. From testing, found that Pixel 3 API 30 runs the test really slow so will exclude that device for now. There are also some changes needed if we remain to use the current Pixel 2 device.
There is Pixel 2 (ARM) emulator that supports multiple APIs including newer ones. I tested that out and it runs the tests well without requiring any other code changes. Will update the tests to use that device with API 30 (Android 11) as it is currently the most used version.
Testing instructions
All instrumented tests should pass locally and in CI.
Images/gif
RELEASE-NOTES.txtif necessary.