How To Test Android Mobile Applications
                     How To Test Android Mobile 
Applications?
Mobile app testing is a hot topic. The number of downloadable apps is barely comprehensible (Android Apps: 
1, 5 million apps; Apple’s App store: 1, 4 million apps) and the device fragmentation is nearly beyond 
imagination (24,093 Distinct Android devices seen up until August 2015). The first thing to understand when 
engaging with mobile application testing is that there is no easy way and no standard way of doing things, 
even though apps have standard requirements.
Standard requirements that require to become tested
   •    U sability
• Functionality
• Performance
• Edge Cases
Other important components when testing cellular apps will be the target gadgets (the devices you decide to test thoroughly 
your app on) that ought to be chosen smartly, typically between 10 - 30 units and relevant for the marketplace. 
A good example of top devices employed worldwide would include things like devices with display dimensions 
between 4.0" - 5.2" with quality between 640 x 1136px - 1080 x 1920px . Next thing is to search for the market 
stocks based on Operating-system and manufacturer. Google android (87% market present), accompanied by 
Apple (13% marketplace share) share the marketplace with many, with a lot of the Android devices jogging 
Marshmallow (34%) and Lollipop (39%). Nearly all Apple device work iOS 10x.
Testing stages of the mobile app
Different tests will be run during several life-cycle stages of app. Tests could be run personally or automated with 
regards to the performed test. Diverse tests are conducted by different sections (growth, QA, and development), 
with regards to the app's lifecycle period.
Tests to execute in the various life-cycle stages of your 
mobile app
As stated before, you can find mainly two forms of methods: 
the regular approach (regular testing) as well as the UI 
automation solution (automated screening).
The manual solution can be used for Checkups, 
Functionality, Edge Situations and Functionality, but it isn't 
designed for repetitive tests. You can find benefits and 
drawbacks to this strategy:
Pros: The specific behavior will get tested
Downsides: It's time-consuming and inefficient
Development can be an ongoing process, there is absolutely 
no start or conclude when discussing app growth, but 
continuous evaluation for continuous development that 
bring about continuous shipping and delivery: it is the never 
ending circuit of constant integration!
A practical example
So let's consider having latest builds or produces every week and every minimal improvement must be 
examined. Those minor improvements bring about 100 different make use of situations (50 for Google android 
and 50 for iOS) that require to be analyzed on 20 unique units. It's about 2000 unique combinations to check 
each week... every week! You can't really do this by hand: the solution to this will be the UI automation 
technique.