Define myths of Android Testing?

Answer

Many enterprises develop android testing strategies that are based on common misconceptions. This section examines a few popular myths and realities of Android testing.

Myth #1:All Android devices are the same... test on emulators is enough

Let's start with a simple example. An application works perfectly on emulator s but on some real devices, it crashes during execution

Emulators are not sufficient for your mobile testing. You must test your app on real devices.

Myth #2:Testing on some common devices is enough

• On different devices, your application looks different because different devices have different hardware, screen sizes, memory etc. You must test your application on different devices, OS versions, carrier networks and locations.

Myth#3:Exploratory testing just before launch is enough

• Generally in all testing, we design the test cases then execute them. But in Exploratory testing, test design and execution all will be done together.
• In exploratory testing, there's no plan and no preparation, then tester would do tests that he wants to do. Some functions will be tested repeatedly, while some functions will not be tested altogether.

Myth#4:If there some bugs in application, users will understand

• If application doesn't work and has bugs, users uninstall your app
• Quality issues are the first reason for bad review in Google Play. It affects to your reputation and you lose customer's trust.

Therefore its essential to have a proper android testing strategy in place