• What is the range of supported OS versions? • Is the user coverage public or enterprise? • For enterprise applications, is there any list of devices approved by the company? • For public applications, what is the targeted audience and application store category? Comprehensive checklist with similar questions can be found at . It is a first step in mobile testing because testers must know what they are going to test. To summarize the previous chapters, I suggest the following mobile application testing guidelines (inspired by ): 1. Define test conditions (scope and priorities) and prepare test suites • Start by preparing test cases based on functional and non- functional requirements and test design specification. • Decide which tests will be running on the emulators and which on the real devices. 2. Determine what test cases will be automated • Identify repetitive testing tasks suitable for automation. • Identify test cases which are required to be executed on multiple devices. • Identify test cases which cover basic functionality and will be easy to automate (e.g. smoke tests covering installation and login).
37 3. Prepare test environment and tools • Acquire test devices and emulators. Select popular devices. • Set up private test cloud or acquire public test cloud access (if device test cloud is needed). • Setup devices and emulators. For emulators – setup parameters (e.g. OS version, screen size, pixel density, memory, architecture, size of SD card memory) to reflect targeted devices. For real device – update or downgrade OS to desired version. Clear the device from unneeded applications or install widely used application (e.g. Messenger or Twitter) based on what you want to test 29 . • Acquire software for support mobile testing (e.g. tools for UI automation, security or performance testing). • Setup build server for continuous integration. 4. Functional testing • Run automated tests on the build server. • Perform manual tests on the selected devices. Support manual testing by in-application bug reporting tools. • Consider how often the automated tests will be executed on the device cloud. 5. Usability testing • Do not forget that usability is key factor to application success. • Start testing usability with sketches and prototypes in early project phases. • Test during the whole development process, test often. 6. Performance testing • Test application for its responsiveness, resource usage and launch time. 7. Reliability testing • Test if the application handles interruptions (7.1.1) correctly. 29 E.g. for reliability testing is better to test application on “messy” device running several background applications.
38 • Test if the application handles network errors, fluctuations, airplane mode and switching between Wi-Fi and cellular networks.
You've reached the end of your free preview.
Want to read all 72 pages?
- Spring '14
- ........., mobile devices, mobile applications