CT-MAT — Mobile Application Testing glossary

120 terms the exam expects you to know, defined in plain language.

A

Accessibility Label(accessibility label, accessibility labels): Textual description of UI elements for screen readers, ensuring proper identification for assistive technologies.
Action Queuing(queuing of user actions): A mechanism that stores user actions performed offline for later synchronization when connectivity resumes.
Analytics-Informed Test Environment Selection(analytics-informed test environment selection): The process of choosing test devices, emulators, and simulators based on user distribution data from mobile analytics.
App Degradation Under Poor Networks(app degradation): Expected graceful behavior of an app when network conditions are slow or unstable.
Assistive Technology(assistive technology): Built-in mobile tools like screen readers (VoiceOver, TalkBack) that help users with disabilities interact with apps.

B

Bandwidth and Latency Simulation(bandwidth simulation, latency simulation, bandwidth and latency simulation): Testing app performance under varying network speeds and delays to ensure graceful degradation.
Broken Authentication(broken authentication): A common mobile API vulnerability where authentication mechanisms are flawed.

C

Cloud-Based Device Lab(cloud-based device labs, cloud labs): A service providing remote access to a wide range of real devices for testing, balancing cost and coverage.
Cloud-Based Device Lab Limitations(cloud-based device labs may have limitations): Constraints of cloud device labs including availability, network simulation fidelity, and data privacy issues.
Cloud-Based Device Labs(cloud-based device labs, cloud labs): Cost-effective services providing access to a wide range of real devices without physical maintenance.
Context-Dependent Best Practices(context-dependent best practices): The principle that in ISTQB, statements like 'X is better than Y' depend on context and are not universally true, often appearing as distractors in multiple-choice questions.
Crash Report Analysis for Test Design(crash report analysis): A technique that uses crash reports from analytics tools to identify and target specific failure-prone areas of an application.

D

Data Privacy Concern(data privacy concerns, data privacy policies): The risk of exposing sensitive information when testing on shared cloud device labs.
Data Synchronization Testing(data synchronization tests, sync testing, data synchronization testing, data sync testing): Ensuring locally stored data is synced correctly on reconnection, handling conflicts, duplicates, and data loss.
Defect Lifecycle(defect lifecycle, defect states): Series of states a defect passes through: New, Assigned, Fixed, Verified, Closed.
Defect Lifecycle States(defect states, lifecycle states): The standard states New, Assigned, Fixed, Verified, and Closed as per ISTQB glossary.
Defect Reporting for Mobile Apps(defect reporting): Capturing device-specific details such as OS version, device model, and network type in defect reports to aid reproduction.
Defect Triage(defect triage, triage session): Process of prioritizing defects based on business impact, frequency, and affected user base in mobile testing.
Device Fragmentation(device fragmentation, mobile device fragmentation): The challenge of diverse device models, OS versions, and form factors in mobile testing that requires risk-based prioritization.
Device Selection Criteria(device selection criteria, key criteria): Factors such as OS version, screen size, hardware specs, network capabilities, and form factor used to choose test devices.
Device and OS Fragmentation(device fragmentation, os fragmentation, device and os variations): Variation of device models, OS versions, and configurations that complicates mobile testing and defect management.
Device-Level Security Testing(device-level security testing): Testing mobile app security on compromised devices and verifying data storage.
Device-Specific Details(device details, device-specific information): Information such as device model, OS version, screen resolution, network type, and sensor data required for defect reproduction.
Device-Specific Environment Details(environment details, device-specific information, device-specific environment details): Critical information such as device model, OS version, network type, and sensor data needed to reproduce mobile defects.

E

Emulator(emulator, emulators, android emulator): A testing tool that simulates both the software and hardware of a mobile device, commonly used for Android testing.
Emulator Limitations(emulator limitations): The inability of emulators and simulators to accurately replicate real-world network conditions and hardware behavior.
Emulator and Simulator Limitations(emulators or simulators cannot fully replace real devices): The inability of emulators or simulators to fully replicate real-world conditions like sensor behavior and battery drain.
Emulator vs Simulator(emulator, simulator, emulators, simulators): Emulators simulate the software environment, while simulators mimic device behavior; both supplement but do not replace real device testing.
Emulator vs Simulator vs Real Device(emulators and simulators, real devices): The trade-offs between faster/cheaper emulators/simulators and real devices that provide higher fidelity for sensor interactions, battery drain, and network conditions.
Emulators(emulators, emulators (mobile testing)): Tools that mimic both the software and hardware of a mobile device, commonly used for Android testing.
Encryption at Rest(encryption at rest): Protecting data stored on the device by encrypting it when not in use.
Entry and Exit Criteria for Mobile Testing(entry and exit criteria): Conditions that define when a test phase can start and be considered complete in a mobile test plan.

G

Gesture Support(gesture support): Support for touch gestures like swipe and pinch that are essential for mobile interaction.
Graceful Degradation(graceful degradation): The app's ability to maintain acceptable functionality under poor network conditions, e.g., showing lower-resolution images.

H

Hardware-Dependent Testing(hardware-dependent features, hardware-specific features, hardware-dependent testing): Testing that requires real devices to accurately assess features like camera, GPS, sensors, and performance under load.
Hybrid Application(hybrid app, hybrid applications, hybrid apps, hybrid application): A mobile app combining web technologies with a native container for installation, allowing limited device API access via plugins.

I

ISTQB Glossary(istqb testing terminology glossary, canonical definitions for exam answers): The authoritative, standardized collection of testing terms and definitions used across all ISTQB certification syllabuses.
Injection Attacks(injection attacks): Server-side attacks like SQL or NoSQL injection exploiting input validation flaws.
Insecure Data Storage(insecure data storage): Storing sensitive data like credentials or tokens in plaintext on the device file system.
Insecure Direct Object References(insecure direct object references): A vulnerability where APIs expose internal object references without authorization.
Interrupt Handling in Mobile Testing(interrupt handling): Testing how the app responds to incoming calls, SMS, notifications, and other system interrupts during execution.

J

Jailbreaking and Rooting(jailbreaking/rooting): Device compromise states that bypass security restrictions and expose sensitive data.

L

Limitations of Analytics in Testing(limitations of analytics): The inherent constraint that analytics data reflects past behavior and may not predict future usage patterns after app updates or market shifts.
Localization of Accessibility Labels(localization of accessibility labels): Adaptation of accessibility labels to different languages to ensure they are meaningful in each locale.

M

Man-in-the-Middle Attack(man-in-the-middle attacks): An attack where communication between app and server is intercepted.
Market Share-Based Device Selection(market share, usage analytics, market share-based device selection, device selection based on market share): The practice of choosing devices for testing based on popularity and usage analytics to maximize coverage.
Mobile Accessibility Testing(accessibility testing for mobile): Testing to ensure a mobile app is usable by people with disabilities, using assistive technologies and compliance with standards.
Mobile Analytics-Driven Test Prioritization(analytics-driven test prioritization): A testing approach that uses real-world usage data to focus efforts on the most common devices, OS versions, and network conditions.
Mobile Application Platforms(mobile application platforms, devices and environments): The underlying operating systems and hardware environments on which mobile applications run.
Mobile Application Test Automation(mobile application test automation, test automation for mobile, test automation): The use of automation tools and frameworks to execute tests on mobile applications.
Mobile Defect Lifecycle(defect lifecycle, defect states, defect life cycle): States including New, Assigned, Fixed, Verified, and Closed that a defect passes through in a tracking system.
Mobile Defect Report(mobile defect report, defect report): A report that includes device model, OS version, screen resolution, network type, and sensor data for reproducibility.
Mobile Defect Triage(defect triage, triage in mobile testing, triage process, triage): A process that prioritizes mobile defects based on business impact, frequency of occurrence, and affected user base.
Mobile Devices(devices, real devices (mobile testing), real devices): Physical hardware such as smartphones and tablets used to test mobile applications.
Mobile Environments(environments): The combination of device hardware, operating system, and network conditions in which mobile apps operate.
Mobile Performance Testing(performance testing for mobile): A testing type that evaluates app responsiveness and stability under variable network conditions, device hardware differences, and battery consumption.
Mobile Platforms(mobile platforms): Operating systems and device ecosystems such as iOS and Android that support mobile application execution.
Mobile Security Testing(security testing for mobile): A testing type that identifies risks such as data leakage, insecure storage, weak authentication, and vulnerabilities in third-party libraries.
Mobile Test Data(test data, mobile test data): Prepared data tailored to mobile scenarios, such as contacts, SMS, GPS locations, and app-specific data, used for realistic testing.
Mobile Test Data Management(test data management for mobile, test data): Preparing test data tailored to mobile scenarios, such as contacts, SMS, GPS locations, and app-specific data.
Mobile Test Environment(mobile test environment, test environment for mobile, test environment, mobile testing environment): Infrastructure and tools required for mobile test execution, including device farms, network simulators, and emulators.
Mobile Test Environment Management(test environment): Use of device farms, network simulators, and emulators to cover real-world conditions.
Mobile Test Environment Setup(test environment setup for mobile, mobile test environment setup): The process of configuring emulators, simulators, real devices, and cloud-based device labs for mobile app testing.
Mobile Test Strategy(test strategy, mobile application test strategy, mobile test strategy): A plan that combines real devices, emulators, and simulators to balance coverage, cost, and speed.
Mobile Usability Testing(usability testing for mobile, usability testing): Testing focused on how effectively, efficiently, and satisfactorily users interact with a mobile app on small screens with touch input.
Mobile web application(web application, web app, mobile web app): A mobile app accessed through a mobile browser, not installed on the device, built with standard web technologies.
Mobile-Specific Behaviors(device-specific behaviors, interrupt handling, battery consumption, mobile-specific behaviors): Device-specific characteristics such as interrupt handling, battery consumption, and sensor behavior that must be tested.

N

Native Application(native app, native applications, native apps, native application): A mobile app developed for a specific platform using platform-specific languages and SDKs, installed directly on the device with full device feature access.
Network Condition Simulation(network conditions, network simulators, network types, network simulation): The practice of mimicking network types like 3G, 4G, 5G, Wi-Fi, and airplane mode during mobile testing.
Network Conditions Impact on Defects(network conditions, network type impact): Influence of network type (Wi-Fi, 4G, 5G) and conditions (poor signal, roaming) on defect reproducibility.
Network Shaping Tools(network shaping tools): Tools that throttle or modify network conditions in cloud labs to simulate real-world environments.
Network Simulation Fidelity(network simulation fidelity, network throttling): The accuracy with which a cloud lab replicates real-world network conditions like latency.
Network Switching Tests(network switching tests, network interruption tests): Tests that validate app behavior when switching between network types (e.g., Wi-Fi to cellular) and ensure no data loss or crashes.
Network Switching and Interruption Tests(network switching tests, interruption tests): Tests that validate app behavior when the device switches between network types or loses connectivity temporarily.
Network Transitions(network transitions, wi-fi to cellular transitions): Changes in network type such as Wi-Fi to cellular that apps must handle robustly to avoid failures.
Network-Level Security Testing(network-level security testing): Verifying network communication encryption and certificate validation to prevent interception.

O

Offline Mode Testing(offline mode testing, offline testing): Verifying app functionality when launched offline, goes offline during use, and reconnects after disconnection.
Offline Mode and Data Synchronization(offline mode testing, data synchronization tests): Tests that verify the app can function offline, store data locally, and synchronize correctly when connectivity is restored.
One-Handed Operation(one-handed operation): The ability to use a mobile app comfortably with one hand, considering reachability and touch targets.
One-Handed Operation Testing(one-handed operation testing, one-handed operation): A testing approach that ensures app usability with one hand by verifying reachability and touch target sizing for key actions.
Order of Activities in a Process(order of activities): A common mis-recall where the sequence of steps in a testing process (e.g., planning, execution, reporting) is reversed.
Over-Testing Low-Risk Configurations(over-testing low-risk configurations): A common mistake of allocating excessive test effort to device-OS combinations with low risk impact.

P

Performance Metric-Driven Testing(performance metric-driven testing): A testing method that uses performance metrics and degradation trends to guide load and stress testing efforts.
Platform Fragmentation(platform fragmentation): The variation in mobile device specifications such as screen size, OS version, and hardware that necessitates prioritized testing.

R

Real Device Connectivity Testing(real device testing, actual device testing, real device connectivity testing, connectivity testing on real devices): Performing connectivity tests on actual devices with real network variations because emulators may not replicate real conditions.
Real Device Testing(real device testing, real devices, real-device testing): Testing on physical mobile devices to accurately capture touch sensitivity, screen glare, and physical interactions.
Real device(real device, real devices): A physical mobile device used for testing to replicate real-world conditions like sensor interactions and network variability.
Regression Testing After Mobile Defect Fix(regression testing for mobile, post-fix regression testing, regression testing in mobile, regression testing, mobile regression testing, regression testing after mobile defect fix): Testing performed on the original device/OS and a representative set of other configurations to verify the fix and prevent new defects.
Risk-Based Device Selection(device selection based on market analytics, risk-based approach to device selection, risk-based selection, risk-based device selection, risk-based test device prioritization): A prioritization strategy for mobile testing that selects devices based on market share, user demographics, and risk analysis.
Risk-Based Prioritization(risk-based prioritization): A method to select a representative subset of devices based on market share, critical user journeys, and known problem areas.
Risk-Based Prioritization for Mobile Testing(risk-based prioritization, prioritization and scheduling): A scheduling strategy that focuses test execution on high-risk areas like critical user journeys and security features.
Risk-Based Test Device Prioritization(risk-based approach, risk analysis): An approach that selects devices covering the most critical user scenarios based on risk analysis.

S

Screen Orientation Change(orientation change, screen orientation change, orientation changes): Switching between portrait and landscape modes that must maintain usability and accessibility.
Screen Orientation Change Testing(screen orientation changes): Testing that ensures usability and accessibility are maintained when screen orientation changes.
Screen Reader Testing(screen reader testing): Process of verifying that assistive technologies correctly interpret accessibility labels and gesture navigation.
Screen Size Constraint(screen size constraint): The limitation of small mobile screens affecting layout, readability, and navigation.
Server-Side and API Security Testing(server-side and api security testing): Testing backend APIs for authentication, session management, and injection vulnerabilities.
Session Management(session management): Handling of user sessions in mobile apps to prevent unauthorized access.
Severity and Priority(severity and priority, severity vs priority, severity vs. priority): Distinct attributes where severity is technical impact and priority is business urgency of a defect.
Severity vs Priority in Mobile Testing(severity and priority, severity vs priority): A distinction where severity reflects technical impact and priority reflects business urgency, especially relevant in mobile due to device fragmentation.
Simulator(simulator, simulators): A testing tool that mimics device behavior but not the underlying hardware, often used for iOS testing.
Simulator vs Emulator(simulator vs. emulator, simulators and emulators): A distinction where a simulator mimics only the software environment, while an emulator mimics both hardware and software.
Simulators(simulators, simulators (mobile testing)): Tools that mimic only the software environment of a device, commonly used for iOS testing.
State Maintenance During Network Transitions(state maintenance): The requirement for an app to preserve its state and resume normal operation after network switches or interruptions.

T

TLS Encryption(tls): Protocol that encrypts network traffic between mobile app and server.
TalkBack(talkback): Android screen reader that interprets accessibility labels and enables gesture-based navigation.
Test Execution Considerations for Mobile Apps(test execution considerations, mobile test execution considerations, test execution considerations for mobile apps): Challenges including device fragmentation, interrupt handling, and resource constraints (battery, memory) during mobile test execution.
Test Level vs. Test Type(test level vs. test type): A key classification: test level (e.g., unit, integration) refers to the scope of testing, while test type (e.g., functional, non-functional) refers to the quality characteristic being tested.
Test Manager vs. Test Management Role(test manager vs. test management role): A distinction between the specific job title 'test manager' and the broader responsibilities of a test management role, often confused in ISTQB contexts.
Tool Support for Mobile Testing(tool support for mobile testing): Software tools that facilitate various mobile testing tasks, including emulators, simulators, and cloud device farms.
Touch Target Size(target size, touch target size, touch target): The physical size of interactive elements that must be large enough for accurate tapping on mobile devices.
Traceability Matrix(traceability matrix): A document linking test requirements to device configurations to ensure coverage across OS, screen size, and hardware combinations.
Traceability Matrix for Mobile Testing(traceability matrix): A document linking test requirements to device configurations to ensure coverage across combinations.
Triage Meeting(triage meeting): A meeting involving testers, developers, and product owners to decide which defects to fix in the current sprint.

U

Usage-Based Test Coverage(usage-based test coverage): A test coverage strategy that aligns testing with actual user behavior and frequently used features.

V

Verification vs. Validation(verification vs. validation): A fundamental distinction in testing: verification checks if the product is built correctly, validation checks if the correct product is built.
VoiceOver(voiceover): iOS screen reader that interprets accessibility labels and enables gesture-based navigation.

W

WCAG 2.1(wcag 2.1, web content accessibility guidelines 2.1): A set of accessibility standards that mobile apps should comply with for users with disabilities.
WCAG 2.1 Touch Target Requirement(wcag 2.1 standard, touch target requirement, wcag 2.1 success criterion 2.5.5, wcag 2.1, minimum target size of 44x44 css pixels): A WCAG 2.1 standard requiring touch targets to be at least 44 by 44 CSS pixels for accessibility.
Web Application(web app, web applications, web apps, web application): A mobile app accessed through a browser, built with standard web technologies, running in a browser sandbox with limited device access.