IoT and Mobile Testing Exam Domains 2026: Complete Guide to All 6 Content Areas

Overview: How the ASTQB IoT and Mobile Testing Syllabus Is Organized

The ASTQB IoT and Mobile Testing Certification is built around six substantive domains that make up the official syllabus published by ASTQB. Unlike some certifications that publish exam blueprint percentages per domain, ASTQB instead publishes instructional time allocations - the number of minutes a training provider is expected to spend teaching each domain. These minutes are a proxy for depth and importance, not a guaranteed breakdown of exam question counts.

Understanding the six domains in order is the single most useful thing you can do before you start memorizing details. Each domain builds a specific competency: recognizing what makes IoT and mobile systems different from traditional software, planning tests for those differences, evaluating quality characteristics unique to constrained and connected devices, choosing the right tools and environments, understanding IoT-specific test challenges, and anticipating how testing needs will evolve. If you want a broader introduction before diving into domain mechanics, our companion piece on what IoT and Mobile Testing actually is is a good starting point.

Domain 1: Introduction to Testing IoT and Mobile Devices

This opening domain sets the vocabulary and mental model for everything that follows. It establishes why testing a mobile app or an IoT device differs fundamentally from testing a desktop application - think intermittent connectivity, diverse hardware, sensor input, battery constraints, and fragmented operating system versions.

Because this domain is foundational, questions here tend to be conceptual rather than scenario-heavy. If you're new to the field, this is also the domain where reviewing what the certification name actually means in practice will help the rest of the material click faster.

Domain 2: Test Planning and Design

Domain 2 shifts from concepts to application. It covers how test planning changes when your target is a mobile device or connected IoT product - device matrices, test data considerations, and designing test cases that account for interrupted sessions, permission prompts, and varying network conditions.

This is one of the domains where practicing scenario-based multiple-choice questions matters more than memorizing lists. Our one-page cheat sheet is designed to reinforce exactly this kind of applied recall.

Domain 3: Quality Characteristics for IoT and Mobile Testing

This is the largest domain by instructional time - 290 minutes according to the official syllabus - and it deserves proportionally more of your study hours. It covers the quality attributes that matter most for mobile and IoT products: usability under touch interfaces, performance under constrained processing and memory, security of data in transit and at rest, interoperability across devices, and reliability given intermittent power and connectivity.

Domain 4: Environments and Tools

At 285 minutes of instructional time, Environments and Tools is nearly as heavily weighted as Domain 3. It focuses on the practical infrastructure testers use: emulators versus simulators versus real devices, cloud-based device farms, automation frameworks suited to mobile platforms, and monitoring tools for IoT device fleets.

If tool names and categories feel overwhelming, our study guide for passing on the first attempt breaks this domain into smaller, testable chunks.

Domain 5: The Internet of Things

This domain narrows focus to IoT specifically - sensors, actuators, edge devices, gateways, and the communication protocols that connect them. It addresses testing challenges unique to IoT ecosystems: constrained device resources, protocol diversity (such as low-power wireless standards), and the layered architecture of sensor-to-cloud data flows.

Candidates coming from a pure mobile-testing background often find this the least familiar domain - plan extra review time here if IoT is new territory for you.

Domain 6: Future-Proofing

The final domain looks forward: how testers keep pace with rapidly evolving device ecosystems, emerging standards, and shifting user expectations. It's less about memorizing facts and more about demonstrating judgment - recognizing how a testing strategy should adapt as new device categories and connectivity standards emerge.

Exam Mechanics: Questions, Time, and Registration

Knowing the domains is only half the picture - you also need to understand exactly how the exam is delivered. The ASTQB IoT and Mobile Testing exam consists of 40 multiple-choice questions, with 60 minutes allotted. Candidates sitting the English exam whose first language isn't English can request a 25% time extension, bringing their total to 75 minutes.

Registration and voucher purchase go through AT*SQA, while actual exam delivery runs on the Kryterion/Webassessor platform. If you're taking the exam online, current instructions require a personal computer with administrative access, the Chrome browser, a cellphone functioning as a second camera, matching government-issued identification, and a completed system-readiness check before you're allowed to schedule your session. During the exam itself, you'll have access to an on-screen calculator and an electronic notepad, but no outside study materials or personal devices are permitted.

For a full breakdown of every fee and what's included in the voucher price, see our complete pricing breakdown. If you want the exact scoring threshold before you schedule, check our guide to the passing score requirements, and if you're still deciding when to sit for it, our exam dates and scheduling guide covers voucher timing in detail.

Sequencing Your Study Around Instructional Weight

Because Domains 3 and 4 carry the largest instructional allocations (290 and 285 minutes respectively), your study calendar should mirror that emphasis rather than splitting time evenly across all six domains. A sensible sequence front-loads the heavier domains while they're fresh, then circles back for lighter domains that need less repetition.

This is the one place we'll invoke general study mechanics: spaced repetition works well for Domain 3's quality characteristics because there are several attributes to distinguish (usability, performance, security, interoperability), and revisiting them across multiple short sessions beats a single long cram. For a more detailed week-by-week plan, see our dedicated study guide for passing on the first attempt, and for a realistic gauge of how challenging candidates find this material, read how hard the exam actually is.

Running full-length practice exams under real time constraints on our practice test platform is the fastest way to find out which domains still need work before exam day. Repeating timed sets on the practice site also builds the pacing instincts you'll need to comfortably finish 40 questions inside 60 minutes.

Who Actually Hires for This Credential

The ASTQB IoT and Mobile Testing Certification is aimed at QA professionals who test mobile applications, connected devices, or hybrid systems that combine both. It's a natural fit for mobile QA engineers, IoT test engineers, embedded systems testers, and general software testers whose organizations are expanding into connected products. Because ASTQB's expanded certification replaced the older Certified Mobile Tester credential, it signals broader competency than mobile-only testing alone.

If you're evaluating whether this credential lines up with your career goals, our guides on IoT and Mobile Testing job roles and earnings potential go deeper on market positioning. And if you're still weighing the investment against the return, our ROI analysis lays out the trade-offs without inflating the numbers.

Frequently Asked Questions