Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Mobile testing

1,771 views

Published on

The realm of mobile computing is composed of various types of mobile devices and their underlying software. Enabling or writing new software for mobile phones, or portable devices has become a new vertical in software development and testing. Smart phones are getting user-friendlier and day-to-day, new apps are being released to satisfy daily user needs. More and more user-friendly apps enable greater user interactions using stylus, touch-based gestures, multi-touch gestures, motion gestures etc. These introduce lot of challenges in development and testing. This document details the approach for mobile testing and the key focus areas for testing.

Published in: Technology
  • Be the first to comment

Mobile testing

  1. 1. MOBILE TESTING –FOCUS AREASSathyan SethuMadhavanThoughtworks
  2. 2. APPS  Browser Apps   Applications runs on the browser  Pre-Installed Apps   ROM’s , OEM apps, SDK apps  Installable Apps   Custom developed apps available in the market
  3. 3. NEXT GEN DEVICES  GPS  (Assisted) GPS  4G/3G/Wi-Fi Internet Access  Touch screen interface  Camera  Compass  Accelerometer
  4. 4. CHALLENGES  Minimal support with test automation tools  Application are starting to be location aware  Integration of live apps  Competition between similar apps  Address Time – To – Market  Maintain state of the apps – Random interactions  Device limitations and ‘N’ configurations
  5. 5. FOCUS AREAS Local awareness andContent Rendering Navigation Haptic Feedback live integration Resource Behavior,consumptions(CPU, Performance and Interruptions Install / Upgrade Memory, Battery) Stability
  6. 6. SPECIFICS ContentRendering   Alignment and Corners   Content display during flip and rotate   Multi-touch gestures (Zoom, Pinch, Long Pinch etc)   Rendering of plugins in browser   Streaming of videos   Target common user base (short fingers, long fingers etc)
  7. 7. SPECIFICSNavigation   Take advantage of learned behaviors   Avoid interaction inconsistencies   Provide clear conceptual links across widgets   Plan for accidental incidents   Don’t relay completely on multi-touch   Provide interaction affordances
  8. 8. SPECIFICS LocationAwareness andLive Integration   Integration with maps   Integration with GPS and AGPS   Integration with social networking apps (Facebook, Twitter etc)   Ensure proper data sync mechanism between integrated applications   More+++ of exploratory testing - User Interactions
  9. 9. SPECIFICSFeedback / Haptic Feedback   Provide visual / physical feedback   Help to avoid repeated actions   Add haptic feedback for accidental taps
  10. 10. SPECIFICSResourceUtilization   Battery - Run in background, run in foreground, run app for long time.   Memory - Run in background, run in foreground, run app for long time.   Battery- Run in background, run in foreground, run app for long time
  11. 11. SPECIFICS Behavior,Performanceand Stability   Network strength - No network to high   Network speed - Low to high (wifi, 3g)   Network Switching – Wifi to 3G   Battery strength - low to high , during charging   Random shutdown
  12. 12. SPECIFICSInterruptions   Screen Lock   New Installation   Receive voice call   Receive SMS, MMS, Email or Notification   Take a photo   USB connection   SD card removal
  13. 13. SPECIFICS Install/Upgrade   Receive via Wireless (OTA)   USB cable upgrade   Existing data/user preferences
  14. 14. ADDITIONAL HAT SME BA UX QA DEV
  15. 15. CONSIDERRequirements * Screen, User and Input Based * Natural Interactions * Easy to remember and perform * Socially acceptable * Not activated by casual actions * Richly connected apps * Navigation requirements
  16. 16. CONSIDERDevelopment * Design non-expert actions * Separate Presentation and Business * More of unit tests -Validate Algorithms * Unit tests - Apps integrations * Consider possible interactions * Conduct frequent user-experience bash * Unit tests for continuous events * Unit tests for multi-user , parallel interactions
  17. 17. CONSIDER * More of ExploratoryTesting * Possible Interactions * Haptic Feedback * Measure Responsiveness * Typical and accidental issues * Unintended Gestures * Each app is different * Resource Consumption * Less support - Emulator based testing * Clear Boundary between SDK and apps functionalities
  18. 18. AVAILABLE TOOLS Iphone Andriod •  Fonemonkey •  Robotium •  Frank •  Dalvik Debug Monitoring Server •  Egg Plant – Image Compare (DDMS) •  Memory Sweep – Memory Snapshot •  Port Forwarding Service •  Screenshots – Home and Lock key •  Screen capture on device •  Thread and heap information •  Logcat •  Process and radio state information •  Incoming call and SMS spoofing •  Location data spoofing and more •  Monkey Tool and Runner •  Hierarchy Viewer
  19. 19. Q &ASATNAIR@THOUGHTWORKS.COM

×