hi @viktorbenei
So I’ve “done” it and it’s running my builds.
“done” was used with quotation marks because I see some stuff the previous script was doing to make sure that exactly emulator was booted for cases where there’re several emulators running and my version had to cut it short because:
a. Being separated into two steps makes it more complex to achieve it
b. I’m not very good on ruby.
But it solves the basic use case of having 1 emulator running that can run tests faster.
The steps are just two different branches of the original step with stuff removed from step.rb.
I’ve added to my project using your previous answer Is it possible to test a step directly on bitrise.io?
On my last build the booting up the emulator ran for 18 seconds and waiting for it to finish boot took 11 seconds.
If anyone wants to use/test/contribute you can find them on links below:
Wait for device
https://github.com/budius/steps-start-android-emulator/tree/wait