1. typically<br />Getting Started with Mobile Apps Testing<br />July 29, 2011 — anuragkhode <br />“I am new to Mobile Testing. Please let me know how to get started?”, “I am working in website testing & needs to switch to mobile testing, please suggest me how to proceed in this field.” Well, I always encounter such questions on “Mobile QA Zone” and “Mobile Application Testing”. For most of the newbie in this field, these are some of the important questions, which will define their further progress in this arena. So without wasting any time, let us move forward from this “Zero Mile” of Mobile Apps Testing. <br />Please find here some tips, which may help you progress in the field of Mobile Application Testing.<br />Basics of Software Testing:- <br />Whether you are an experienced or a fresher in this field, knowledge of Software Testing basics is essential in any kind of testing you perform. Even if you are starting your carrier as a Mobile Apps Tester, you need to know all the software testing principles, Software Testing Techniques, Types of Software Testing, Objective of Testing and other basics in Software Testing. There are many sites and resources available on internet, which can guide you about the same. If you are just starting your carrier in this field, don’t bother to accumulate all the complicated theories of software testing in your mind at once. Go step-by-step. It is strongly recommended to undergo some good training program in software testing which can give you some practical experience of testing. Please avoid mugging complicated testing theories.<br /> 2. Basics of Telecom:- <br />As you have decided to work in Mobile Domain, knowing the Telecom basics will always give you an added advantage. Mobile Apps Testing is not just about testing of mobile product or application. You will surely get an advantage if you are aware of other things in this domain which revolves around Mobile products testing. 2G, 3G, CDMA, GPRS, GSM, HSCSD, SIM, SMS, WAP are some basic things of telecom that you should be aware of. You can check out some more details about the same here .<br /> 3. Awareness about Mobile OS/Platforms:- <br />There are many Mobile OS/Platforms present in the market. Android, iOS( iPhone), Blackberry OS(RIM), J2ME, Symbian, Palm, Windows phone, Samsung Bada , Nokia Meego and so on. It is very important to have knowledge about these Mobile OS/Platforms as a Mobile Apps Tester. Awareness about the capabilities and limitations of these platforms give you confidence to differentiate application bug with platform/OS limitations. You may find some more details about Mobile Operating Systems here .<br /> 4. Get familiar with your own Mobile Phone:-<br />I am sure many of you must not even be completely aware of which Mobile Handset model you are using, what is the OS in it and what is the software version your phone is having. If you are a beginner, just start exploring your own cell phone. Just open up and try using internet on your Smartphone. Use Wi-Fi, GPRS. Check out how you can format or perform Factory reset on your device (Be careful).Check what is the IMEI number of your phone. Try to upgrade OS version of your Android device. Experiment with different settings and user permissions on your phone. In short, be familiar with all the features and functions of your mobile handset and it will surely help you to dig out more scenarios while testing any mobile app or any mobile Handset you are given to test .<br /> 5. Get aware of Testing in Mobile Domain:- <br />When we talk about testing in Mobile domain, it is not only confined to Mobile Apps, but also includes mobile handset and mobile website testing.<br />Downloadable Mobile Application Testing: – Some applications come pre-installed in mobile handset while some mobile applications are downloadable from different mobile application stores(Apple App store, Android Market, Getjar, Nokia Ovi Store, Blackberry App world etc.). Apart from conventional Functional and UI testing, you may need to test your application against the submission criteria and guidelines provided by these Application stores. As said earlier, tester’s role here should not be only functional testing of mobile app, but also to make sure your application adheres to the guidelines provided by these mobile app stores.<br />Mobile Handset Testing:-Similar to Organizations that develop third party downloadable mobile applications, there are many companies that develop complete mobile handset. A mobile QA here may need to test native applications or features that are available in the phone. SMS, MMS, Voice Call, MMS, Phonebook, Calculator, Bluetooth and other mobile features. It also includes Multimedia (Camera, Video, Media player, ringtones) and Mobile Protocol stack testing.<br />Mobile Website Testing (WAP Sites):-Unlike downloadable mobile applications, mobile websites can be accessed via browser. No download involved. Testing of Mobile WAP sites has its own challenges. Proper navigation, good user interfaces (design), security, performance and mobile browser compatibility are important areas. <br /> 6. Get Aware of Types of Mobile Apps Testing:-<br />Similar to general Software Testing, Mobile Software Testing also includes:-<br />User Interface Testing (Color scheme, Menu styles, Consistency of UI over various Devices)<br />Functional Testing (Testing core functionality of Mobile App as per specification)<br />Performance & Stress Testing [Behavior of Mobile Application in Low resources(Memory/Space), Behavior of mobile website when many mobile user simultaneously access mobile website)]<br />Usability Testing (Testing of usability aspects of Mobile Apps)<br />Apart from above mentioned testing types, some key testing types may include the following.<br />Testing for Compatibility:-Testing the compatibility of your application with native device features (i.e. To make sure your application is not hampering native device functionality)<br />Certification Compliance Testing:-For downloadable mobile applications, there are various Third party Mobile Quality Certification program for various platforms. True Brew Testing(for BREW Apps), Java Verified program (for J2ME apps), Symbian Signed Test Criteria (for Symbian Apps) are some examples. Apart from regular functional testing, you may need to test your application against the test cases/Testing criteria provided by these certification processes. However, it depends on your client, whether they want to certify their application or not.<br />Submission Guidelines Compliance Testing: – The application needs to adhere to the specified submission guidelines to publish it in any mobile application store. Failure to meet these guidelines may result in rejection of your app on mobile application stores. For example failure to comply with application Submission guidelines for Apple App Store may result in rejection of your app in Apple app store.<br />Interruption Testing (Voice Calls, SMS, Charger, Low memory Notification) while application is running.<br />Monkey Testing: – Continual key pad entries via tools to test application stability with various key press events.<br />Low Network/No Network case Testing: – Application behavior when there is no network coverage or Low network strength.<br /> 7 . Go through the Sample Test Cases for Mobile Application:-<br />For newbie in Mobile Testing, it is always advisable to go through some sample test cases for Mobile Apps. Going through the test cases for any mobile application, gives a complete insight of the kind of testing conducted for Mobile Application. You may ask your seniors to provide you some Test Suites for any mobile project your organization completed earlier. However, you can still go through some general Test Cases for Mobile application here.<br /> 8. Explore the Capabilities of Simulator:-<br />Simulators always play big role when there are no mobile devices available for testing. Though Device testing is always preferred as it represents more likely end user scenarios, the importance of simulators cannot be ignored. In order to have effective testing over Simulator, It is recommended to explore all the capabilities of Simulator.<br /> 9 . Take Help from Remote Device Access Service-<br />Due to a large number of devices available in the market, it is not feasible to buy a new device every time. At the same time Simulators are not completely reliable enough to launch a mobile app based on testing conducted only on simulators. RDA (Remote device services) can be a good solution to deal with these challenges. The remote device access services enable access to a live device over the Internet. As a Mobile Apps Tester, you should be aware of such services and should suggest your managers about the capabilities of such Services.<br />Some Available RDA Services are:<br />Device Anywhere (Paid)<br />Perfecto Mobile (Paid)<br />Nokia RDA (Free, For Symbian Phones)<br />Advantages of RDA:<br />You don’t need to purchase actual device.<br />User can select different Carriers e.g. Verizon, T-Mobile, AT & T.<br />RDAs are more reliable than simulators as they are real devices.<br />Some RDA Service like Device Anywhere also has automation capabilities.<br />Disadvantages of RDA:<br />Since you access devices remotely it takes time for any action or key event.<br />Sometimes the needed device is not available due to prior reservations.<br />Higher Service Cost<br /> 10 . Explore Tools and Utilities:-<br />There are many software tools and utilities available in the market which may help you in testing of your Mobile Application effectively. Some of these tools are available in SDKs itself. However you may still dig out the internet for such tools on various platforms.<br />Tools to check Battery Consumption while your app is running. E.g. Nokia Energy Profiler.<br />Tools/Software to capture screenshot: – There are many tools available for various mobile platforms to capture screenshot from device itself. E.g Screenshot tool for Symbian S60 Devices.<br />Tools to Generate dummy files to test behavior of mobile app at Low EFS. e.g. Maxfilecnt utility from QUALCOMM for BREW mobile apps,Fill Device Memory Lite for Android apps.<br />Tools to Generate Random key events. e.g. Monkey tool(Android), BREW Grinder(BREW), Hopper Test Tool (Windows Mobile)<br />Tools to Capture Logs. E.g. Apphance for Android.<br /> 11. Explore Automation Tools for Mobile:-<br />Along with Manual Mobile Testing, be ready to explore your potential in Mobile Automation Testing as well. Mobile Testing is a new field and many automation tools are coming in to market gradually. If you get any opportunity to work on any mobile automation tool, it is well and good. But if you don’t get such opportunity, it is better to explore on your own. Don’t wait for the time when you will get an opportunity to work on Mobile Automation Tool. Believe me, sooner or later you will definitely face a question from your Interviewer- “Have you worked on any Mobile automation tool ? ”<br />Here are some automation tools available for Mobile Apps Testing:-<br />TestComplete<br /> M-Eux<br />TestQuest Countdown<br />Test Quest Pro<br />Robotium<br />VNC<br />Sikuli<br />Deviceanywhere<br />FoneMonkey (iPhone)<br />Eggplant (iPhone)<br />TestiPhone( For iPhone Mobile Web)<br />IBM® Rational® Performance Tester (RPT)<br />3P Mobile<br />Expertest<br />MITE (A Mobile content testing and validation tool for Mobile Web app)<br /> 12 . Explore Communities, Forums, Blogs :-<br />Even if you work for 24 hours a day in exploring various aspects in this arena, I guarantee even 24x 7×365 will not be enough. The reason is very simple. You cannot get opportunities to work in each and every area of this domain and by that time you manage to do that, you will find that there are many more things left to learn. Finally Technology is changing everyday and in Mobile Domain, even at faster pace <br />Hence the solution is to join Communities & forums to learn from each other’s knowledge and experiences. Initiate the discussions and you will find there are many QAs sharing their experiences.<br />Here are some Sites and links in mobile testing arena which may prove helpful to you.<br /> Mobile Application Testing Blog<br />Mobile QA Zone-A Mobile/Tablets Testing Community<br /> Nokia Forum<br />Mobile Test Automation Group<br />Mobile Apps Testing-Linked In Group<br /> Android Testing Group<br />Iphone Mobile Testers Group<br />Mobile Test Automation Tools Group<br />In our upcoming articles, all these topics will be elaborated and we will take a closer look on all the aspects of Mobile Apps Testing in details.Till then Stay tuned.:)<br />Hey…one more thing…I would like to connect with you all…if you wish the same then:-<br />Follow me on Twitter:-@anuraagrules, HYPERLINK quot;
http://twitter.com/quot;
quot;
%21/mobileapptestquot;
quot;
Mobile Application Testing on Twitterquot;
@mobileapptest,@mobileqazone<br />Join Me on Linkedin:- Anurag Khode, Mobile Apps Testing(Mobile QA Zone)<br />Like us on Facebook:-Mobile Application Testing, Mobile QA Zone<br />Join Me on Mobile QA Zone:- Anurag Khode on Mobile QA Zone<br /> <br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Mobile Application Testing. Tags: How to do Mobile Application Testing, Mobile Software Testing, Mobile Software Testing Tutorial. 3 Comments »<br />“Mobile QA Zone” collaborates with “Tea-time with Testers”‏‏<br />July 4, 2011 — anuragkhode <br />After my announcement of collaboration between UTI and MQZ for providing feedback on UTI documents, let me declare yet another candid sync up between our very own Mobile QA Zone and an International Monthly on software Testing i.e. Tea-time with Testers.<br />You all are already aware of our work as MQZ, let me tell you more about Tea-time with Testers (for those who don’t know yet) . “Tea-time with Testers” is an outcome of efforts taken by its Editor and Co-Founder Mr.Lalitkumar Bhamare accompanied by Mr.Pratikkumar Patel who happens to be another key person and Co-founder of this brilliant venture.<br />The reason I decided to go ahead with “Tea-time with Testers” is the true passion they have for software testing which is completely selfless.Their very first edition was launched in February 2011 and to my surprise, with launch of its 5th issue (June 2011 issue) Tea-time with Testers has reached up to 57 Countries in the world. Isn’t that a mind blowing ?<br />This magazine has become talk of the Global Testing Community for its quality, content, design, liveliness and many other original ideas which are solely focused on benefit of every tester across the corner.<br />In every single issue of Tea-time with Testers, you’ll realize that it has everything that one Tester may need.<br /> Articles from Testers across the globe and thereby ensuring the integrity of testers which is very much needed.<br /> Thought provoking articles along with articles which teach us the craft of Testing.<br /> ”Blogger of the Month” and “Smart Tester of the Month” awards to encourage young and fresh Testers to let them thrive in Global Testing Community.<br /> Testing Puzzles, Tickle your QA Bone sections are really mind blowing and one can’t just go ahead without leaving a smile <br />Mr.Lalit approached me and asked join the wagon and guide their readers in separate column dedicated to “Mobile Application Testing”. When I asked, “Why Mobile Apps?” the answer given by him made me confident about their foresight and that very moment I decided to take their offer.<br />Am happy to announce myself as an Assistant Editor of “Tea-time with Tester” where I will be writing my thoughts around “Mobile Application Testing”. I look forward to see Tea-time with Testers and Mobile QA Zone flourishing together by our honest and sincere efforts and of course with the very much needed support from you all.<br />Feel free to SUBSCRIBE this brilliant magazine right away. Oh YES ! Its FREE !!! <br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Mobile Application Testing. Tags: Mobile Software Testing, Mobile Software Testing Community. 1 Comment »<br />Reasons Why Mobile Apps Need Testing<br />December 14, 2010 — anuragkhode <br />Guest Post By- Ed Thomas<br />For any mobile app developer hoping to produce a top quality mobile application, app testing is an essential part of the app development process. Here are several reasons for getting your application tested by a mobile app testing professional before its consumer release:<br />Check the Basic User Experience<br />After designing and developing a mobile app you will need it to be tested by a group of eager mobile users. This simply requires the application to be test run in it’s simplest form – fully using the app for it’s intended purpose. Users at this testing stage should be asked to give feedback on the complete user experience and record any glitches they discover. Screenshots can be extremely useful at this point, and if the app in question is iPhone based there is no excuse for making the most of the screen capture function.<br />Test Navigation<br />Whilst basic user testing may bring awareness to navigation problems, computer based app testing is the most accurate way of checking full app navigation. This process will check all menu functions are correctly working and that both internal and external links are accurate.<br />Test System and Negative Usage<br />By performing app tests, a developer can accurately determine how your application will function in various conditions. Testing the apps reactions to system changes such as low memory or low battery as well as putting the application up against negative challenges such as malicious attacks.<br />Check for Hidden Defects<br />If all is well with the general user experience of your app, there could still be hidden issues that could cause sporadic performance or later problems. These defects are found through both software and hardware tests and are only completely detectable through professional services.<br />Check Connectivity<br />Many iPhone apps rely on internet connectivity in some form or another after original download (even if just for updates). Monitoring how a mobile app functions in conditions of low internet connectivity or mobile signal is a very important stage in mobile app testing and will ensure that any problems formed during app development can be corrected before release.<br />Test Audio Functionality<br />Another area which needs to be tested is the apps ability to interact with various audio settings on different handsets. App details including audio and vibrate feedback (when a sound or buzz plays on a touch) also need to be thoroughly checked to eliminate any future glitches.<br />Author: Ed Thomas has a wide expertise in the field of apps development and website development. He is one of the reputed app developers UK and shares his expertize through his scholarly articles.<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Mobile Application Testing. Tags: Mobile Application Testing, mobile apps testing, Mobile Software Testing, Mobile Testing. 1 Comment »<br />Mobile Application Testing at a Glance<br />December 2, 2010 — anuragkhode <br />Bringing you Mobile Application Testing topics in this blog at a glance for you.<br />Automated testing of Windows Mobile applications<br />Testing Checklist for Mobile Applications<br />Nokia Test Criteria for J2ME Applications<br />Symbian Signed Test Criteria and Test cases<br />Complete Guide to Hoffman Box Testing in BREW<br />Test Plan for a mobile applications<br />Mobile Operating System<br />How to run J2ME applications on devices<br />Testing Mobile Applications with HP QTP<br />Mobile Application Testing With TestComplete – Overview<br />Mobile Web application testing<br />Mobile application testing challenges<br />List of companies developing mobile games and apps<br />Introduction to J2ME Emulators<br />10 Things You Need to Know About Mobile Apps<br />How to install a Windows Mobile emulator<br />How to use Windows Mobile Emulator<br />Nokia N-95 8GB<br />Mobile Application Testing or Mobile Testing,Confused????<br />5 Things to keep in mind before starting Mobile Application Testing<br />Nokia N-900<br />Samsung Corby S3650<br />Lessons for Testing Mobile Services and Applications<br />While testing data calls in J2ME mobile application<br />Automation Testing Tools for Mobile Applications<br />How to conduct Application Stability test in BREW Mobile Application<br />National Software Testing Laboratories (NSTL)<br />How to Install Symbian Application in Device ?<br />What is IMEI Number ?<br />Finding iPhone Memory Leaks: A “Leaks” Tool Tutorial<br />How to Submit your BREW Mobile Application To NSTL<br />List of Mobile Network Operators In India and World<br />Performance testing mobile web applications using IBM Rational Performance Tester<br />Seesmic for Android<br />Google Mobile Application:Google Voice<br />FoneMonkey:Free Mobile Application Testing tool for iphone apps<br />How the mobile service providers know whether the mobile is switched off or out of coverage?<br />Quick Testing Tip:Blackberry Mobile Application Testing<br />Security Testing for Mobile Applications<br />Automated testing of Blackberry applications with QTP<br />Be a Guest Blogger on www.mobileappstesting.com<br />What is Handset Bluetooth testing?<br />Symbian Signed Tests Cases v 4.0.14<br />Smart Phone OPERATING SYSTEMS<br />AUTOMATED GUI TESTING OF MOBILE JAVA APPLICATIONS<br />How to use hopper-A stress testing tool for windows mobile!<br />List of Sites for All BREW Handsets and Specs<br />Mobile Application Platform most used by mobile developers in early 2010<br />Automated testing of Android applications<br />Test your Mobile Application on Nokia RDA<br />Performance Testing: Getting Your Ecommerce and Mobile Web Ready for Peak Holiday Traffic<br />TestiPhone-A web browser based simulator for testing iPhone web apps<br />MITE (Mobile Interactive Testing Enviornment)<br />Testing iPhone Applications with eggPlant<br />Join “Mobile QA Zone” a nextGen Mobile Software Testing Comminity<br />Interview Question on Mobile Application Testing<br />Testing a Mobile Application with “Test Maker”<br />Test your mobile application for unnecessary excessive data calls<br />MOBILE QA ZONE<br />Join Mobile Software Testing Community Mobile QA Zone<br />Join Android Testing Group in Mobile QA Zone<br />Join Iphone Testing Group on Mobile QA Zone<br />Join Blackberry Testing Group on Mobile QA Zone<br />Join Future in Mobile Technology Group on Mobile QA Zone<br />Watch Videos on Mobile Application Testing on Mobile QA Zone<br />Meet and Interact with More than 300 Mobile Application Testers all over the world on Mobile QA Zone<br />Meet and interact with Anurag Khode on Mobile QA Zone <br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Mobile Application Testing. Tags: Mobile Application Testing, Mobile QA Zone, Mobile Software Testing, Mobile Software Testing Community, Mobile Testing. 1 Comment »<br />Test your mobile application for unnecessary excessive data calls<br />November 16, 2010 — anuragkhode <br />Testing a Mobile Application makes you think on different aspects of a mobile application.Excessive data call can also be considered as one of the pretty good test case while testing a Mobile Application.It can be a case when your Mobile Application in doing good in its working and functionality but still a user don’t want to use it.The reason behind it would may be your mobile application is making unnecessary request(which could have been prevented) which is annoying your user.<br />A Mobile Developer should keep in consideration this case while developing a mobile application that his application is not making unnecessary data call where it is not required.As a Mobile Quality Analyst, along with conventional validations and verification testing it is very important to look in to such kind of scenarios which can surely impact on overall success of that application in the market.<br />When your mobile application is making unnecessary data calls where it is not required, directly or indirectly you are making your users to pay a bit more for your application/or services.Also when you make such requests, some times you are making user to wait for that action to complete in which user is really not interested.<br />So now onwards whenever a new mobile application is coming to you for testing,apart from conventional test cases try to to think on this aspect also.<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Mobile Application Testing. Tags: Mobile Application Testing, Mobile Software Testing, Mobile Testing, Software Testing. 1 Comment »<br />Interview Question on Mobile Application Testing<br />October 25, 2010 — anuragkhode <br />Interview Questions on Mobile Application Testing!!!…well I know very well, many of you must have been in search of this thing since so long.Starting from a beginner in this domain to an expert, everyone is very keen to know what are the different question they may come across in there interview.Here in my post I have shared some interview questions which me or my friends have come across in there interviews for the post of Mobile Software Testers.I hope this will help you:-<br />What is the difference between Mobile Testing and Mobile Application Testing ?<br />What is your approach while Testing Mobile Applications?<br />Have you ever written a Test Plan?What are the things specific to Mobile Application would you emphasis on while writing test plan for Mobile Applications?<br />Do you know Facebook?Tell me what are the High level test cases for Facebook Web Application and for Facebook Mobile Application?<br />Can you please let me know,the devices you have worked upon?<br />Testing of Mobile Application on Emulators.Can you let me know your view?<br />Have you ever worked on any automation tool for Testing Mobile Application?<br />Please tell me about your project.What kind of Mobile Applications have you worked upon?<br />Do you have Idea about Mobile Operating Systems?<br />Blackberry Devices have which Operating system?<br />What is current iOS (iphone OS) version?<br />You have two cases. 1st you can not disconnect your call and 2nd you can not send SMS from your devices.Tell me Severity and Priority in both the cases?<br />What are different Mobile Platforms/OS?<br />What are the different way you can install a Mobile Application?<br />Have you ever worked on Device Anywhere?Do you have experience of working on it?<br />Do you have Idea about application certification program like True Brew Testing(TBT),Symbian Signed Test Criteria,Java Verified Program?<br />See this application(Interviewer is given a Handset with a Mobile Application installed).Tell me what are the bugs in this Mobile application/Game.?<br />Have you ever worked on LBS Application ?<br />How will you test a Location Based Mobile Application?<br />How will you perform Performance Testing for a Mobile Application?<br />Well there are lot more Mobile Application Testing Interview Questions to be added.I will incorporate rest of the questions in My Next Post.Till then Have a Nice Time :)<br />Adding some more Quetions provided by our Reader Mr.rajendra prasad reddy<br />Some mobile handset,messaging related, GPS related questions:-<br />Can you name some performance testing tool.<br />Can you explain some file format for multimedia testing (audio and video)<br />How to write bluetooth the test case for stress, give me 20 example.<br />Explain the WAP protocol stack.<br />Explain the type of testing you have done in mobile application testing.<br />How basic phone is different from smart phone in testing perspective<br />Which android version you tested ?<br />Write few scenarios for any feature in a mobile phone other than browser.<br />Do you know about android?<br />Explain the Architecture of android<br />Load Testing on Mobile and Web application.<br />Test conditions for touch screen mobiles(landscape and portrait).<br />Explain about the mobile application project that you worked in previous company?<br />How you did performance testing for mobile application in your previous organization.<br />Can you name some performance testing tool. 12 What do you understand by Multimedia testing in mobile devices.<br />What is mobile memory leakage, have you tested that?, which tools have you used.<br />On which mobile u have tested the browser?<br />Types of devices tested during mobile application testing?<br />writing high level scenario’s for any mobile features(I selected Calling)<br />Different types of DRM<br />What is combined delivery?<br />Is it possible to transfer seperate delivery contents to memory card then to other phone?<br />can we open seperate delivery files, if we have rights and contents copied from memory card?<br />what different types of browser contents tested?25.Any idea of SDK?<br />Any idea of VPN?<br />Explain the type of testing you have done in mobile application testing.<br />How GPRS works?<br />How GPS works internally.<br />What is GPS how did you tested<br />About GPS and A-GPS.<br />Write test cases on Camera feature.<br />That are the mobile platforms you worked on?<br />What is Android and what are the extra features in Android?<br />A mobile number contains 10 digits, which kind of method you follow to test a mobile number on a telephone keypad?<br />What is Bluetooth and how you test them?<br />what is the extension of android application?<br />Explain abt tools used in Mobile Handset Testing.<br />How to test SMS, MMS and what is Class1, class2 message.<br />Test cases for Alarm , Settings , Media player , Browser , Bluetooth ?<br />On which mobile u have tested the browser?<br />What all the GSM mobile you have tested?<br />Bug Tracking Tool – JIRA<br />What are the BT profiles, give some examples.<br />What BT profiles supported in Froyo and not supported in Eclairs.<br />What is the MMS size and is it network dependent ?<br />Latest version of OMA DRM<br />when message with 500 character sent what happens<br />Write any five test cases for Messaging Subsystem?<br />What kind of mobile application i have tested?<br />What do you understand by Multimedia testing in mobile devices.<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Interview Quetions. Tags: Interview Question on Mobile Application Testing, Mobile Software Testing. 24 Comments »<br />Testing a Mobile Application with “Test Maker”<br />October 17, 2010 — anuragkhode <br />Here is another automation tool for Mobile Applications, “TestMaker” from PushToTest Inc.TestMaker is solutions for testing mobile and web application.It provides record/playback, unit testing, and data driven testing solutions.It also provides telephony protocol handlers to rapidly build test suites.<br />According to “Push To Test” Sprint and Bell Aliant have adopted this solution for there mobile testing needs.Well this is the reason also why I am sharing this tool with you.I have not adopted this tool for yet so I keep it up to you to have a look on this tool and to see whether it satisfies your Mobile Testing Need.<br />For more details and download of this tool visit:-<br />http://www.pushtotest.com/mobiletesting<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Mobile Application Testing, Mobile/Handset Testing. Tags: Mobile Application Testing, mobile apps testing, Mobile Automation Testing, Mobile Software Testing, Mobile Testing. 2 Comments »<br />Testing iPhone Applications with eggPlant<br />September 22, 2010 — anuragkhode <br />Sharing with you just another automation tool for iphone as “Eggplant”. As per Testplant Inc.,with the help of eggplant and simulator you can pretty good test your iphone application. As I have not explored this tool I would not prefer to comment on its working and feasibility to test iphone applications, but I just thought to share this new thing with you. You can follow the following link for more details and yes do not forget to give me a feedback on this tool and your experience <br />Testing iPhone Applications with eggPlant<br />Try demo for Eggplant<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Iphone Application Testing, Mobile Application Testing, Mobile application Testing and Automation tools. Tags: iphone automation testing, iphone Testing, Mobile Automation Testing, Mobile Software Testing, Mobile Testing. 1 Comment »<br />Android Test Cases (Android Testing Criteria)<br />Hey Friends,<br />As shared with you all earlier,UTI(Unified Testing Initiative) have released one testing criteria for Android Application just few months back.The android test criteria will provide you a complete testing criteria/test cases for your Android Application.I suggest you all to just go through this document and make these test cases an integral part of your Test Suite.I hope this will definitely help you to deliver a Quality Android Mobile Application.You can download Android test criteria from here<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Android Application Testing, Test Cases. 6 Comments »<br />Symbian Signed Tests Cases v 4.0.14<br />April 15, 2010 — anuragkhode <br />Symbian Signed Tests Cases v 4.0.14<br />This version of the test criteria is in effect from 5th January 2010.<br />Reference: Symbian Signed Test Criteria<br />TEST 1 — InstallationTEST STEPSBefore starting the test round, use a file manager to note the free user space available on the phone. You will need this information in test 8.1Install the application being tested.The application must install without error.2During installation note the version number presented to the user.The version number must match that specified during submission.3Verify that the application has successfully installed on the device by navigating to the area on the phone where new applications are installed.The application should present one or more icon(s) on the phone.NotesFor any submissions which do not appear obviously once installed, the submitter must include details in the submission statement of how successful installation can be verified.If the content does not appear obviously on the device once installed, and specific instructions are lacking in the submission statement, then this test will be failed.<br />TEST 2 – Application start/stop behaviourTEST STEPS1Start the application by selecting the icon or following the steps outlined in the submission statementNavigate to the Task Manager and check that the application appears there.2Close the application from the Task Manager.Exit the Task Manager, and re-launch the Task Manager.The application must no longer appear in the Task Manager.3Start the application as in Step 1.Go to the Task Manager to verify that the application is running.The application must appear in the task manager.4Close the application from within the application UI and then return to the Task Manager.The application must no longer be running and must no longer appear in the task manager.5Restart the application as in Step 1.Navigate to the Task Manager.The application must once again appear in the Task Manager.NotesAn application which must run in the background does not need to appear in the Task Manager or present a UI so long as the developer justifies this behaviour during submission.All applications must have some way of verifying that they are running on the device, though, and the developer should provide this information.<br />TEST 3 — Application credentialsTEST STEPS1With the application running, check the name of the application displayed on the phone.The application must display the same name on the phone as stated during submission.2Note the functionality of the application as it runs on the device.The basic functionality of the application must match that declared during submission.NotesStep 1 does not apply to applications which do not have a UIVoIP applications must present a UI in order to pass this test.<br />TEST 4 — No disruption to voice callsTEST STEPS1With the application installed and running use a second phone to call the test device.The incoming call must be indicated to the user on the test device.2Answer the call on the test device.You must be able to conduct a conversation with the other party without interference from the application being tested.3End the call in the normal way on the test device.The voice call must be ended.4From the test device, make a call to a second phone. Answer the call from the other device.The call must be indicated on both devices, and you must be able to conduct a conversation with the other party without interference from the application being tested.5End the voice call from the second device.The call must be ended on both devices.6Place a test call to the emergency 112 number from the device.*Please check in your territory for the approved way to make test calls to the emergency services.NotesIf the application being tested has the MultimediaDD capability, and has audio functionality, then that functionality must be in use whilst this test is performed. Particularly, it should be checked that the audio from the application is faded down to allow the user to hear the telephone call.VoIP applications will need this test running using both the handset held to the user’s ear and using a headset. The test should be run with a VoIP call in progress, and the incoming GSM call should be announced with call waiting tones.<br />TEST 5 — No disruption to text messagesTEST STEPS1With the application installed and running, send a text message to the test device.The incoming text message must be notified to the user as per their alert settings.2Read the text message on the test device and choose to reply. Send the reply.The reply must be received at the second device.3From the standby screen on the test device, navigate to the “new text message” option and create a new message. Send the message to the second device.The message must be received at the second device.<br />TEST 6 — Auto-start behaviourTEST STEPS1With the application running, find the settings for the application — either within the application itself or from the settings option on the device.There must be an option which allows the user to enable/disable auto-start functionality.2Ensure that the setting for auto-start behaviour is disabled, and restart the device.The application must not start on device boot.3Now change the setting so that auto-start behaviour is enabled for the application and restart the phone.The application must start when the phone boots.NotesIf the application does not have auto-start functionality, then this test does not need to be run.<br />TEST 7- No disruption to key device applicationsTEST STEPS1Ensure that the contacts, messaging and calendar applications are populated with data and start the application as in Test 2.After the application has been installed and used, the data entered into those applications must not be altered in any way without the user being aware.2With the application running, navigate to the messages application and create a new message.Save that message to the drafts folder and then open and edit it.Finally, delete the message from the drafts folder and delete a message from the inbox.All of the above actions should be possible without interference from the installed application.3Navigate to the contacts application.Create a contact, then edit that contact and then delete it.The application should not interfere with any of the actions above without notifying the user and giving them option to avoid the change.4Navigate to the calendar application.Create an appointment in the calendar. Edit the appointment and then delete it.The application should not interfere with any of the actions above without notifying the user and giving them option to avoid the change.5Use the web browser on the device to go to a web page which is known to work on the network being used.It must be possible to create a data connection and to access the web page selected.NotesIf the application, as part of stated functionality, makes changes to user data then an exception can be claimed here. The functionality must be described in the documentation with the application and all data other than that mentioned in the user guide must remain untouched as described in the test case.The data used in this test case is also needed for Test 8, so leave the data on the device when proceeding straight into Test 8.<br />TEST 8 — Un-installTEST STEPS1Stop the application as described in Test 2 and uninstall the application using the system installer.The application must be uninstalled without error.2Following the same steps as in Test 1, navigate to where you would expect to see the application icon.The application icon must not longer be present on the device.If you used another method to verify successful installation in Test 1 then use this method to ensure that the application has been uninstalled.3Check the contacts, messages and calendar applications to ensure that that the data present in Test 7 is still present in those applications.4Using the same file manager as at the start of Test 1 check that the amount of user space available on the device is either the same as that found in step 1 or that any difference between the space available before and after fulfils the following criteria.a) Excluding user-generated and downloaded content, the application leaves no more than 100Kb of data on the phone after uninstallb) Any data left on the device after install matches the explanation given during the submission processNotesYou should start this test with the application data from Test 7 still in place on the device.<br />TEST 9 — Device adaptationTEST STEPSNote: The following test steps should be run on the list of devices corresponding to the UIDs specified in the .pkg file.The lead device list can be found at http://tiny.symbian.org/devicetable1Install the application onto the deviceThe application should install on the device or present an error message to explain that it cannot install onto that device.2Launch the application.The application should run on the device or present an error message to explain that it cannot run on that device.3Briefly examine the application whilst running.UI elements should be functional and text should be readable in the main screen of the application.4If the device on which the application is currently being tested supports portrait and landscape screen modes, start the application and then switch between the screen modes.The application should continue to be functional, and usable, in both screen orientations of the device, whether or not the application rotates in response to the screen mode change.5Close the application from the application UIThe application should stop running.6Uninstall the application from the phone.The un-installation should happen without error and the application must be un-installed.NotesApplications which do not present a UI to the user in normal usage do not need to run this test.On the primary device — on which all of the other test cases have been run – only step 4 of this test should be performed as all of the other steps of this test case are covered elsewhere.<br />Additional Tests for VoIP applications<br />Note that Test 3 and Test 4 both contain additional notes which apply to the testing of VoIP applications. Please read and apply these notes when running those tests on VoIP applications.<br />Test 10 — Additional emergency call testing for VoIP appsTEST STEPSNote: These test steps should be performed twice — once with a SIM card in the device and once without.1With the VoIP application running in the background, but with no VoIP call in progress, initiate an emergency call in the usual way.The emergency call must be placed over the GSM/CDMA network successfully.2With the VoIP application running in the background with a VoIP call in progress, initiate an emergency call in the usual way.The emergency call must be placed over the GSM/CDMA network successfully and the VoIP call should be terminated or placed on hold.3With the VoIP application in the background, and an emergency call active make a VoIP call to the device.The incoming VoIP must be rejected, and the emergency call must not be interrupted.<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in Symbian Application Testing, Test Cases. 6 Comments »<br />Testing Checklist for Mobile Applications<br />October 23, 2009 — anuragkhode <br />By-Anurag Khode,Copyright 2009-10<br />No.ModuleSub-ModuleTest Case DescriptionExpected Result1InstallationVerify that application can be Installed Successfully.Application should be able to install successfully. 2UninstallationVerify that application can be uninstalled successfully.User should be able to uninstall the application successfully.3Network Test CasesVerify 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”4Verify 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.5Voice Call HandlingCall AcceptVerify 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.6Call RejectionVerify 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.7Call EstablishVerify 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.8SMS HandlingVerify that user can get SMS alert when application is running.User should be able to get SMS alert when application is running.9Verify 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.10Unmapped keysVerify that unmapped keys are not working on any screen of application.Unmapped keys should not work on any screen of application.11Application LogoVerify 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.12SplashVerify that when user selects application logo in application manager splash is displayed.When user selects application logo in application manager splash should be displayed.13Note that Splash do not remain for fore than 3 seconds.Splash should not remain for fore than 3 seconds.14Low MemoryVerify 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.15Clear KeyVerify that clear key should navigate the user to previous screen.Clear key should navigate the user to previous screen.16End KeyVerify that End Key should navigate the user to native OEM screen.End Key should navigate the user to native OEM screen.17Visual FeedbackVerify 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.18Continual Keypad EntryVerify that continual key pad entry do not cause any problem.Continual key pad entry should not cause any problem in application.19Exit ApplicationVerify 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.20Charger EffectVerify 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.21Low BatteryVerify 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.22Removal of BatteryVerify 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.23Battery ConsumptionVerify that application does not consume battery excessively.The application should not consume battery excessively.24Application Start/ Restart1. 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.25Application Side EffectsMake sure that your application is not causing other applications of device to hamper.Installed application should not cause other applications of device to hamper.26External incoming communication – infraredApplication 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.<br />Share this:<br />StumbleUpon<br />Digg<br />Reddit<br />Email<br />Facebook<br />Print<br />Posted in J2ME Application Testing, Mobile Application Testing, Test Cases. Tags: Test cases for Mobile Applications, Testing Checklist for Mobile Application. 24 Comments »<br />