ASTQB-CMT Exam Information and Outline
ASTQB Certified Mobile Tester
ASTQB-CMT Exam Syllabus & Study Guide
Before you start practicing with our exam simulator, it is essential to understand the official ASTQB-CMT exam objectives. This course outline serves as your roadmap, breaking down exactly which technical domains and skills will be tested. By reviewing the syllabus, you can identify your strengths and focus your study time on the areas where you need the most improvement.
The information below reflects the latest 2026 course contents as defined by ASTQB. We provide this detailed breakdown to help you align your preparation with the actual exam format, ensuring there are no surprises on test day. Use this outline as a checklist to track your progress as you move through our practice question banks.
Below are complete topics detail with latest syllabus and course outline, that will help you good knowledge about exam objectives and topics that you have to prepare. These contents are covered in questions and answers pool of exam.
Exam Code : ASTQB-MT
Exam Name : ASTQB Certified Mobile Tester
Exam Duration : 60 Minutes
Number of Questions : 40
Passing Score : 65%
Format : Multiple Choice Questions
Learning Objectives for Introduction to Mobile Testing
1.2 Expectations from Mobile Users
MOB-1.2.1 (K2) Explain the expectations for a mobile application user and how this affects test prioritization
1.3 Challenges for Testers
MOB-1.3.1 (K2) Explain the challenges testers encounter in mobile application testing and how the environments and skills must change to address those challenges
MOB-1.3.2 (K2) Summarize the different types of mobile applications
1.5 Equipment Requirements
MOB-1.5.1 (K2) Explain how equivalence partitioning can be used to select devices for testing
1.6 Lifecycle Models
MOB-1.6.1 (K2) Describe how some software development lifecycle models are more appropriate for mobile applications
Mobile applications generally fall into two categories- those developed specifically to be native mobile
applications and those that were designed to be viewed through a web browser on a mobile device.
From the user’s viewpoint- there is no difference- although some browser-based applications may be
optimized for the mobile device providing a richer (or at least more readable) user experience. From
the developer’s and tester’s viewpoint- there are different challenges- goals and success criteria. This
syllabus is focused on the applications specifically developed for use by a mobile device although
there will be some discussion about applications that have become mobile despite the original
intentions.
Mobile devices include any of the so-called hand-held devices including (dumb) mobile phones- smart
phones and tablets/netbooks as well as devices that have been created for a specific use such as ereaders or a device used by a parcel delivery service that allows the driver to record delivery- the customer to sign and an image to be taken documenting the delivery. Mobile devices also extend to
wearable items such as smart watches and glasses that allow access to specific applications and may
include additional native functionality- such as telling time or improving vision. While some of the
mobile application testing concepts discussed in this syllabus are applicable to wearable devices-
wearable devices are not the focus of this syllabus.
The field of mobile devices is continually expanding as new uses are devised and devices are created
to support those uses
COURSE OUTLINE- COURSE CONTENTS- SYLLABUS
Introduction to Mobile Testing
Expectations from Mobile Users
- Explain the expectations for a mobile application user and how this affects test prioritization Challenges for Testers
- Explain the challenges testers encounter in mobile application testing and how the environments and skills must change to address those challenges
- Summarize the different types of mobile applications
Equipment Requirements - Explain how equivalence partitioning can be used to select devices for testing
Lifecycle Models - Describe how some software development lifecycle models are more appropriate for mobile applications
Test Planning and Design
Identify Functions and Attributes
- Explain why use cases are a good source of testing requirements for mobile applications
Identify and Assess Risks
- Describe different approaches to risk analysis
Determine Coverage Goals
- Explain how coverage goals will influence the level and type of testing to be conducted
Identify Test Conditions and Set Scope
- Describe how test analysts should take the device and application into consideration when creating test conditions
Quality Characteristics for Mobile Testing
Functional Testing - For a given mobile testing project apply the appropriate test design techniques
- Recall the purpose of testing for the correctness of an application
- Explain the important considerations for planning security testing for a mobile application
- Summarize the concepts of perspectives and personas for use in mobile application testing
- Summarize how device differences may affect testing
- Explain the use of Teststorming for deriving test conditions
Non-Functional Testing - Create a test approach that would achieve stated performance testing goals
- Recall aspects of the application that should be tested during performance testing
- Explain why real devices are needed when simulators are used for testing
- For a given mobile testing project- select the appropriate criteria to be verified with usability testing
- Explain the challenges for portability and reliability testing mobile applications
Environments and Tools
Tools - Recall the expected capabilities for mobile application testing tools
- Explain the use of generic tools in testing mobile applications
Environments and Protocols - Recall the sources of data for a mobile application
Specific Application-Based Environment Considerations
- Explain the differences between browser-based and native device applications
Real Devices- Simulators- Emulators and the Cloud
- Explain why testing is not conducted entirely on real devices
- For a given mobile testing project- determine how and when to use simulators/emulators during testing
- Recall how to verify the reliability of a simulator/emulator
- For a given mobile testing project- determine how and when to use cloud-based testing
Performance Test Tools and Support - Explain how the cloud can be used to support performance testing
- Explain the types of data a performance tool needs to be able to create and track
Future-Proofing
Expect Rapid Growth - Recall ways in which the mobile application and device market will expand
- Recall areas in which user expectations will increase
Build for Change - Summarize the considerations for building a flexible testing framework
- Analyze a given mobile testing project and determine the appropriate activities to reduce maintenance costs while enabling wide product adoption
Plan for the Future - Explain how lifecycle models are likely to change and how this will affect testing
Anticipating the Future - Recall the ways in which testers will need to adapt