Do not give up on emulators. Obviously is better to have the real device to do dry run testing. But sometimes you might not have the real hardware at the moment. The drag about emulators is that you have to accommodate your app for the components your emulator does not have or does not behave the same way the real hardware. In this case, studying the way the emulators behave and have a testing procedure for them might be the best idea. That could a task for an automation tester. Also, there are other solutions for emulators. It could be Genymotion or even the devices in Google Firebase. As far for Android Studio emulators is good to have a powerful machine to run these. And always use X86 architecture since these ones are similar to the Android Studio machine.
Comments about Android Emulator Woes
Do not give up on emulators. Obviously is better to have the real device to do dry run testing. But sometimes you might not have the real hardware at the moment. The drag about emulators is that you have to accommodate your app for the components your emulator does not have or does not behave the same way the real hardware. In this case, studying the way the emulators behave and have a testing procedure for them might be the best idea. That could a task for an automation tester. Also, there are other solutions for emulators. It could be Genymotion or even the devices in Google Firebase. As far for Android Studio emulators is good to have a powerful machine to run these. And always use X86 architecture since these ones are similar to the Android Studio machine.
😊+