Device fragmentation challenges in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is device fragmentation a challenge in mobile app testing?

Device fragmentation means there are many different devices with various screen sizes, OS versions, and hardware. Why does this make testing mobile apps harder?

A Because the app might behave differently on different devices, requiring more tests to cover all cases.

B Because all devices run the same OS version, so testing on one device is enough.

C Because device fragmentation reduces the number of devices to test on.

D Because device fragmentation only affects desktop applications, not mobile apps.

💡 Hint

Think about how different devices might show or run the app differently.

Device fragmentation means many device types exist. Each may behave differently, so testers must check the app on many devices to ensure it works well everywhere.

🧠 Conceptual

intermediate

Which testing approach best handles device fragmentation?

Given many device types, which testing approach helps cover most device differences efficiently?

A Using device emulators and real devices to test a representative sample of devices.

B Skipping testing on devices with older OS versions.

C Testing only on the newest device model available.

D Testing only on devices from one manufacturer.

💡 Hint

Think about balancing cost and coverage.

Using both emulators and real devices for a representative sample helps cover many device types without testing every single device physically.

❓ Predict Output

advanced

What is the output of this device compatibility check code?

Consider this Python code snippet that checks device compatibility based on OS version and screen size.

Testing Fundamentals

devices = [
    {'name': 'DeviceA', 'os_version': 10, 'screen_size': 5.5},
    {'name': 'DeviceB', 'os_version': 9, 'screen_size': 6.1},
    {'name': 'DeviceC', 'os_version': 11, 'screen_size': 4.7}
]

compatible_devices = [d['name'] for d in devices if d['os_version'] >= 10 and d['screen_size'] >= 5.0]
print(compatible_devices)

A ['DeviceA', 'DeviceC']

B ['DeviceB']

C ['DeviceA']

D ['DeviceB', 'DeviceC']

💡 Hint

Check which devices have OS version 10 or higher and screen size 5.0 or larger.

DeviceA has OS 10 and screen 5.5 (meets both conditions). DeviceB has OS 9 (too low). DeviceC has OS 11 and screen 4.7 (screen too small). So only DeviceA qualifies.

❓ assertion

advanced

Which assertion correctly verifies app UI adapts to different screen sizes?

You want to check if the app's main button width adjusts correctly on devices with screen width 320 and 480 pixels.

Given button_width is the actual width in pixels, which assertion is best?

Testing Fundamentals

screen_width = 320  # or 480
button_width = get_button_width(screen_width)  # returns button width in pixels

A assert button_width > screen_width

B assert button_width == screen_width * 0.8

C assert button_width == 320 or button_width == 480

D assert button_width < 0

💡 Hint

The button should be 80% of the screen width.

Option B checks the button width is 80% of screen width, which matches the expected adaptive UI behavior. Others are incorrect or illogical.

❓ framework

expert

Which test framework feature best supports testing across many device types?

In a test automation framework, which feature helps efficiently run tests on multiple device configurations to handle fragmentation?

A Running tests only on a single device to save time.

B Ignoring device differences and testing only UI elements.

C Hardcoding device names inside each test case.

D Parameterization to run the same test with different device settings automatically.

💡 Hint

Think about running the same test many times with different inputs.

Parameterization allows running the same test with various device parameters, covering many devices efficiently. Hardcoding or ignoring devices reduces coverage.