Contents 10- Things You Need to Know About Mobile Apps.............2 Reasons Why Mobile Apps Need Testing...........................

4 Mobile Application Testing Challenges..............................6 5-Things to keep in mind before starting Mobile Application Testing..........................................................8 Symbian Signed Tests Cases v 4.0.14...............................9 Testing Checklist for Mobile Applications........................17 Test Plan for a mobile applications.................................22 How to setup Android SDK on Linux ubuntu....................28

References
Anurag Khode - Quality Analyst at Umundo Inc Ed Thomas Manish Phegade(Technical Associate) & Sangram Desai (Sr. Technical Associate) Source-WIKI Forum Nokia Source:-http://www.qcubicle.com/mobile-testing/mobile-application-testing-challenges/

10- Things You Need to Know About Mobile Apps
The Internet Advertising Bureau (IAB) has put together a list of 10 things everyone should know about mobile applications, or at least, it’s got 10 of its members to think of one each. We’re happy to share their advice with you… 1. Only do apps when you need more Compared to browsing, mobile apps offer a richer level of user interaction, allowing more complex graphics, media and information to be presented. They also provide a more robust and secure environment for user engagement. But, if you can deliver what you are trying to achieve through a browser, you will be able to reach far more consumers. Jeremy Copp, CEO, Rapid Mobile Media Ltd 2. Tell people about your app Don’t just rely on app stores; you can distribute apps via mobile sites, operators and through multiple ad placements and formats for maximum impact and reach. Theo Theodorou, EMEA Sales Manager, Mobile Advertising, Microsoft Advertising 3. Think further than the iPhone The iPhone offers fantastic functionality for developers and users alike, and apps developed for the platform are eminently PR-able, and are often shared virally. It has a fast growing user base, and reaches relatively wealthy 25-44 year olds, who actively use mobile media very well. But also developing a java version, optimised to work over a wide range of handsets, including BlackBerrys, will give you a far greater potential reach. Mark Angell, Business Development Director, Marvellous 4. Get the balance right There are two fundamental balances to achieve.

Firstly, business objectives versus user needs: for the application to be effective, the business needs must carefully consider the user, as well as commercial objectives. Secondly, the three E’s (Engagement, Entertainment and Effectiveness): functional apps often outlast the usage of entertainment-based apps. Paul Taylor, Strategist & Planner, COI 5. Consider the average app user There are 8.7 million people who have used a downloaded app in the UK, which is 18% of mobile users. 60% of these users are playing games that they have downloaded. The median age of an app user is 32 years old, and 43% are female. 36% of app users own Smartphones, compared to 15% of the total market. Alistair Hill, Analyst and Mobile Products, Europe, comScore 6. Brand-building versus sales Free applications get the most downloads, whereas paid-for applications generate revenue. Knowing whether you are branding or selling is a key point when launching your first application. Ross Butler, Creative, Parrott and Miller 7. Product longevity is essential Every service needs a roadmap, no matter how basic. Customers will quickly get bored with a unifunctional app which has no new features or capability added over time. By adding functionality as time goes on, you can create brand advocacy. Christian Harris, CEO, Gorillabox 8. Send them in the right direction Ads in existing applications are a great place to advertise, but make sure that the destination site is optimised for mobile. If it isn’t, then you risk low conversion and a poor perception of your brand. Jonathan Abraham, Brand Sales Director, AdMob 9. Test, test and test again If a customer can access it on their handset it needs to work. If it doesn’t, it will do more damage than good to your brand. Invite feedback, and always read customer reviews, to ensure you are meeting the needs of your consumer. Oliver Newton, Head of Emerging Platforms, i-level 10. Be on brand Just as with any form of communication, ensure that your app is ‘on brand’. Tone of voice, brand values, message, production values and brand fit are essential in making a great brand application.

Test Navigation Whilst basic user testing may bring awareness to navigation problems. 3. 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. app testing is an essential part of the app development process. Check the Basic User Experience After designing and developing a mobile app you will need it to be tested by a group of eager mobile users. there could still be hidden issues that could cause sporadic performance or later problems. Test System and Negative Usage By performing app tests. computer based app testing is the most accurate way of checking full app navigation. 4. This simply requires the application to be test run in it’s simplest form – fully using the app for it’s intended purpose. 5. 2. Check for Hidden Defects If all is well with the general user experience of your app. Check Connectivity Many iPhone apps rely on internet connectivity in some form or another after original download (even if just for updates). Users at this testing stage should be asked to give feedback on the complete user experience and record any glitches they discover. Here are several reasons for getting your application tested by a mobile app testing professional before its consumer release: 1. 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. 6. These defects are found through both software and hardware tests and are only completely detectable through professional services. Test Audio Functionality .Reasons Why Mobile Apps Need Testing Guest Post By. and if the app in question is iPhone based there is no excuse for making the most of the screen capture function. This process will check all menu functions are correctly working and that both internal and external links are accurate. a developer can accurately determine how your application will function in various conditions. Screenshots can be extremely useful at this point.Ed Thomas For any mobile app developer hoping to produce a top quality mobile application.

Another area which needs to be tested is the apps ability to interact with various audio settings on different handsets. He is one of the reputed app developers UK and shares his expertize through his scholarly articles. . Author: Ed Thomas has a wide expertise in the field of apps development and website development. 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.

g. Content delivery bothers both mobile user and carrier as well. Most the web sites are designed for delivering content for desktop application.com/mobile-testing/mobile-application-testing-challenges/ Principal objective behind mobile application testing is to ensure best user experience. Image delivery should be in size range which device can handle without any burden. when content delivers with a bigger image size. when page size is large.qcubicle. Later will start testing application using emulators or simulators. . Factors affect mobile content delivery 1) Types of content 2) Network. Carrier. E. User type and device capabilities 3) Context in which the content is received 4) User Goals Mobile users typically have different interests to users of fixed or desktop devices. Image should be cropped or resized before it delivers to mobile device. Scrolling to read documents or web page will not be user friendly Another example is image handling capabilities Page UI will be broken or timeout error message displayed on screen.Mobile Application Testing Challenges Source:-http://www. Edge. device will not be able to handle it. Also page can divide into fragments and display in multiple pages. memory size etc. when access from mobile devices. More areas to consider while mobile Application testing • • Bandwidth – Carrier or device should be GPRS. The best practices of delivering Web content to mobile devices is process and deliver content by which user agent or devices. Their intentions are often to find out specific pieces of information that are relevant to their context. Mobile web application testing first will be done on web browser using various mobile device user agents.. They are likely to have more immediate and goal-directed intentions than desktop Web users. 3G or 4G compatible Mobile handset Capabilities like screen size. Notebook or for wide range of handheld devices. Web content should be delivered according to the mobile devices. Page should be cropped or resized and delivered without losing relevant information.

Entering long URL in mobile browser address bar for Module testing. which does not have Back button is even more interesting (will required a small R&D to find how user can navigate back). Consequently testing should be carried out in as wide a range of real devices and specific software versions as is practical. Input -Mobile device input capabilities like keyboard. in practice. . Few emulators does not support copy paste URL . Data transfer should be minimum while accessing pages. However. Many manufacturers provide emulators for their device that can provide a convenient preliminary means of testing. When your application is not carrier specific then testing become more challenging Carriers provide mobile handsets with customized preloaded applications or browser versions .Page layout or content will change when user access page in different screen modes Pop ups or redirection – Pop ups or redirection while doing testing is very annoying for users. • • • • Mobile application Testing Carry out testing on actual devices as well as emulators. Testing or Using an application on a device.This may internally again effect application performance and testing. This saves lot time in entering an URL in device browser.• Cost -Cellular network connectivity is commonly charged per data volume. touch screen etc Text input -Text input tends to be very slow and cumbersome on a mobile device Device screen flip capabilities.But luckily in Device Anywhere studio copy paste is possible. many of these emulators behave in a different way to actual devices they emulate.

For example if you have to test any media sharing application on Mobile just search for some other media sharing applications and observe its feature. business apps) there are some things that a Mobile Application Tester should go through for effective testing. Analyze the device related issues:. Use emulator but don’t completely trust it:. social networking. . 3.When it is deviced which are the target devices do not forget to have a look on device related known issues. Define the performance criteria:-For any mobile applications performance is one of the most important concern. In this case to save time you may try some test with your emulator so that this time will be utilized and overall time in testing will be reduced. Analyzing similar applications:. 2. 4. Keep your emulator ready for testing : Some times it takes times for processing any request for example for downloading any media files or for loading an page on device.Try to analyze some other application which are similar to your application.chatting tools. so it may happen you may miss some issue which comes in weak network on actual devices. Also in emulator response time is faster. Make sure you are having some performance parameters so that you will be testing the mobile applications against it. 5. This will help you understand which are the issues related to device and which are due to your application under test.While testing you may take help of emulator but please note that all the test cannot be performed in emulator. 1.5-Things to keep in mind before starting Mobile Application Testing Before starting testing any mobile applications (let it be . games. Since Memory is one of the constraints for mobile devices performance and behavior of your application under these conditions is interesting things to see.

Reference: Symbian Signed Test Criteria TEST 1 — Installation TEST STEPS Before starting the test round.Symbian Signed Tests Cases v 4.14 This version of the test criteria is in effect from 5th January 2010. During installation note the version number presented to the user. Verify that the application has successfully installed on the device by navigating to the area on the phone where new applications are installed. The version number must match that specified during submission. TEST 2 – Application start/stop behaviour TEST STEPS 1 Start the application by selecting the icon or following the steps outlined in the submission 1 2 3 .0. The application must install without error. and specific instructions are lacking in the submission statement. then this test will be failed. If the content does not appear obviously on the device once installed. Notes For any submissions which do not appear obviously once installed. You will need this information in test 8. The application should present one or more icon(s) on the phone. use a file manager to note the free user space available on the phone. the submitter must include details in the submission statement of how successful installation can be verified. Install the application being tested.

Notes An 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. Restart the application as in Step 1. check the name of the application displayed on the phone. TEST 3 — Application credentials TEST STEPS With the application running.statement Navigate to the Task Manager and check that the application appears there. Close the application from within the application UI and then return to the Task Manager. 3 Go to the Task Manager to verify that the application is running. 2 Exit the Task Manager. 5 Navigate to the Task Manager. All applications must have some way of verifying that they are running on the device. Close the application from the Task Manager. 4 1 . The application must once again appear in the Task Manager. The application must display the same name on the phone as stated during submission. and re-launch the Task Manager. Start the application as in Step 1. The application must no longer be running and must no longer appear in the task manager. The application must no longer appear in the Task Manager. The application must appear in the task manager. and the developer should provide this information. though.

The basic functionality of the application must match that declared during submission. From the test device. Place a test call to the emergency 112 number from the device. TEST 4 — No disruption to voice calls TEST STEPS With the application installed and running use a second phone to call the test device. 4 The call must be indicated on both devices. The voice call must be ended.2 Note the functionality of the application as it runs on the device. Answer the call from the other device. 1 3 5 . The call must be ended on both devices. and you must be able to conduct a conversation with the other party without interference from the application being tested. 2 You must be able to conduct a conversation with the other party without interference from the application being tested. End the voice call from the second device. make a call to a second phone. 6 *Please check in your territory for the approved way to make test calls to the emergency services. End the call in the normal way on the test device. The incoming call must be indicated to the user on the test device. Answer the call on the test device. Notes Step 1 does not apply to applications which do not have a UI VoIP applications must present a UI in order to pass this test.

TEST 5 — No disruption to text messages TEST STEPS With the application installed and running. then that functionality must be in use whilst this test is performed. The test should be run with a VoIP call in progress. 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. From the standby screen on the test device. navigate to the “new text message” option and create a new message. and has audio functionality. send a text message to the test device. The message must be received at the second device. and restart the device.Notes If the application being tested has the MultimediaDD capability. There must be an option which allows the user to enable/disable auto-start functionality. and the incoming GSM call should be announced with call waiting tones. Send the message to the second device. find the settings for the application — either within the application itself or from the settings option on the device. Particularly. 1 2 3 1 2 . The reply must be received at the second device. Read the text message on the test device and choose to reply. Ensure that the setting for auto-start behaviour is disabled. The application must not start on device boot. TEST 6 — Auto-start behaviour TEST STEPS With the application running. The incoming text message must be notified to the user as per their alert settings. Send the reply.

Navigate to the contacts application. The application should not interfere with any of the actions above without notifying the user and giving them option to avoid the change. then this test does not need to be run. The application should not interfere with any of the actions above without notifying the user and giving them option to avoid the change. then edit that contact and then delete it. With the application running. TEST 7. The application must start when the phone boots. navigate to the messages application and create a new message. 4 Create an appointment in the calendar. Notes If the application does not have auto-start functionality. Navigate to the calendar application. All of the above actions should be possible without interference from the installed application. Edit the appointment and then delete it. 2 Save that message to the drafts folder and then open and edit it. delete the message from the drafts folder and delete a message from the inbox. 3 Create a contact. messaging and calendar applications are populated with data and start the application as in Test 2. 5 Use the web browser on the device to go to a web page which is known to work on the 1 . 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. Finally.No disruption to key device applications TEST STEPS Ensure that the contacts.3 Now change the setting so that auto-start behaviour is enabled for the application and restart the phone.

network being used. Using 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. 3 4 Check the contacts. navigate to where you would expect to see the application icon. 2 The application icon must not longer be present on the device. Following the same steps as in Test 1. Notes If the application. as part of stated functionality. The application must be uninstalled without error. messages and calendar applications to ensure that that the data present in Test 7 is still present in those applications. It must be possible to create a data connection and to access the web page selected. The data used in this test case is also needed for Test 8. a) Excluding user-generated and downloaded content. TEST 8 — Un-install TEST STEPS Stop the application as described in Test 2 and uninstall the application using the system installer. the application leaves no more than 100Kb of data on the phone after uninstall 1 . If you used another method to verify successful installation in Test 1 then use this method to ensure that the application has been uninstalled. so leave the data on the device when proceeding straight into Test 8. 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. makes changes to user data then an exception can be claimed here.

and usable.org/devicetable Install the application onto the device 1 The application should install on the device or present an error message to explain that it cannot install onto that device.b) Any data left on the device after install matches the explanation given during the submission process Notes You should start this test with the application data from Test 7 still in place on the device. If the device on which the application is currently being tested supports portrait and landscape screen modes. Launch the application. The application should continue to be functional.symbian.pkg file. 4 5 . start the application and then switch between the screen modes. TEST 9 — Device adaptation TEST STEPS Note: The following test steps should be run on the list of devices corresponding to the UIDs specified in the . 2 The application should run on the device or present an error message to explain that it cannot run on that device. whether or not the application rotates in response to the screen mode change. Close the application from the application UI The application should stop running. 3 UI elements should be functional and text should be readable in the main screen of the application. in both screen orientations of the device. The lead device list can be found at http://tiny. Briefly examine the application whilst running.

but with no VoIP call in progress. The incoming VoIP must be rejected. initiate an emergency call in the usual way. The emergency call must be placed over the GSM/CDMA network successfully. Test 10 — Additional emergency call testing for VoIP apps TEST STEPS Note: These test steps should be performed twice — once with a SIM card in the device and once without. Please read and apply these notes when running those tests on VoIP applications. Notes Applications which do not present a UI to the user in normal usage do not need to run this test. The emergency call must be placed over the GSM/CDMA network successfully and the VoIP call should be terminated or placed on hold.6 Uninstall the application from the phone. With the VoIP application in the background. Additional Tests for VoIP applications Note that Test 3 and Test 4 both contain additional notes which apply to the testing of VoIP applications. With the VoIP application running in the background with a VoIP call in progress. With the VoIP application running in the background. and the emergency call must not be interrupted. 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. The un-installation should happen without error and the application must be un-installed. initiate an emergency call in the usual way. and an emergency call active make a VoIP call to the device. 1 2 3 .

back in action. Module 1 Installation SubTest Case Description Module Expected Result Verify that application Application should be able to can be Installed install successfully. Successfully. successfully. 6 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 . Call Verify that user can Rejectio reject the Voice call n at the time when application is running and can resume back in application from 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. there is Network Please try after some time” problem and user is performing operations for data call. Verify that application User should be able to can be uninstalled uninstall the application successfully. Verify the behavior of User should get proper error application when message like “Network error. 2 Uninstallation 3 Network Test Cases 4 5 Voice Call Handling Call Verify that user can Accept accept Voice call at the time when application is running and can resume back in application from the same point.Testing Checklist for Mobile Applications No. Verify that user is User should be able to able to establish data establish data call when call when Network is Network is back in action.

point. manager splash is displayed. it. Verify that unmapped Unmapped keys should not keys are not working work on any screen of on any screen of application. SMS Handling User should be able to establish a Voice call in case when application data call is running in background. reading the SMS. 9 10 Unmapped keys 11 Application Logo 12 Splash 13 . application. 7 Call Verify that user can Establis establish a Voice call h in case when application data call is running in background. Splash should not remain for fore than 3 seconds. running. Note that Splash do not remain for fore than 3 seconds. Verify that user can User should be able to resume back from the resume back from the same same point after point after reading the SMS.the same point. 8 Verify that user can User should be able to get get SMS alert when SMS alert when application is application is running. Verify that when user When user selects application selects application logo in application manager logo in application splash should be displayed. Verify that application Application logo with logo with Application Application name should be Name is present in present in application application manager manager and user can select and user can select it.

17 Visual Feedback There should be visual feedback given when response time for any action is more than 3 second. 15 Clear Key 16 End Key End Key should navigate the user to native OEM screen.Slider.End Key or form of exit modes Exit option in application and like Flap. Verify that there is visual feedback when response to any action takes more than 3 seconds. Verify that End Key should navigate the user to native OEM screen. Verify that when application is running then inserting and removing charger do not cause any problem and proper When application is running then inserting and removing charger should not cause any problem and proper message should be displayed when 20 Charger Effect . in application. Verify that user is User should be able to exit able to exit from with every form of exit modes application with every like Flap. Verify that clear key should navigate the user to previous screen.End from any point. Clear key should navigate the user to previous screen.14 Low Memory Verify that application Application should display displays proper error proper error message when message when device device memory is low and memory is low and exits gracefully from the exits gracefully from situation. the situation. 18 Continual Keypad Entry 19 Exit Application Verify that continual Continual key pad entry key pad entry do not should not cause any problem cause any problem. Key or Exit option in application and from any point.Slider.

applications of device to hamper. 1.message is displayed charger is inserted in device.Observe the application launch In the timeline defined Make sure that your Installed application should application is not not cause other applications causing other of device to hamper. more than 25s to start. 22 Removal of Battery 23 Battery Consumption Verify that application The application should not does not consume consume battery excessively. “Press a button” on the device to launch the app. 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. 24 Application Start/ Restart 25 Application Side Effects . 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. Find the application Application must not take icon and select it 2. 3. battery excessively. When application is running and battery is low then proper message is displayed to the user telling user that battery is low.

the Infrared (if applicable) application presents the user to the device with a continue option or is application presents continued automatically from the user] the point it was suspended at b) Give a visual or audible notification The application must not crash or hung. . after the user exits the [Send a file using communication.26 External incoming communicatio n – infrared Application should When the incoming gracefully handle the communication enters the condition when device the application must incoming at least respect one of the communication is following: a) Go into pause made via Infra Red state.

and is to be used as a guide for the testing activity.1 Unit Testing . Testing requirements specific to a particular manufacturer’s (or network operator’s) device. The procedure for carrying out testing in terms of preparation of test cases. Distribution. test environment setup. The intended audience for this document: The Project Managers Product development team members Test engineers 1. etc.e. DRM etc. assessment against standards for violence.) for the purpose of preventing the deployment or sale of an application. security. The article does not address the following: • Content censorship (i.1 Overview This document explains the testing methodology for a mobile application. and standards (e. user interface. defects logging and reporting are explained.2 Scope The scope of testing as explained in the document is to test the operating characteristics of an application that runs on mobile devices supporting J2ME. • 1.Test Plan for a mobile applications Source-WIKI Forum Nokia 1 Introduction 1. WAP) implementation.4 Acronyms Acronym Expansion DRM Digital Rights Management J2ME™ Java™ 2 Platform Micro Edition 2 Test Plan and Strategy 2. gambling. functionality. political messaging etc.3 References Mention the documents of references 1.g. The tests are organized by requirement category such as usability.

1. these will be reported. usability. 2. or groups of units of the application are united and tested as a completely merged application.1 Testing Procedure The steps in testing consist of: • • Creation of all the test scenarios and test cases Preparation of a test case document that has a brief description of the test case . Unit tests are designed to test a single class or component or module in isolation. security. • . separate units (packages / modules / components). installation etc. Verification of the system at this stage might include: functionality. 2. It is intended to validate the application as a whole.2. The purpose of System Testing is to identify defects that will only surface when a complete system is assembled.2.1. Developers run unit tests.4 Logging Tests and Reporting The developer will fix the defects that are found in unit testing.1 Objective The objective of Unit testing is to verify that a particular module of source code is working properly. steps to conduct tests and expected result Defect Report generation.3 Exit Criteria • • • All planned test cases are executed Units are working as per the expected results Defect are fixed in the code and tracked to closure 2.2 Entry Criteria • • • Test cases are reviewed Build is complete and self test done Unit Test environment is set up 2.1. if defects corresponding to other modules or components are found during unit testing. The rest of this document mainly explains how System Testing is performed by the testing team. 2. Additionally.1. and only for the components they are working on.2 System Testing In System Testing.

Personal Information Management (PI) – The application accessing user information needs to be able to do it in an appropriate manner and not to destroy the information.Outlined below are the main test types that will be performed a. h. It must be capable of dealing with both network problems and server-side problems. Stability (ST) – Focusing on the application being stable on the device. Functionality (FN) – Documented features are implemented in the application and work as expected. formatted application specification documents and online documentation. User Interface (UI) e. Security 2. b. and is done prior to taking up system testing which is to test new functionality. g. Regression testing consists of running a set of standard tests to ensure that old functionality has not been broken by new functionality.4 Pass/Fail Conditions It is expected that an application must pass all the tests in each test category to be successful. 2. c. Sources for the information are user manuals. Connectivity (CO) – the application must demonstrate its ability to communicate over a network correctly. Application Characteristics (AC) – Information about the application is provided to help the testing team in the testing work.3 Regression Testing This is an additional step. Regression tests are also run if a new release is made after fixing a number of defects. 2. d. the following information is provided: • The name of the application • The version number of the application • Device used for testing • Device firmware version For each error reported. Application Launch (AL) – Once an application is loaded it must start (launch) and stop correctly in relation to the device and other applications on the device. the following information is provided: • Description of the error • Frequency of occurrence of error: Systematic or Random or Once • Location of the error in the application .5 Test Report For each report. f.

the test schedules may need to be reviewed. All “Show-Stopper” bugs receive immediate attention from the development team. Devices. • • • • • 5 Entry and Exit Criteria 5. In case of lack of required equipment or changes in the feature requirements. Emulators and other support tools will be fully functional prior to project commencement.1 Risks: The following may impact the test cycle: • • Device availability Any new feature addition/modification to the application which is not communicated in advance. Any changes in the functional requirements since the requirements were signed-off/formulated • 4.• Steps to reproduce the error 3 Schedules for Testing This will be decided in consultation with the project manager. 4 Risks and Assumptions 4.2 Assumptions: • Every release to QA will accompany a release note specifying details of the features implemented and its impact on the module under test. All bugs found in a version of the software will be fixed and unit tested by the development team before the next version is released All documentation will be up-to-date and delivered to the system test team. Any delay in the software delivery schedule including defect fixes.1 Entry Criteria • • • • Development of the application is complete Successful completion of unit testing for the applications Release of software to the test environment Dedicated resources are allocated .

Test Metrics Following metrics will be captured and reported as part of the Test • • • • • • Summary Report Test Design effort Test execution effort Number of Test Cases executed Number of Defects and their classification Test Coverage (Number of test cases executed/Number planned) 7 Logging Tests and Reporting Some third party applications will be used for reporting bugs found during test execution. Test environment is up and working 5. The QA team will log defects in the tool as testing progresses. The remaining 5% do not impact critical functionality All test results have been evaluated and accepted. There are no showstoppers or high criticality defects unresolved or outstanding • • 6 . 8 Roles and Responsibilities The roles and responsibilities of the testing team for the project are as follows: 8.• • Approved test bed to carry out system testing.2 Exit Criteria The Following is the criteria when the testing will be stopped for this module: • All test cases have been executed and at least 95% have passed successfully.1 Project Manager / Test Manager Responsibilities: • • • • Overall responsibility for managing the testing process Approval of test documents Approval of inspections/reviews done as per the test plan Providing resources for the project .

. Deliverables • • • Test Plan Test Cases Document – Document with a description and expected result for each test case.8. 9.2 Test Lead Responsibilities: • • • • Requirement gathering Planning and estimating for testing Tracking and monitoring the testing as per the test plan Reporting the project status 8. Test Results – The Pass/Fail status of each test cases and the list of issues.3 Test Engineer Responsibilities: • • • Creating the test cases as per the test plan Executing the test cases Documenting the results and logging errors.

6: Download following installation files from Sun java site. You know very well that Android is the buzzword nowadays and it is just rocking all the way in mobile arena.bash. . I hope you have a basic idea about Linux command line &. We literally had to start from scratch and we faced quite a lot problems while installing Android SDK on Linux since both of us were newbie in Linux. So let’s get started. Eclipse ( A development environment for java and now android) ADT plugin for eclipse JDK(Java Development Kit)& JRE(Java runtime Environment). So here in this article we are going to tell you something interesting. Please note that you may not need to install eclipse & ADT plug in if you are just going to use the setup for testing. there was a requirement in our project where we have been asked to develop the project in Linux than our traditional platform Windows. We are going to explain the step by step process of how to install Android on your Linux machine. If not just have a look atthem before starting.10 in our case) Guest Post By:. But have you ever wondered how can we develop the android apps in Linux OR one step behind How to install Android SDK on Linux? Well. Everything is just going great with Android for now. As a developer or tester you must have installed Android SDK on windows OS and it must be pretty easy for you going along with it.6 and jre1.How to setup Android SDK on Linux ubuntu How to setup Android SDK on Linux ubuntu(Ubuntu 10. Being open source and as the learning curve is pretty easy we cannot stop ourselves being avid admirer of Android.Manish Phegade(Technical Associate) & Sangram Desai (Sr. Technical Associate) Friends. Step by Step Guide to Install Android SDK on Linux:1) Download JDK and JRE: ➢ download Jdk1. The main components required are: • • • • Android SDK setup. I hope you will like it as it is pretty interesting.

google.6 can be downloaded from eclips site (http://www.5.6 on my PC but in forums they have suggested to use Eclipse 3.1.1.bin ➢ Install JRE and JDK ➢ Set JAVA_HOME / PATH variables Under Linux Bash Profile: In linux. The. set it as follows: export JAVA_HOME=/usr/java/jdk1.org/downloads/?tab=developer) I have installed Eclipse 3.0_07/bin/java export PATH=$PATH:/usr/java/jdk1.bashrc file will now be visible.bashrc file as: export PATH=${PATH}:/home/”Your loginfolder”/android-sdk_r08linux_86/android-sdk-linux_86/platform-tools —————————————————————————————————— 3) Download ADT 8.6 (Helios) Eclips 3.g.0_07/bin/java.5:- .0.com/android/ADT-8.✔ jdk-6u23-linux-i586.zip —————————————————————————————————— 4) Download Eclipse 3. Open this file and add following lines at the bottom:e. unzip the file and save it at appropriate location and also set the path at very bottom of .5. So after going into root folder.5. If your path is set to /usr/java/jdk1. unlike windows all the environment variables and the corresponding paths are saved in a special file known as .0.bin ✔ jre-6u23-linux-i586.tgz After downloading.0_07/bin —————————————————————————————————— 2) Download and install Android SDK for linux: URL: – http://dl.6.So here is the download link for Eclipse 3.google.bashrc file.5 rather than 3.eclipse.com/android/android-sdk_r08-linux_86. This file is hidden. click on “View option-> show hidden files”. It is stored in your root folder. URL: – http://dl.

Add lines given below just above “-vmargs”.0_23/bin/java —————————————————————————————————— 6) Installing the ADT Plugin in Eclipse • • • • • • • Start Eclipse. Click OK. In the Add Site dialog. • • • —————————————————————————————————— 7) Now we have only installed the Android setup. In the next window. Edit Eclipse. “Android Plugin”) in the “Name” field.g. then click Finish.org/technology/epp/downloads/release/galileo/R/eclipsejava-galileo-linux-gtk. -vm /home/”Your loginfolder”/Downloads/New/new1/jdk1. you’ll see a list of the tools to be downloaded. then select Help > Install New Software. Enter a name for the local update site (e. We Now launch SDK manager and Download the current version of android for which we need to build/test the Application. Click Add in the top-right corner.gz —————————————————————————————————— 5) Configure Eclipse: • • • Now set the path of jdk in the eclipse.http://archive.6. Read and accept the license agreements.eclipse.ini file. Browse and select the downloaded zip file. restart Eclipse. select the checkbox next to Developer Tools and click Next. When the installation completes. Click Next. In the Available Software dialog.. click Archive. .tar.

click Browse… and locate your downloaded SDK directory. • • • —————————————————————————————————— 8 ) Go to android SDK>tools>emulator The Emulator WILL NOT start. This is because you need to change the file Permission as executable to let the OS know that it is an executable. Let us know if you have any query. you need to set up the path Of android SDK in the eclipse.Set Sdk path in Eclipse: – If you have installed eclipse. then OK. Right click on emulator icon. . Do it as follows. Click Apply. Select Android from the left panel. Otherwise it Won’t recognize. For the SDK Location in the main panel. So:• • Go to the android installation directory->tools->Emulator. • Select Window > Preferences… to open the Preferences panel (Mac OS X Eclipse > Preferences). That’s it! You are now ready to play with the Android on Linux.

Sign up to vote on this title
UsefulNot useful