Quick Testing Tip:Blackberry Mobile Application Testing

Sharing with you just a small tip which I just came to know while testing a mobile application on Blackberry Curve.Actually i was just testing my application tvider and was facing with some exceptions.However when I was just about to log A issue I was always in fond answer of question “What was that exception(crash) text exactly???”
And literally after few days I got to know very interesting thing.
Whenever you face any exception on your Blackberry device and you just have to take a look on that issue and also you need to have some information about it,just hold Alt key on your blackberry and type lglg .

By this you are navigated to a page where all the exception/warning your app may have undergone.
Basically this is called event log screen.

You can also get information about that exception here.
This tip has helped me, I hope it will help you too!!!!

Testing Checklist for Mobile Applications

No.	Module	Sub-Module	Test Case Description	Expected Result
1	Installation		Verify that application can be Installed Successfully.	Application should be able to install successfully.
2	Uninstallation		Verify that application can be uninstalled successfully.	User should be able to uninstall the application successfully.
3	Network Test Cases		Verify the behavior of application when there is Network problem and user is performing operations for data call.	User should get proper error message like “Network error. Please try after some time”
4			Verify that user is able to establish data call when Network is back in action.	User should be able to establish data call when Network is back in action.
5	Voice Call Handling	Call Accept	Verify that user can accept Voice call at the time when application is running and can resume back in application from the same point.	User should be able to accept Voice call at the time when application is running and can resume back in application from the same point.
6		Call Rejection	Verify that user can reject the Voice call at the time when application is running and can resume back in application from the same point.	User should be able to reject the Voice call at the time when application is running and can resume back in application from the same point.
7		Call Establish	Verify that user can establish a Voice call in case when application data call is running in background.	User should be able to establish a Voice call in case when application data call is running in background.
8	SMS Handling		Verify that user can get SMS alert when application is running.	User should be able to get SMS alert when application is running.
9			Verify that user can resume back from the same point after reading the SMS.	User should be able to resume back from the same point after reading the SMS.
10	Unmapped keys		Verify that unmapped keys are not working on any screen of application.	Unmapped keys should not work on any screen of application.
11	Application Logo		Verify that application logo with Application Name is present in application manager and user can select it.	Application logo with Application name should be present in application manager and user can select it.
12	Splash		Verify that when user selects application logo in application manager splash is displayed.	When user selects application logo in application manager splash should be displayed.
13			Note that Splash do not remain for fore than 3 seconds.	Splash should not remain for fore than 3 seconds.
14	Low Memory		Verify that application displays proper error message when device memory is low and exits gracefully from the situation.	Application should display proper error message when device memory is low and exits gracefully from the situation.
15	Clear Key		Verify that clear key should navigate the user to previous screen.	Clear key should navigate the user to previous screen.
16	End Key		Verify that End Key should navigate the user to native OEM screen.	End Key should navigate the user to native OEM screen.
17	Visual Feedback		Verify that there is visual feedback when response to any action takes more than 3 seconds.	There should be visual feedback given when response time for any action is more than 3 second.
18	Continual Keypad Entry		Verify that continual key pad entry do not cause any problem.	Continual key pad entry should not cause any problem in application.
19	Exit Application		Verify that user is able to exit from application with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.	User should be able to exit with every form of exit modes like Flap,Slider,End Key or Exit option in application and from any point.
20	Charger Effect		Verify that when application is running then inserting and removing charger do not cause any problem and proper message is displayed when charger is inserted in device.	When application is running then inserting and removing charger should not cause any problem and proper message should be displayed when charger is inserted in device.
21	Low Battery		Verify that when application is running and battery is low then proper message is displayed to the user.	When application is running and battery is low then proper message is displayed to the user telling user that battery is low.
22	Removal of Battery		Verify that removal of battery at the time of application data call is going on do not cause interruption and data call is completed after battery is inserted back in the device.	Removal of battery at the time of application data call is going on should not cause interruption and data call should be completed after battery is inserted back in the device.
23	Battery Consumption		Verify that application does not consume battery excessively.	The application should not consume battery excessively.
24	Application Start/ Restart		1. Find the application icon and select it 2. “Press a button” on the device to launch the app. 3.Observe the application launch In the timeline defined	Application must not take more than 25s to start.
25	Application Side Effects		Make sure that your application is not causing other applications of device to hamper.	Installed application should not cause other applications of device to hamper.
26	External incoming communication – infrared		Application should gracefully handle the condition when incoming communication is made via Infra Red [Send a file using Infrared (if applicable) to the device application presents the user]	When the incoming communication enters the device the application must at least respect one of the following: a) Go into pause state, after the user exits the communication, the application presents the user with a continue option or is continued automatically from the point it was suspended at b) Give a visual or audible notification The application must not crash or hung.

Experitest releases FREE FOREVER SeeTestManual for any android device

Experitest Ltd (www.experitest.com) the leading provider of mobile testing tools has released today a FREE FOREVER SeeTestManual tool for any Android device that makes manual testing easy and fast.


The SeeTestManual free edition enables to test any real android device connected via USB or WiFi to your computer using your PC mouse and Keyboard.
- Manually test any real device using your PC
- Control the real physical phone via your PC
- Support for all multi touch events, buttons and text input







Download Now your FREE FOREVER SeeTestManual for Android:
http://experitest.com/manual/
Watch video:
http://www.youtube.com/watch?v=xL16ELs4Dt0&feature=plcp
Online help: http://experitest.com/studio/manualhelp/WebHelp/help.htm

Test mobile friendliness of your website

With the boom of Smartphones in the market and the availability of good data plans in the market across all carriers, lots of users have started using their mobile phone to access the websites for the information they needed. Yes you have a good website made for desktop and users can access it from their mobile phones also. But just loading websites in the phone is not enough for your users. There are many things which matters for users like the time to load the website, User interface, accessibility of various functions available on the website and so on.
GO MO is an initiative from Google which helps developers having a good mobile ready websites.

Google have also provided a quick tool GOMOMeter which helps you to analyze your website on mobile.The tool shows you how your current site looks on a Smartphone and provides a report on what’s working and what you can do better. User just needs to enter his website URL and needs to provide answers of some questions like:-

• Do you see broken images or missing content?
• Can you read the text without zooming or scrolling?
• Can links and buttons be clicked with a thumb?
• Is search functionality easily accessible?

Here is the example of small test I conducted for Facebook site.GOMO also provides a detailed report about your site.The sample report for Facebook Site can be found here

You can also take a look on Best Practices for Mobile Sites on GO MO website


Mentioned above are just key pointers.You can take a look on these best practices in details on GO MO website.:)