Audience
Anyone involved in software testing who wishes to broaden their knowledge of Mobile Application Testing or anyone who wishes to start a specialist career in Mobile Application Testing.
Prerequisites
The ISTQB Foundation Level certificate must be obtained before taking the exam.
Duration
Two days. Lecture presentations are supported by group practical work which allows discussion, reinforcement of learning and enhancement of the understanding process.
Course Objectives
This course has been independently developed but conforms to the current ISTQB Mobile Application Testing Foundation Level syllabus. Course fees do not include the BCS examination which may be taken at any PearsonVUE testing centre. Our Bath training centre is also a PearsonVUE testing centre, if you'd like to take the exam as part of the course please notify us after booking and we can arrange this for you.
At the end of the course, participants should be able to:
- Understand and review business and technology drivers for mobile apps in order to create a test strategy.
- Identify and understand the key challenges, risks and expectations associated with testing a mobile application.
- Apply test types and levels specific to mobile applications.
- Apply common test types, such as those mentioned in [ISTQB_CTFL_2018], in the mobile specific context.
- Carry out the activities required specifically for mobile application testing as part of the main activities described in the ISTQB test process.
- Identify and use suitable environments and appropriate tools for mobile application testing.
- Understand methods and tools used specifically to support mobile application test automation.
Course Content
1. Mobile World - Business and Technology Drivers
1.1. Mobile Analytics Data
1.2. Business Models for Mobile Apps
1.3. Mobile Device Types
1.4. Types of Mobile Applications
1.5. Mobile Application Architecture
1.6. Test Strategy for Mobile Apps
1.7. Challenges of Mobile Application Testing
1.8. Risks in Mobile Application Testing
2. Mobile Application Test Types
2.1. Testing for Compatibility with Device Hardware
2.1.1. Testing for Device Features
2.1.2. Testing for Different Displays
2.1.3. Testing for Device Temperature
2.1.4. Testing for Device Input Sensors
2.1.5. Testing Various Input Methods
2.1.6. Testing for Screen Orientation Change
2.1.7. Testing for Typical Interrupts
2.1.8. Testing for Access Permissions to Device Features
2.1.9. Testing for Power Consumption and State
2.2. Testing for App Interactions with Device Software
2.2.1. Testing for Notifications
2.2.2. Testing for Quick-access Links
2.2.3. Testing for User Preferences Provided by the Operating System
2.2.4. Testing for Different Types of Apps
2.2.5. Testing for Interoperability with Multiple Platforms and Operating System Versions
2.2.6. Testing for Interoperability and Co-existence with other Apps on the Device
2.3. Testing for Various Connectivity Methods
3. Common Test Types and Test Process for Mobile Applications
3.1. Common Test Types Applicable for Mobile Application
3.1.1. Installability Testing
3.1.2. Stress Testing
3.1.3. Security Testing
3.1.4. Performance Testing
3.1.5. Usability Testing
3.1.6. Database Testing
3.1.7. Globalization and Localization Testing
3.1.8. Accessibility Testing
3.2. Additional Test Levels applicable for Mobile Applications
3.2.1. Field Testing
3.2.2. Testing for Application Store Approval and Post-release Testing
3.3. Experience-based Testing Techniques
3.3.1. Personas and Mnemonics
3.3.2. Heuristics
3.3.3. Tours
3.3.4. Session-Based Test Management (SBTM)
3.4. Mobile Test Process and Approaches
3.4.1. Test Process
3.4.2. Test Approaches
4. Mobile Application Platforms, Tools and Environment
4.1. Development Platforms for Mobile Applications
4.2. Common Development Platform Tools
4.3. Emulators & Simulators
4.3.1. Overview of Emulators & Simulators
4.3.2. Using Emulators and Simulators
4.4. Setting up a Test Lab
5. Automating the Test Execution
5.1. Automation Approaches
5.2. Automation Methods
5.3. Automation Tools Evaluation
5.4. Approaches for setting up an Automation Test Lab