Monday, December 6, 2010

Classification of Devices as per mobile platform(s)


As the number of devices is vast as per corresponding platforms, testing on all the available devices in the market would not feasible and so need to go for classification of devices.

Devices can be classified as per various features/specifications even on a particular platform:
  • Family wise devices
  • Screen Resolutions
  • OS versions
  • Nature of keypad
  • Nature of Device
 
Ø      By classifying the devices into various available families of devices, we would be able to generalize the compatibility of the app across multiple families of same platform of devices.

Ø      By classifying the devices into all the various screen resolutions of the platform, we would be able to be assured of the compatibility of the app across multiple screen resolutions in terms of UI and display which is the main and primary critical factor.

Ø      By classifying and identifying the devices of all the various OS versions of same platform, we can make sure that we are trying to cover all the supported and available devices of various OS versions.

Ø      By classifying and identifying the devices of various natures of keypads – as in Standard, QWERTY, Touch keypads, we can check for the keying in of the text in the app, as some apps pose issues with QWERTY and Touch keypads.

Ø      By classifying and identifying the devices of various natures of devices – as in Low end device, High end device, Smart device, Touch device, Touch/Qwerty, Slider etc.., we can make sure that we are trying to cover all the device models.

By grouping the devices as per the above specifications; we can select few devices which cater to all the specifications and can assure that the app would work fine for the remaining devices of the same specifications.

Monday, November 29, 2010

The Challenges faced when testing mobile apps

Testing a mobile app is very similar yet different from testing any web based application. At the heart of it, testing the two would follow the STLC yet scope/number of platforms on which the two are tested draws them apart. Normally, to test a web application, the scope of testing is confined to limited browsers; whereas while testing a mobile app, the scope is enormous and varies according to the platform the app supports. Categorizing this as a challenge that a Mobile App Tester faces, here are few more that I would like to share in the same context:

  • Testing the app on all the physical devices that it supports may not be feasible at all the times due to various constraints and has to be hence prioritized.
  • A strategic approach to testing mobile solutions takes into account a number of characteristics unique to the mobile platform and supported OS.
  • Ideally, the functionality of the app or the user experience is expected to remain consistent across multiple devices of similar/varying platforms. Hence compatibility of the app to these becomes critical, calling the need of the app to be tested across multiple devices/platforms the app supports.
  • And in some cases, there might be chance of inconsistency in terms of functionality across multiple devices of same platform.
  • Even though you are testing on same platform, there might be discrepancies across multiple OS versions of devices.
  • GPRS connectivity would be inconsistent and mostly very bad during the peak hours (mostly 6-10pm), which may lead to inconsistent results.
  • As we cannot test on all physical devices, sometimes we may end up testing on simulators, on which we cannot rely completely.
  • The increased and continuous launch of new devices into market

Inception


Mobile space, in contemporary times is at the center of corporate growth strategy irrespective of the industries, target customers or regions they are catering to. Emerging trends and rapidly changing rules of the game are keeping testers like me on our toes, pushing us to keep ourselves up breast with the latest trends and patterns. Through this blog, I intend to share my learning and my 2 cents to this immense and dynamic field which is equally exciting.

Also the frustration which has been creeping in me since few months has ignited towards writing the blog. I would like to thank all the people/circumstances/situations which made me frustrated, and with out this; I would not have been able to start writing.

And last, but not the least, I would like to thank Anurag Khode who has inspired me in writing this blog and Ashwin Maru, my technical editor & Rupal Der, who is the editor of the blog in regards to the language support.