A Mobile Application Testing Community
Compatibility testing - its really important and challenging too, (sharing here what difficulties I have faced in this approach )
1. Compatibility testing -
a. Testing in different screen size -
When I started android app testing there were mostly 4 or 5 set of popular device resolution.
but nowadays every brand releasing android devices and I am seeing some new set of screen size (bigger display)
In Blackberry If you ignore below 4.6 os devices, you will find arround
8 or 9 set of device resoultion. In their new os 7 they have introduced 4 new
set of resoultion
At least we have simulator in BB, so we can test here but what about android ?
Even we dont have a free tool also. If you go for a free trial version of a paid
tool , you will find out dated devices :)
2. Os
Android as I have seen I am not getting much defects because of os versions (Not sure of ICS os)
BB - Developer has to give seperate builds for 4.6 os , 5.0 os, and 6.0 os
because API present in Higher os is not present in lower versions so we need
to test seperately
3. Carrier Compatibilty - This is most difficult thing I have faced
I am not getting Is the defect because of app or n/w strength. ( Developer
may argue that app is proper its due to n/w strength :) ),
When I conduct performance metrics on cell n/w I need to take at least 3 or 4 readings to take the avg reading, as
n/w strength differs and eveing n/w will be very slow.
In our working place we may not get the range for all carriers.
Some times client may report a defect in a specific device in cell n/w.
Even if u have emultor/ simulator how will you put SIM in that ???
If your game supports only 3G, even if u put 3G SIM, if 3g strength is week it will take
2G so what will you do ?
4. Touch / non touch devices - Blackberry introduced their first touch device in 5.0 os
now android also has device with qwerty keypad
So this things also we need to take care
-----------------------------------------------
Tips - You should be ready with one sheet which is having popular devices, screen size and os
version details , i/p methods (one sheet for one os). Check your apps supported os/display/ i/p method
Select the popular devices (hit device like in BB - 9900, 9700, 8520 ) in your list based on the criteria then do testing.
Suggestions and corrections are most welcome
Thanks and Regards,
Divya
Comment
Comment by Divya on February 29, 2012 at 2:17pm Vishal, thanks for the valuable feedback :)
>> Last thing I want to share, when you are going
to test any app or Game for mobile/wireless device,
it should be tested thoroughly on real device instead
of any simulator or cloud device.
-- Agreed but as we wont be having that much devices on hand, we have to go for
simulator/cloud options
Comment by Vishal Kishor Sakharkar on February 29, 2012 at 1:51pm Hi Divya,
Tips - You should be ready with one sheet which is having popular devices, screen size and os
version details , i/p methods (one sheet for one os). Check your apps supported os/display/ i/p method
Select the popular devices (hit device like in BB - 9900, 9700, 8520 ) in your list based on the criteria then do testing.
Yes Divya, your all four points are valid and every qa faced those while testing. But we need to make some pre-requisites before testing any App or Game. Those can be:
1. Confirm and make the list of Technology you are supporting.
BB
Android
iOS
2. Make the Resolution list according to technology you are supporting, like BB, iOS and Android.
e.g.
BB - 320x240
360x480
480x800
(The above are latest screen resolutions for BB)
3. Make your own checkist points for Keypad, Touch and Touch n' Type device and clasify it.
4. OS version may differs in BB, but we have to test the app in every OS version if requirement is there.
5. Run the valid Testing Criteria for each technology.
The above things can be help you to sort out the confusion in compatibility testing.
@ Vaibhav: - Great Sharing.
Creation of Compatibility Test Suite :- Compatibility testing should not involve more than 10% of your regression test suite. i.e. if you have 100 test cases in your regression suite then 10 or max 15 test cases should be there in compatibility test suite.
Please elaborate this point, becasue I havn't tested any app or game via Automation.
Last thing I want to share, when you are going to test any app or Game for mobile/wireless device, it should be tested thoroughly on real device instead of any simulator or cloud device.
Make correct if I went wrong.
Regards,
Vishal.
Comment by Divya on February 29, 2012 at 10:39am Thanks Mani, Anurag,
Vabhiav, valuable info u have provided , thanks a lot :)
Regards,
Divya
Good Info!Thanks Vaibhav,Divya!
Hi Divya,
Excellent write up. My 2 cents on this is as below -
Creation of Compatibility Test Suite :- Compatibility testing should not involve more than 10% of your regression test suite. i.e. if you have 100 test cases in your regression suite then 10 or max 15 test cases should be there in compatibility test suite.
Features to be tested in Compatibility Test Suite :- As we have already completed functional testing, in turn there should not be any transcational based testing i.e. if its Banking app then deposit/ withdrawal.
Testing should be carried out around specific to UI features, device specific feature (e.g. Back Button in BB and Back Button in Android and only one key on iOS devices).In UI feature, you can differantiates apps pages as Tier 1 pages, Tier 2 pages etc. Tier 1 pages (page which gets max hits by user ) should be excellent fit for all devices.
Color code of the pages should be uniform through all the devices.
Getting the right set of Devices for Testing :- From your user base, you need to select the top devices
Biggest challange is to get the devices on desired carrier, we use to face such sceanrio in each product release. Only way to overcome this is Go for cloud based solutions. (where Cost matters ).
As per my knowledge, Perfecto is the only cloud based provider which gives devices on Indian carrier. DA doesnt.
Hope this helps. Please correct if something is wrong.
Thanks,
Vaibhav
Comment by nagendhran mani on February 27, 2012 at 5:47pm good information......
Comment by Divya on February 27, 2012 at 4:47pm For android, If you want to check the app is compabitiobile wid various devices, you can use
testdroid cloud tool
DeviceAnywhere replied to sandeep's discussion Documents For Device Anywhere
Punith replied to Punith's discussion Mobile Hanset/Device/Phone Testing (Features)
DeviceAnywhere is now friends with sandeep, Anand, Sandeep and Ravikumar Devatagal more
K K posted a group
Divya liked Swapna Kulkarni's discussion How to mock location on Android Emulator by using DDMS and KML file© 2012 Created by Anurag Khode.
You need to be a member of Mobile QA Zone to add comments!
Join Mobile QA Zone