Game Testing on Android Emulators without x86 Support

As you know from the previous blog if you have read it, if not you can still read it HERE.
I am trying to find the best possible solution for testing games when there is not enough resources and how to automate that process.
For current engine ( Unity ), Firebase Game Loop testing framework does wonders but it requires a development team to implement the support for it. Usually also coding a bot to perform any game related tasks… This approach works well, if the game is small bot can be easily made, but if the game is quite large then another solution would be needed. I am working on a mobile game, it has a fair chance of features that having bot to do will be enough, but I also want an option to have an “exploratory” testing method. With “exploratory” testing methods, I mean to have games receive input events, sensor events, or any kind of events / command and perform them in that order.
So question how to achieve that?
To achieve that, depending on the platform and engine there are some solutions, and I won't go into details too much how I will achieve them, at least not into this post, here I am dealing with what happens after you have your tests ready but you are unable to execute them on emulator as most emulators only except x86 builds.

First thing that came to my mind when I got into this situation was: “Cool, I could use Firebase, but Firebase is limited to only 15 tests per day...What next…?”
Damn, yeah 15 tests per day may sound much, but actually it is not, to test for example 10 different languages on phone, that would take 10 devices - 10 tests.
To test different aspects at least 5 one, would take 5 devices - 5 tests.
What about sub tests: such as playing a game with a specific character, or play without sound, or watch for performances :/
Yeah on free-model not gonna work, but then again what about creating multiple accounts, then multiple “projects” then switching and running them.
So, If I needed 60 tests per day, I would need to create 4 different emails, to have 4 different projects and then through CL to manage that.
Still could work but it is a hassle.

My dream is to not be limited by the number of devices, but by the number of hardware, so in my case before we execute tests on real devices, to execute them in a simulated environment and have them executed at least each night. Now you may ask why without x86 support. Recently Unity removed x86 support for Android with version 2019.3 so you are no longer able to build for that architecture, therefore I am unable to use android emulators as they are all x86. It is true you could run their armeabi images but they are extremely slow..
I tried to run Genymotion, as in back of my mind I was convinced it uses armeabi architecture, but sadly they also use x86 architecture so that approach didn't work well.
Then I started to dig around and found some possible solutions:

• Bluestacks
• MEME
• Dolphin
• Andy Android Emulator
• LDPlayer

app_installed {args[1]}
remove_app {args[1]}
install_apk {args[4]} {args[2]} {args[1]}
run_app {args[5]}