Functional Testing with Android Emulator?
Hi everyone, I'm relatively new to QA and would appreciate some input.
Would a Android Emulator provide a similar experience to testing the functionality of an application to a real device?
I found a thread on this from 2006 and the answers are rather inconclusive, I also consider that mobile technology has come a long way since then.
Any thoughts would be appreciated!
From what I have seen is most clients insist on testing on real device. Regarding emulators - I used ipad emulator on mac desktop 3-4 years back to test an application & we didn't have any complaints from the users, who later used the application on actual ipad. I don't have any idea about today's emulators.
I test a hybrid application we are developing on both emulator and device. I am using Genymotion as an emulator though, simply because the stock Android emulators in the SDK are VERY slow. Genymotion provides a pretty decent interface, and is fairly fast, although still not as fast as an actual device.
Our process flow actual accounts for 3 different platforms to test on, actually. For code-review and team lead review we use the Chrome developer tools to test, then as it passes to QA I use emulation for quick exploratory testing, and finally I use the device proper to test more, and to execute automated scripts on.
As far as my experience goes, the emulator is near enough to an actual device that the results are indistinguishable. If these are native apps you are testing, you should be fine with either. If it is a Cordova hybrid or web view application, either would do fine, although the device itself may test faster than the emulator.
Hope this helps!
Originally Posted by sanketvaidya
You can use Browserstack or saucelab for the emulator
I am utilizing Genymotion as an emulator however, just on the grounds that the stock Android emulators in the SDK are very moderate. Genymotion gives a truly not too bad interface, and is genuinely quick.
The answer is yes and no. For certain types of apps, say a web app that mainly fetches information and display content, and android emulator is quite effective. For things that have a high amount of hardware integration, ex: using bluetooth LE, or motion co processor, etc... there could be a lot of variability that can cause results to be different.
Originally Posted by Stevicus
This is an extreme example. But say you had a bright screen with relatively white colored content and the screen was drawing a lot of power, which in turn is causing the wires to emit more magnetic interference which is interfering with Bluetooth LE and causing a lot of noise in the signal. You may consider testing against specific hardware you want to support.
To answer your question, we need to understand that there is no emulator who can replace the actual device, till date.
Having said that, almost every software testing company used emulator to test their native, web or hybrid apps. Below is the list of points which are being followed in qa services companies as well:
- Development and unit testing can be performed using Android SDK or Genymotion.
- Basic regressions test and functionality verification can also be done on emulators, if actual devices are not available.
- However no application should be released to market before its verification on real devices using sanity suite.
Reason for verification on Real device:
- Irrespective of how advance the emulator is, it has been found that 20-30 % defects are only found and reproducible on real device
One good example can be when we are traveling and network connection goes out.
Or how the application behaves once the battery level goes down to 10%.
These scenarios cannot be reproduced on emulator.
Hope you have a good idea of how you can divide your testing between Emulators and real device.
The answer would always be a combination of emulators and real device, one of the reason being its cost effectiveness. Both have their own benefits and downfalls.
An article https://qualityboulevard.blogspot.in...nk-before.html talks about many factors affecting tesing on smartphones including emulator Vs device combo.
Quality Assurance Lead, India
"A Cat looked at the mirror and what she saw was a Lion. Secret of success depends on how you see yourself."