Menu
Home
People
Places
Arts
History
Plants & Animals
Science
Life & Culture
Technology
Reference.org
Mobile application testing
open-in-new
<h2 id="key-challenges-for-mobile-application-testing">Key challenges for mobile application testing</h2> <ul><li>Must be downloadable: The <a href="/facts/Mobile_app/r7vp6meo">application</a> must be obtainable for the particular <a href="/facts/Mobile_operating_system/wysBVca1">platform</a>, generally from an <a href="/facts/App_store/czIkzyv9">app store</a>.</li> <li>Diversity in mobile platforms/OSes:There are different <a href="/facts/Mobile_operating_system/wysBVca1">mobile operating systems</a> in the market. The major ones are <a href="/facts/Android_(operating_system)/nNyHb0xz">Android</a>, <a href="/facts/IOS/mK5cggH5">iOS</a>, and <a href="/facts/Windows_Phone/khEg0rGT">Windows Phone</a>. Each <a href="/facts/Mobile_operating_system/wysBVca1">operating system</a> has its own limitations.</li> <li>Device availability: Access to the right set of devices when there is an ever-growing list of devices and operating system versions is a constant <a href="/facts/Mobile_app/r7vp6meo">mobile application</a> testing challenge. Access to devices can become even more challenging if testers are spread across different locations.</li> <li>Mobile network operators: There are over 400 <a href="/facts/Mobile_network_operator/6Tt5J4TF">mobile network operators</a> in the world;<a class="footnote-ref" id="fnref:5" href="#fn:5"><sup>5</sup></a> some are <a href="/facts/CDMA/o2RLKE4M">CDMA</a>, some <a href="/facts/GSM/Sw8QYaLE">GSM</a>, and others use less common network standards like <a href="/facts/FOMA/pVeQ1HX0">FOMA</a>, and <a href="/facts/TD-SCDMA/lhy2RrMw">TD-SCDMA</a>.</li> <li>Scripting: The variety of devices makes executing a <a href="/facts/Test_script/Yz2uKhaP">test script</a> (scripting) a key challenge. As devices differ in <a href="/facts/Keystrokes/0YdM6AoB">keystrokes</a>, <a href="/facts/Input_method/HoB832tg">input methods</a>, menu structure and display properties, a single script does not function on every device.</li> <li>Test method: There are two main ways of testing <a href="/facts/Mobile_app/r7vp6meo">mobile applications</a>: testing on real devices or testing on <a href="/facts/Emulator/FMHE8qDj">emulators</a>.<a class="footnote-ref" id="fnref:6" href="#fn:6"><sup>6</sup></a> Emulators often miss issues that can only be caught by testing on real devices, but because of the multitude of different devices in the market, real devices can be expensive to purchase and time-consuming to use for testing.<a class="footnote-ref" id="fnref:7" href="#fn:7"><sup>7</sup></a><a class="footnote-ref" id="fnref:8" href="#fn:8"><sup>8</sup></a></li> <li>Compatibility: It is necessary to test the <a href="/facts/Computer_compatibility/PNAF7EAB">compatibility</a>; ensuring that the application works consistently even with different device properties, such as different screen sizes and <a href="/facts/Display_resolution/8LQTWvl3">resolutions</a>.</li> <li>Should be able to pick up the phone: While executing the app application should be able to pick up a call.</li> <li>Variety of mobile devices: Mobile devices differ in screen input methods (<a href="/facts/QWERTY/0DCjXEa9">QWERTY</a>, touch, normal) with different <a href="/facts/Computer_hardware/8jSjsCNv">hardware</a> capabilities.</li> <li> Lack of capacity for users' scenarios creation. While conducting performance testing of mobile application, the engineers usually lack sufficient hardware to perform proper load testing.</li></ul> <h2 id="types-of-mobile-application-testing">Types of mobile application testing</h2> <ul><li><a href="/facts/Functional_testing/2VudQTaz">Functional testing</a> ensures that the <a href="/facts/Mobile_app/r7vp6meo">application</a> is working as per the requirements. Most of the tests conducted for this is driven by the <a href="/facts/User_interface/e9sPEWVD">user interface</a> and call flow.</li> <li>Laboratory testing, usually carried out by <a href="/facts/Mobile_network_operator/6Tt5J4TF">network carriers</a>, is done by simulating the complete <a href="/facts/Wireless_network/yr4SWTdl">wireless network</a>. This test is performed to find out any glitches when a <a href="/facts/Mobile_app/r7vp6meo">mobile application</a> uses voice and/or data connection to perform some functions.</li> <li><a href="/facts/Software_performance_testing/qtlCrHme">Performance testing</a> is undertaken to check the performance and behavior of the <a href="/facts/Mobile_app/r7vp6meo">application</a> under certain conditions such as low battery, bad network coverage, low available memory, simultaneous access to the <a href="/facts/Mobile_app/r7vp6meo">application</a>'s server by several users and other conditions. Performance of an <a href="/facts/Mobile_app/r7vp6meo">application</a> can be affected from two sides: the <a href="/facts/Mobile_app/r7vp6meo">application</a>'s server side and client's side. <a href="/facts/Software_performance_testing/qtlCrHme">Performance testing</a> is carried out to check both.</li> <li>Memory leakage testing: <a href="/facts/Memory_leak/JzufAL28">Memory leakage</a> happens when a computer program or <a href="/facts/Mobile_app/r7vp6meo">application</a> is unable to manage the memory it is allocated resulting in poor performance of the <a href="/facts/Mobile_app/r7vp6meo">application</a> and the overall slowdown of the system. As mobile devices have significant constraints of available memory, memory leakage testing is crucial for the proper functioning of an <a href="/facts/Mobile_app/r7vp6meo">application</a></li> <li>Interrupt testing: An <a href="/facts/Mobile_app/r7vp6meo">application</a> while functioning may face several interruptions like incoming calls or network coverage outage and recovery. The different types of interruptions are:</li></ul> <ul><li>Incoming and outgoing <a href="/facts/SMS/kacRfW0X">SMS</a> and <a href="/facts/Multimedia_Messaging_Service/Pg5CvwLx">MMS</a></li> <li>Incoming and outgoing calls</li> <li>Incoming notifications</li> <li>Battery removal</li> <li>Cable insertion and removal for data transfer</li> <li>Network outage and recovery</li> <li>Media player on/off</li> <li>Device power cycle</li></ul> An <a href="/facts/Mobile_app/r7vp6meo">application</a> should be able to handle these <a href="/facts/Interrupt/Mm6C4rpc">interruptions</a> by going into a suspended state and resuming afterwards. <ul><li><a href="/facts/Usability_testing/prsYgc00">Usability testing</a> is carried out to verify if the <a href="/facts/Mobile_app/r7vp6meo">application</a> is achieving its goals and getting a favorable response from users. This is important as the usability of an <a href="/facts/Mobile_app/r7vp6meo">application</a> is its key to commercial success (it is nothing but <a href="/facts/Usability/zuAnqu9Q">user friendliness</a>).<a class="footnote-ref" id="fnref:9" href="#fn:9"><sup>9</sup></a> Another important part of usability testing is to make sure that the <a href="/facts/User_experience/0GF3UETu">user experience</a> is uniform across all devices.<a class="footnote-ref" id="fnref:10" href="#fn:10"><sup>10</sup></a> This section of testing hopes to address the key challenges of the variety of mobile devices and the diversity in mobile platforms/OS, which is also called device fragmentation. One key portion of this type of usability testing is to be sure that there are no major errors in the functionality, placement, or sizing of the <a href="/facts/User_interface/e9sPEWVD">user interface</a> on different devices.<a class="footnote-ref" id="fnref:11" href="#fn:11"><sup>11</sup></a></li> <li><a href="/facts/Installation_testing/e6F0BXFu">Installation testing</a>: Certain <a href="/facts/Mobile_app/r7vp6meo">mobile applications</a> come <a href="/facts/Pre-installed_software/boFAWQDy">pre-installed</a> on the device whereas others have to be installed by the store. Installation testing verifies that the installation process goes smoothly without the user having to face any difficulty. This testing process covers installation, updating and uninstalling of an <a href="/facts/Mobile_app/r7vp6meo">application</a></li> <li>Certification testing: To get a certificate of compliance, each mobile device needs to be tested against the guidelines set by different <a href="/facts/Mobile_operating_system/wysBVca1">mobile platforms</a>.</li> <li><a href="/facts/Security_testing/gtEmKE5b">Security testing</a>: Checks vulnerabilities to <a href="/facts/Hacking_(computing)/4bAJ9F1A">hacking</a>, authentication and authorization policies, data security, session management and other security standards.<a class="footnote-ref" id="fnref:12" href="#fn:12"><sup>12</sup></a></li> <li>Location testing: Connectivity changes with network and location, but you can't mimic those fluctuating conditions in a lab. Only in Country non-automated testers can perform comprehensive usability and functionality testing.</li> <li>Outdated software testing: Not everyone regularly updates their operating system. Some <a href="/facts/Android_(operating_system)/nNyHb0xz">Android</a> users might not even have access to the newest version. Professional testers can test outdated software.</li> <li><a href="/facts/Load_testing/fHRPN97k">Load testing</a>: When many users all attempt to download, load, and use an app or game simultaneously, slow load times or crashes can occur causing many customers to abandon your app, game, or website. In-country human testing done manually is the most effective way to test load.<a class="footnote-ref" id="fnref:13" href="#fn:13"><sup>13</sup></a></li> <li><a href="/facts/Black-box_testing/j2velRR9">Black-box testing</a>: Where the <a href="/facts/Mobile_app/r7vp6meo">application</a> is tested without looking at the <a href="/facts/Mobile_app/r7vp6meo">applications</a> <a href="/facts/Code/CSntvnEo">code</a> and <a href="/facts/Logic_programming/Xgh8lj3F">logic</a>. The tester has specific <a href="/facts/Test_data/QF0SurNA">test data</a> to input and the corresponding output that the <a href="/facts/Mobile_app/r7vp6meo">application</a> should produce, and inputs the <a href="/facts/Test_data/QF0SurNA">test data</a> looking for the program to output data consistent with what the tester was expecting. This method of test can be applied virtually to every level of software testing: <a href="/facts/Unit_testing/SYoGGS3T">unit</a>, <a href="/facts/Integration_testing/FcPo9Fmn">integration</a>, <a href="/facts/System_testing/ThxRDsAy">system</a> and <a href="/facts/Acceptance_testing/xlDUeQ0M">acceptance</a>.</li> <li><a href="/facts/Crowdsourced_testing/xtPRMfKf">Crowdsourced testing</a>: In recent years, crowdsourced testing has become popular as companies can test <a href="/facts/Mobile_app/r7vp6meo">mobile applications</a> faster and cheaper using a global community of testers. Due to growing diversity of devices and operating systems as well as localization needs, it is difficult to comprehensively test <a href="/facts/Mobile_app/r7vp6meo">mobile applications</a> with small in-house testing teams. A global community of testers provides easy access to different devices and platforms. A globally distributed team can also test it in multiple locations and under different network conditions. Finally, localization issues can be tested by hiring testers in required geographies. Since real users using real devices test the <a href="/facts/Application_software/YQuj7Kog">application</a>, this is more likely to find issues faced by users under real world conditions.<a class="footnote-ref" id="fnref:14" href="#fn:14"><sup>14</sup></a><a class="footnote-ref" id="fnref:15" href="#fn:15"><sup>15</sup></a></li></ul> <h2 id="references">References</h2> <ol> <li id="fn:1"><p>"'What is Mobile Testing?', SmartBear Software". smartbear.com. Retrieved 2014-07-23. <a href="https://smartbear.com/products/qa-tools/automated-testing-tools/resources/what-is-mobile-testing/" target="_blank">https://smartbear.com/products/qa-tools/automated-testing-tools/resources/what-is-mobile-testing/</a> <a href="#fnref:1" class="footnote-back-ref">↩</a></p></li> <li id="fn:2"><p>"'Increase efficiency and productivity with Test Automation', Bitbar". bitbar.com. Retrieved 2014-08-07. <a href="http://bitbar.com/increase-efficiency-and-productivity-with-test-automation" target="_blank">http://bitbar.com/increase-efficiency-and-productivity-with-test-automation</a> <a href="#fnref:2" class="footnote-back-ref">↩</a></p></li> <li id="fn:3"><p>"Mobile app revenues 2015-2020 | Statistic". Statista. Retrieved 2019-03-08. <a href="https://www.statista.com/statistics/269025/worldwide-mobile-app-revenue-forecast/" target="_blank">https://www.statista.com/statistics/269025/worldwide-mobile-app-revenue-forecast/</a> <a href="#fnref:3" class="footnote-back-ref">↩</a></p></li> <li id="fn:4"><p>"Core technology of wearable devices". DigiTimes. July 15, 2014. <a href="https://www.digitimes.com/news/a20140714PR201.html?chid=9" target="_blank">https://www.digitimes.com/news/a20140714PR201.html?chid=9</a> <a href="#fnref:4" class="footnote-back-ref">↩</a></p></li> <li id="fn:5"><p>"Testing Strategies and Tactics for Mobile Applications, Keynote White Paper" (PDF). Keynote.com. Retrieved 2012-05-02. <a href="http://www.keynote.com/docs/whitepapers/WP_Testing_Strategies.pdf" target="_blank">http://www.keynote.com/docs/whitepapers/WP_Testing_Strategies.pdf</a> <a href="#fnref:5" class="footnote-back-ref">↩</a></p></li> <li id="fn:6"><p>"Emulated vs. Real Device Mobile App Testing". bitbar.com. Retrieved 2016-11-08. <a href="http://bitbar.com/rely-only-on-real-emulators-vs-devices/" target="_blank">http://bitbar.com/rely-only-on-real-emulators-vs-devices/</a> <a href="#fnref:6" class="footnote-back-ref">↩</a></p></li> <li id="fn:7"><p>"Testing on Emulators vs Real Devices | Smashing Magazine". Smashing Magazine. 2 October 2014. Retrieved 2016-11-08. <a href="https://www.smashingmagazine.com/2014/10/what-every-app-developer-should-know-about-android/" target="_blank">https://www.smashingmagazine.com/2014/10/what-every-app-developer-should-know-about-android/</a> <a href="#fnref:7" class="footnote-back-ref">↩</a></p></li> <li id="fn:8"><p>"The Pitfalls of Mobile Emulators| Mobile1st Blog". Mobile1st.com. Retrieved 2015-09-30. <a href="http://mobile1st.com/the-pitfalls-of-mobile-emulators-5-blind-spots-that-mean-trouble/" target="_blank">http://mobile1st.com/the-pitfalls-of-mobile-emulators-5-blind-spots-that-mean-trouble/</a> <a href="#fnref:8" class="footnote-back-ref">↩</a></p></li> <li id="fn:9"><p>"StickyMinds | How the Usability Matrix of Emotions Can Benefit Your Software Testing | Page 1". StickyMinds. Retrieved 2015-10-29. <a href="http://www.stickyminds.com/article/how-usability-matrix-emotions-can-benefit-your-software-testing" target="_blank">http://www.stickyminds.com/article/how-usability-matrix-emotions-can-benefit-your-software-testing</a> <a href="#fnref:9" class="footnote-back-ref">↩</a></p></li> <li id="fn:10"><p>Contractor, Lena. "What is User Experience?". WhatUsersDo. Retrieved 2015-10-31. <a href="http://whatusersdo.com/clients/resources/what-is-user-experience" target="_blank">http://whatusersdo.com/clients/resources/what-is-user-experience</a> <a href="#fnref:10" class="footnote-back-ref">↩</a></p></li> <li id="fn:11"><p>"Mobile UX Issues Caused by Device Fragmentation". Testmunk Blog. Retrieved 2015-10-31. <a href="http://blog.testmunk.com/mobile-ux-issues-caused-by-device-fragmentation/" target="_blank">http://blog.testmunk.com/mobile-ux-issues-caused-by-device-fragmentation/</a> <a href="#fnref:11" class="footnote-back-ref">↩</a></p></li> <li id="fn:12"><p>"Mobile App Testing Techniques and Tools". Mindster. 2019-07-16. Archived from the original on January 2, 2021. Retrieved 2021-01-02. <a href="https://mindster.com/mobile-app-testing-techniques-tools/" target="_blank">https://mindster.com/mobile-app-testing-techniques-tools/</a> <a href="#fnref:12" class="footnote-back-ref">↩</a></p></li> <li id="fn:13"><p>"Mobile App Testing | Services Issues | Page 1". GTT. Retrieved 2016-03-22. <a href="http://www.globaltelecomtesting.com/mobile-app-testing-services.php" target="_blank">http://www.globaltelecomtesting.com/mobile-app-testing-services.php</a> <a href="#fnref:13" class="footnote-back-ref">↩</a></p></li> <li id="fn:14"><p>"Mobile Application Testing using Managed Crowd Sourcing". Qualitrix.com. 2017-02-06. Retrieved 2017-03-14. <a href="http://qualitrix.com/mobile-application-testing" target="_blank">http://qualitrix.com/mobile-application-testing</a> <a href="#fnref:14" class="footnote-back-ref">↩</a></p></li> <li id="fn:15"><p>"6 Major Pitfalls of Crowdsourced Software Testing - QualityLogic". QualityLogic. 2017-10-26. Retrieved 2018-02-14. <a href="https://www.qualitylogic.com/2017/10/26/6-major-pitfalls-crowdsourced-software-testing/" target="_blank">https://www.qualitylogic.com/2017/10/26/6-major-pitfalls-crowdsourced-software-testing/</a> <a href="#fnref:15" class="footnote-back-ref">↩</a></p></li> </ol>