cognizant 20-20 insights
Real-time Scenario or a Smartphone-based App: Sample Test Execution
Use Case 1Mobile ApplicationsUse Case 2Use Case n
Devices/BrowsersSky Fire Dolphiniphone3iphone4iphone5Nexus OneMoto DroidSamsungCaptivateHTC IncredibleNexus SMoto Droid XCurve 8330Tour 9630Bold 9650Bold 9000 TouchiOS Native3,4&5Android Native(2.1,2.2,2.3, 3.0,4.0)Blackberry Native5,6 ,7,8 & 9Opera MiniFirefox 4 Firefox 5 Firefox 6OperaMobile 11.1
M o b i l e T e s t L a b
Two Key Challenges in MobileApplication Test Automation
Mobile Platorms and Technology Coverage
The primary factor that determines an automationtool’s success is its ability to work across platformsand technology stacks. The following challengesinuence automation success:
Multiple platforms and browsers.
Mobile devices with varied application runtimes.
Multiple network types (e.g., GSM/GPRS/Wi-Fi/Wi-Max).
Different speeds of connectivity acrossgeographies.
Multiple network operators with custom-ized network features.
Limitations in processing speed.
Limitations of mobile memory size.
Differences in device communicationprotocols (e.g., WAP/HTTP).
Test Execution Challenge
Test execution across different devices and brows-ers is a huge, challenging effort. For example,consider a test case that is created and needs tobe executed on three different platforms — iOS,Android and Blackberry. In this example, the testcase is expected to be executed on 13 differentdevices and in 10 different combinations, whichleads to 130 rounds of testing. Designing a testexecution matrix of this scope is both difcult andtime-consuming (see Figures 1 and 2).
Mobile Testing Industry Opportunities
In the growing mobile market, the need for spe-cialized mobile testing is growing. The followingthree opportunities contribute almost 80% oftotal market demand.
Mobile Automation Testing
There are only a handful of tools available to suc-cessfully automate testing. The ROI promised byautomation testing highlights the need for moreoptions.
Mobile functional testing always involves a non-heuristic component that cannot be automated.
Mobile Perormance Testing
Compared with a desktop/notebook environment,mobile device system resources (e.g., processingpower, memory, etc.) are limited. Hence, perfor-mance testing of mobile applications is crucial.Therefore, this domain is growing and has greatpotential.