ISTQB CT-MAT study guide
ISTQB CT-MAT · Work through your exam, one topic at a time.
The ISTQB Certified Tester Mobile Application (CT-MAT) is a specialist-level certification in the ISTQB portfolio. ISTQB describes it as providing "an insight into methods, techniques, and tools a professional may use to test mobile applications," and notes that it "covers the required mobile project activities, roles, methods, and methodologies." In other words, it is aimed at testers who already hold core testing knowledge and now work on mobile products, where device fragmentation, platform differences, connectivity, and release cadence change how testing must be organised. The ISTQB CT-MAT study guide has 4 sections and about 1,417 words.
01Introduction to Mobile Application Testing
This domain frames why mobile testing differs from desktop and web work: the app ships onto hardware, OS versions, networks and store pipelines that the test team does not own. The exam checks that you can name the mobile application types, tie business models to test priorities, and reason about fragmentation as risk rather than as a slogan.
376 words, about 2 min02Mobile Devices and Platforms
This domain is the hardware and OS layer of the syllabus: what a device contains, how platforms fragment, and which environment - emulator, simulator, real device or cloud device farm - can actually expose a given defect. Emulator - software model of hardware and OS (e.g.
345 words, about 2 min03Testing Mobile Applications
This domain covers test types and levels: which quality characteristics need mobile-specific tests, and where in the lifecycle those tests sit. Install, upgrade and uninstall including data migration; permissions and denial paths; push and local notifications; deep links; in-app purchase; background/foreground transitions and state restore; offline mode and sync conflicts; orientation changes and multi-touch gestures.
347 words, about 2 min04Mobile Application Test Automation
This domain examines how to automate mobile tests economically: which tool categories exist, the mobile-specific obstacles that make scripts flaky, and the process decisions around ROI and maintenance. Vendor frameworks : Espresso for Android instrumentation, XCUITest for iOS - fast, close to the platform, single-platform only.
349 words, about 2 min