You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 44.199.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 12:56, 12 May 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪AntiCompositeNumber‬. The reason given is Open proxy/Webhost: Visit the FAQ if you are affected .
- Start of block: 13:55, 18 August 2022
- Expiry of block: 13:55, 18 May 2025
Your current IP address is 44.199.189.47. The blocked range is 44.199.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((multiple issues|((format|date=March 2018))
((more citations needed|date=July 2019))))

'''Mobile application testing''' is a process by which [[application software]] developed for [[Mobile device|handheld mobile devices]] is tested for its functionality, usability and consistency.<ref>((cite web | url=http://smartbear.com/products/qa-tools/automated-testing-tools/resources/what-is-mobile-testing/ | title='What is Mobile Testing?', SmartBear Software|publisher=smartbear.com|date=|accessdate=2014-07-23))</ref> Mobile application testing can be an automated or manual type of [[Software testing|testing]].<ref>((cite web | url=http://bitbar.com/increase-efficiency-and-productivity-with-test-automation | title='Increase efficiency and productivity with Test Automation', Bitbar|publisher=bitbar.com|date=|accessdate=2014-08-07))</ref> [[Mobile applications]] either come pre-installed or can be installed from [[App store|mobile software distribution platforms]]. Global mobile app revenues totaled 69.7 billion [[United States dollar|USD]] in 2015, and are predicted to account for US$188.9 billion by 2020.<ref>((Cite web|url=https://www.statista.com/statistics/269025/worldwide-mobile-app-revenue-forecast/|title=Mobile app revenues 2015-2020 ((!)) Statistic|website=Statista|language=en|access-date=2019-03-08))</ref>

[[Bluetooth]], [[Global Positioning System|GPS]], sensors, and [[Wi-Fi]] are some of the core technologies at play in [[Wearable computer|wearables]].<ref>((Cite web|url=https://www.digitimes.com/news/a20140714PR201.html?chid=9|title=Core technology of wearable devices|date=July 15, 2014|website=DigiTimes))</ref> Mobile application testing accordingly focuses on field testing, user focus, and looking at areas where [[Computer hardware|hardware]] and [[software]] need to be tested in unison.
<ref>((cite news |last1=Bolat |first1=Alex |title=Deneme Bonusu Veren Siteler 2023 |url=https://cbfwa.org/ |access-date=5 October 2021))</ref>
==Key challenges for mobile application testing==
* '''Must be downloadable''': The [[Mobile app|application]] must be obtainable for the particular [[Mobile operating system|platform]], generally from an [[app store]].
* '''Diversity in mobile platforms/OSes''':There are different [[mobile operating system]]s in the market. The major ones are [[Android (operating system)|Android]], [[iOS]], and [[Windows Phone]]. Each [[Mobile operating system|operating system]] has its own limitations.
* '''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 [[Mobile app|mobile application]] testing challenge. Access to devices can become even more challenging if testers are spread across different locations.
* '''Mobile network operators''': There are over 400 [[mobile network operator]]s in the world;<ref>((cite web|url=http://www.keynote.com/docs/whitepapers/WP_Testing_Strategies.pdf |title=Testing Strategies and Tactics for Mobile Applications, Keynote White Paper|publisher=Keynote.com|date=|accessdate=2012-05-02))</ref> some are [[CDMA]], some [[GSM]], and others use less common network standards like [[FOMA]], and [[TD-SCDMA]].
* '''Scripting''': The variety of devices makes executing a [[test script]] (scripting) a key challenge. As devices differ in [[keystrokes]], [[input method]]s, menu structure and display properties, a single script does not function on every device.
* '''Test method''': There are two main ways of testing [[Mobile app|mobile applications]]: testing on real devices or testing on [[emulator]]s.<ref>((Cite web|title = Emulated vs. Real Device Mobile App Testing|url = http://bitbar.com/rely-only-on-real-emulators-vs-devices/|website = bitbar.com|accessdate = 2016-11-08))</ref> 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.<ref>((Cite web|title = Testing on Emulators vs Real Devices ((!)) Smashing Magazine|url = https://www.smashingmagazine.com/2014/10/what-every-app-developer-should-know-about-android/|website = Smashing Magazine|accessdate = 2016-11-08))</ref><ref>((Cite web|title = The Pitfalls of Mobile Emulators((!)) Mobile1st Blog|url = http://mobile1st.com/the-pitfalls-of-mobile-emulators-5-blind-spots-that-mean-trouble/|website = Mobile1st.com|accessdate = 2015-09-30))</ref>
* '''Compatibility''': It is necessary to test the [[Computer compatibility|compatibility]]; ensuring that the application works consistently even with different device properties, such as different screen sizes and [[Display resolution|resolutions]].
* '''Should be able to pick up the phone''': While executing the app application should be able to pick up a call.
* '''Variety of mobile devices''': Mobile devices differ in screen input methods ([[QWERTY]], touch, normal) with different [[Computer hardware|hardware]] capabilities.
==Types of mobile application testing==
* '''[[Functional testing]]''' ensures that the [[Mobile app|application]] is working as per the requirements. Most of the tests conducted for this is driven by the [[user interface]] and call flow.
* '''Laboratory testing''', usually carried out by [[Mobile network operator|network carriers]], is done by simulating the complete [[wireless network]]. This test is performed to find out any glitches when a [[Mobile app|mobile application]] uses voice and/or data connection to perform some functions.
* '''[[Software performance testing|Performance testing]]''' is undertaken to check the performance and behavior of the [[Mobile app|application]] under certain conditions such as low battery, bad network coverage, low available memory, simultaneous access to the [[Mobile app|application]]'s server by several users and other conditions. Performance of an [[Mobile app|application]] can be affected from two sides: the [[Mobile app|application]]'s server side and client's side. [[Software performance testing|Performance testing]] is carried out to check both.
* '''Memory leakage testing''': [[Memory leak|Memory leakage]] happens when a computer program or [[Mobile app|application]] is unable to manage the memory it is allocated resulting in poor performance of the [[Mobile app|application]] 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 [[Mobile app|application]]
* '''Interrupt testing''': An [[Mobile app|application]] while functioning may face several interruptions like incoming calls or network coverage outage and recovery. The different types of interruptions are:
:* Incoming and outgoing [[SMS]] and [[Multimedia Messaging Service|MMS]]
:* Incoming and outgoing calls
:* Incoming notifications
:* Battery removal
:* Cable insertion and removal for data transfer
:* Network outage and recovery
:* Media player on/off
:* Device power cycle

:An [[Mobile app|application]] should be able to handle these [[Interrupt|interruptions]] by going into a suspended state and resuming afterwards.

* '''[[Usability testing]]''' is carried out to verify if the [[Mobile app|application]] is achieving its goals and getting a favorable response from users. This is important as the usability of an [[Mobile app|application]] is its key to commercial success (it is nothing but [[Usability|user friendliness]]).<ref>((Cite web|title = StickyMinds ((!)) How the Usability Matrix of Emotions Can Benefit Your Software Testing ((!)) Page 1|url = http://www.stickyminds.com/article/how-usability-matrix-emotions-can-benefit-your-software-testing|website = StickyMinds|accessdate = 2015-10-29))</ref> Another important part of usability testing is to make sure that the [[user experience]] is uniform across all devices.<ref>((Cite web|title = What is User Experience?|url = http://whatusersdo.com/clients/resources/what-is-user-experience|website = WhatUsersDo|accessdate = 2015-10-31|first = Lena|last = Contractor))</ref> 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 [[user interface]] on different devices.<ref>((Cite web|title = Mobile UX Issues Caused by Device Fragmentation|url = http://blog.testmunk.com/mobile-ux-issues-caused-by-device-fragmentation/|website = Testmunk Blog|accessdate = 2015-10-31))</ref>
* '''[[Installation testing]]''': Certain [[Mobile app|mobile applications]] come [[Pre-installed software|pre-installed]] 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 [[Mobile app|application]]
* '''Certification testing''': To get a certificate of compliance, each mobile device needs to be tested against the guidelines set by different [[Mobile operating system|mobile platforms]].
* '''[[Security testing]]''': Checks vulnerabilities to [[Hacking (computing)|hacking]], authentication and authorization policies, data security, session management and other security standards.<ref>((Cite web|date=2019-07-16|title=Mobile App Testing Techniques and Tools|url=https://mindster.com/mobile-app-testing-techniques-tools/|url-status=live|archive-url=https://web.archive.org/web/20210102172907/https://mindster.com/mobile-app-testing-techniques-tools/|archive-date=January 2, 2021|access-date=2021-01-02|website=Mindster|language=en-US))</ref>
* '''Location testing''': Connectivity changes with network and location, but you can't mimic those fluctuating conditions in a lab. Only in Country((clarify|date=June 2019)) non-automated testers can perform comprehensive usability and functionality testing.
* '''Outdated software testing''': Not everyone regularly updates their operating system. Some [[Android (operating system)|Android]] users might not even have access to the newest version. Professional testers can test outdated software.
* '''[[Load testing]]''': 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.<ref>((Cite web|title = Mobile App Testing ((!)) Services Issues ((!)) Page 1|url = http://www.globaltelecomtesting.com/mobile-app-testing-services.php|website = GTT|accessdate = 2016-03-22))</ref>
* '''[[Black-box testing]]''': Where the [[Mobile app|application]] is tested without looking at the [[Mobile app|applications]] [[code]] and [[Logic programming|logic]]. The tester has specific [[test data]] to input and the corresponding output that the [[Mobile app|application]] should produce, and inputs the [[test data]] 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: [[Unit testing|unit]], [[Integration testing|integration]], [[System testing|system]] and [[Acceptance testing|acceptance]].
* '''[[Crowdsourced testing]]''': In recent years, crowdsourced testing has become popular as companies can test [[Mobile app|mobile applications]] 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 [[Mobile app|mobile applications]] 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 [[Application software|application]], this is more likely to find issues faced by users under real world conditions.<ref>((Cite news|url=http://qualitrix.com/mobile-application-testing|title=Mobile Application Testing using Managed Crowd Sourcing|date=2017-02-06|work=Qualitrix.com|access-date=2017-03-14|language=en-US))</ref><ref>((Cite news|url=https://www.qualitylogic.com/2017/10/26/6-major-pitfalls-crowdsourced-software-testing/|title=6 Major Pitfalls of Crowdsourced Software Testing - QualityLogic|date=2017-10-26|work=QualityLogic|access-date=2018-02-14|language=en-US))</ref>

==References==
((reflist))

[[Category:Mobile software development]]
[[Category:Software testing]]
[[Category:Mobile phones]]

Pages transcluded onto the current version of this page (help):

Mobile application testing (edit)
Template:Ambox (view source) (template editor protected)
Template:Category handler (view source) (protected)
Template:Cite news (view source) (protected)
Template:Cite web (view source) (protected)
Template:Clarify (view source) (template editor protected)
Template:Delink (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Fix-span (view source) (template editor protected)
Template:Fix/category (view source) (protected)
Template:Format (edit)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Multiple issues (view source) (template editor protected)
Template:Multiple issues/styles.css (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Template:Space (view source) (protected)
Template:Spaces (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:DecodeEncode (view source) (template editor protected)
Module:Delink (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:String (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Mobile application testing.

Retrieved from "https://en.wikipedia.org/wiki/Mobile_application_testing"