{"status":"ok","message-type":"work","message-version":"1.0.0","message":{"indexed":{"date-parts":[[2026,7,13]],"date-time":"2026-07-13T01:13:27Z","timestamp":1783905207904,"version":"3.55.0"},"reference-count":29,"publisher":"Association for Computing Machinery (ACM)","issue":"6","license":[{"start":{"date-parts":[[2013,11,11]],"date-time":"2013-11-11T00:00:00Z","timestamp":1384128000000},"content-version":"vor","delay-in-days":0,"URL":"https:\/\/www.acm.org\/publications\/policies\/copyright_policy#Background"}],"content-domain":{"domain":["dl.acm.org"],"crossmark-restriction":true},"short-container-title":["SIGSOFT Softw. Eng. Notes"],"published-print":{"date-parts":[[2013,11,11]]},"abstract":"<jats:p>Mobile apps are everywhere. Some apps entertain and others enable business transactions. Apps increasingly interact with complex IT landscapes. For example, a banking app on a mobile device acts as a front end that invokes services on a back-end server of the bank, which might contact even more servers. Mobile testing becomes crucial and challenging. This paper follows a user-centric testing approach. The app's architecture matters for testing, as does its user base and usage context. Addressing these factors ensures that test cases cover all relevant areas. Most apps need test automation for two reasons: agility and compatibly. Agile projects test frequently, such as every night, to detect bugs early. Compatibility tests ensure that an app runs on all relevant devices and operating system versions on the market. Thus, testers execute test scripts on many devices. This demands for a private device cloud and a mobile test automation framework. Swisscom IT Services followed this path, enabling us to address the major quality issues we identified for mobile apps: pre-usage failures (installation fails, app crashes during startup) and lack of basic regression testing (upgrades buggier than predecessor).<\/jats:p>","DOI":"10.1145\/2532780.2532813","type":"journal-article","created":{"date-parts":[[2013,11,27]],"date-time":"2013-11-27T14:13:59Z","timestamp":1385561639000},"page":"1-8","update-policy":"https:\/\/doi.org\/10.1145\/crossmark-policy","source":"Crossref","is-referenced-by-count":17,"title":["Mobile Testing"],"prefix":"10.1145","volume":"38","author":[{"given":"Klaus","family":"Haller","sequence":"first","affiliation":[{"name":"Swisscom IT Services, Z\u00fcrich, Switzerland"}],"role":[{"vocabulary":"crossref","role":"author"}]}],"member":"320","published-online":{"date-parts":[[2013,11,11]]},"reference":[{"key":"e_1_2_1_1_1","unstructured":"http:\/\/en.wikipedia.org\/wiki\/Smartphone  http:\/\/en.wikipedia.org\/wiki\/Smartphone"},{"key":"e_1_2_1_2_1","volume-title":"Agile Record","year":"2013"},{"key":"e_1_2_1_3_1","article-title":"Co-opting Customer Competence","author":"Prahalad C.K.","year":"2000","journal-title":"Harvard Business Review"},{"key":"e_1_2_1_4_1","volume-title":"Thomson Learning","author":"Graham D.","year":"2008"},{"key":"e_1_2_1_5_1","unstructured":"S. Wellmann: 2007. Google Lays Out Its Mobile User Experience Strategy. Information Week April 11 http:\/\/www.informationweek.com\/mobility\/business\/google-laysout-its-mobile-user-experien\/229216268 last retrieved April 9 2003.  S. Wellmann: 2007. Google Lays Out Its Mobile User Experience Strategy. Information Week April 11 http:\/\/www.informationweek.com\/mobility\/business\/google-laysout-its-mobile-user-experien\/229216268 last retrieved April 9 2003."},{"key":"e_1_2_1_6_1","unstructured":"http:\/\/developer.android.com\/tools\/devices\/emulator.html  http:\/\/developer.android.com\/tools\/devices\/emulator.html"},{"key":"e_1_2_1_7_1","unstructured":"http:\/\/www.experitest.com\/  http:\/\/www.experitest.com\/"},{"key":"e_1_2_1_8_1","unstructured":"http:\/\/www.perfectomobile.com\/  http:\/\/www.perfectomobile.com\/"},{"key":"e_1_2_1_9_1","unstructured":"http:\/\/developer.samsung.com\/remotetestlab  http:\/\/developer.samsung.com\/remotetestlab"},{"key":"e_1_2_1_10_1","volume-title":"White Paper","year":"2012"},{"key":"e_1_2_1_11_1","unstructured":"Selenium Web Driver. http:\/\/docs.seleniumhq.org\/projects\/webdriver\/  Selenium Web Driver. http:\/\/docs.seleniumhq.org\/projects\/webdriver\/"},{"key":"e_1_2_1_12_1","unstructured":"Robotium. http:\/\/code.google.com\/p\/robotium\/  Robotium. http:\/\/code.google.com\/p\/robotium\/"},{"key":"e_1_2_1_13_1","volume-title":"Dpunkt Verlag","author":"Seidl R.","year":"2011"},{"key":"e_1_2_1_14_1","unstructured":"http:\/\/en.wikipedia.org\/wiki\/Access_Point_Name  http:\/\/en.wikipedia.org\/wiki\/Access_Point_Name"},{"key":"e_1_2_1_15_1","unstructured":"Digi Connect\u00ae Application Guide Cellular IP Connections (Uncovered) 2005  Digi Connect\u00ae Application Guide Cellular IP Connections (Uncovered) 2005"},{"key":"e_1_2_1_16_1","doi-asserted-by":"publisher","DOI":"10.1145\/1808266.1808267"},{"key":"e_1_2_1_17_1","doi-asserted-by":"publisher","DOI":"10.1109\/AST.2007.9"},{"key":"e_1_2_1_18_1","doi-asserted-by":"publisher","DOI":"10.1145\/1138929.1138952"},{"key":"e_1_2_1_19_1","doi-asserted-by":"publisher","DOI":"10.1109\/IWAST.2012.6228987"},{"key":"e_1_2_1_20_1","doi-asserted-by":"publisher","DOI":"10.4018\/jitwe.2006010103"},{"key":"e_1_2_1_21_1","volume-title":"Florida Institute of Technology","author":"Jha A. K.","year":"2007"},{"key":"e_1_2_1_22_1","doi-asserted-by":"publisher","DOI":"10.1109\/TSE.2003.1265525"},{"key":"e_1_2_1_23_1","doi-asserted-by":"publisher","DOI":"10.1145\/1999732.1999740"},{"key":"e_1_2_1_24_1","first-page":"1","article-title":"Usability Testing of Mobile Applications: A Comparison between Laboratory and Field Testing","volume":"1","author":"Kaikkonen A.","year":"2005","journal-title":"Journal of Usability Studies, Issue"},{"key":"e_1_2_1_25_1","unstructured":"Testing experience -- Special Issue on \"Mobile App Testing \" September 2012  Testing experience -- Special Issue on \"Mobile App Testing \" September 2012"},{"key":"e_1_2_1_26_1","unstructured":"R. F. Alvarez: Testing on Real Handset vs. Testing on a Simulator -- the big battle testing experience September 2012  R. F. Alvarez: Testing on Real Handset vs. Testing on a Simulator -- the big battle testing experience September 2012"},{"key":"e_1_2_1_27_1","unstructured":"D. Knott: Best Practices in Mobile App Testing testing experience September 2012  D. Knott: Best Practices in Mobile App Testing testing experience September 2012"},{"key":"e_1_2_1_28_1","unstructured":"J. Jacob M. Tharakan: Roadblocks and their workaround while testing Mobile Apps testing experience September 2012  J. Jacob M. Tharakan: Roadblocks and their workaround while testing Mobile Apps testing experience September 2012"},{"key":"e_1_2_1_29_1","unstructured":"K. Rayachotti: Mobile Test Strategy testing experience September 2012  K. Rayachotti: Mobile Test Strategy testing experience September 2012"}],"container-title":["ACM SIGSOFT Software Engineering Notes"],"original-title":[],"language":"en","link":[{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2532780.2532813","content-type":"unspecified","content-version":"vor","intended-application":"text-mining"},{"URL":"https:\/\/dl.acm.org\/doi\/pdf\/10.1145\/2532780.2532813","content-type":"unspecified","content-version":"vor","intended-application":"similarity-checking"}],"deposited":{"date-parts":[[2025,6,18]],"date-time":"2025-06-18T20:22:06Z","timestamp":1750278126000},"score":1,"resource":{"primary":{"URL":"https:\/\/dl.acm.org\/doi\/10.1145\/2532780.2532813"}},"subtitle":[],"short-title":[],"issued":{"date-parts":[[2013,11,11]]},"references-count":29,"journal-issue":{"issue":"6","published-print":{"date-parts":[[2013,11,11]]}},"alternative-id":["10.1145\/2532780.2532813"],"URL":"https:\/\/doi.org\/10.1145\/2532780.2532813","relation":{},"ISSN":["0163-5948"],"issn-type":[{"value":"0163-5948","type":"print"}],"subject":[],"published":{"date-parts":[[2013,11,11]]},"assertion":[{"value":"2013-11-11","order":2,"name":"published","label":"Published","group":{"name":"publication_history","label":"Publication History"}}]}}