Mobile-specific test cases in Testing Fundamentals - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Why is testing on multiple screen sizes important for mobile apps?

Mobile devices come in many screen sizes. Why must testers check the app on different screen sizes?

A Because smaller screens do not support touch input

B To ensure the app layout adapts and remains usable on all screen sizes

C Because larger screens always run apps faster

D To reduce the app size for smaller screens

💡 Hint

Think about how the app looks and works on phones vs tablets.

Different screen sizes can change how content fits and how users interact. Testing ensures the app is usable and visually correct on all devices.

❓ Predict Output

intermediate

What is the output of this mobile network state test code?

Consider this pseudocode that checks network state on a mobile device:

network = getNetworkState()
if network == 'wifi':
    print('Connected to WiFi')
elif network == 'cellular':
    print('Using mobile data')
else:
    print('No network')

If the device is in airplane mode, what will be printed?

A No network

B Using mobile data

C Connected to WiFi

D Error: network variable undefined

💡 Hint

Airplane mode disables all network connections.

In airplane mode, no network is available, so the else branch runs printing 'No network'.

❓ assertion

advanced

Which assertion correctly verifies the app handles low battery warning on mobile?

You want to test that the app shows a warning message when battery level is below 15%. Which assertion is correct?

Testing Fundamentals

battery_level = 10
warning_displayed = app.checkLowBatteryWarning(battery_level)
# Which assertion below is correct?

A assert warning_displayed == True

B assert warning_displayed != True

C assert warning_displayed = True

D assert warning_displayed == False

💡 Hint

Remember the syntax for equality check in assertions.

Option A correctly uses '==' to check if warning_displayed is True. Option A uses assignment '=' which is invalid in assert. Options A and D check for False which is incorrect.

🔧 Debug

advanced

Find the bug in this mobile orientation test code

Here is code to detect if the device is in landscape mode:

def isLandscape(width, height):
    if width > height:
        return True
    else
        return False

What is the bug?

A Parameters should be height, width instead

B Wrong comparison operator, should be width < height

C Missing colon after else

D Function should return string, not boolean

💡 Hint

Check syntax carefully after else statement.

The else statement is missing a colon at the end, causing a syntax error.

❓ framework

expert

Which mobile testing framework supports both Android and iOS with a single codebase?

You want to automate tests for a mobile app on both Android and iOS using one codebase. Which framework is best?

A JUnit

B Espresso

C XCUITest

D Appium

💡 Hint

Consider cross-platform support.

Appium supports both Android and iOS automation with one codebase. Espresso is Android-only, XCUITest is iOS-only, and JUnit is a general Java testing framework.

Practice

1. Which of the following is a key focus when writing mobile-specific test cases?

easy

A. Testing only desktop browser compatibility

B. Testing features unique to mobile devices like GPS and touch gestures

C. Ignoring screen size variations

D. Testing only backend APIs without UI

Solution

1. Step 1: Understand mobile-specific features

   Mobile devices have unique features like GPS, accelerometer, and touch gestures that desktop devices do not.

2. Step 2: Identify test case focus

   Mobile-specific test cases must focus on these unique features to find device-specific issues.

3. Final Answer:

   Testing features unique to mobile devices like GPS and touch gestures -> Option B

4. Quick Check:

   Mobile features = A [OK]

Hint: Focus on device features unique to mobile devices [OK]

Common Mistakes:

• Ignoring mobile-only features
• Testing only desktop scenarios
• Not considering touch interactions

2. Which syntax correctly describes a test step for checking screen orientation change in a mobile test case?

easy

A. Step 1: Open browser and check URL

B. Step 1: Click desktop menu and verify dropdown

C. Step 1: Rotate device to landscape mode and verify UI adjusts correctly

D. Step 1: Run backend API and check response code

Solution

1. Step 1: Identify relevant mobile action

   Rotating device orientation is a common mobile-specific action to test UI responsiveness.

2. Step 2: Match test step syntax

   Step 1: Rotate device to landscape mode and verify UI adjusts correctly clearly states rotating device and verifying UI adjustment, which fits mobile test case syntax.

3. Final Answer:

   Step 1: Rotate device to landscape mode and verify UI adjusts correctly -> Option C

4. Quick Check:

   Mobile orientation test = B [OK]

Hint: Look for steps mentioning device rotation or orientation [OK]

Common Mistakes:

• Confusing desktop actions with mobile
• Ignoring device rotation in test steps
• Using backend steps in UI test cases

3. Consider this test step in a mobile app test case:

Step 1: Enable airplane mode
Step 2: Open the app
Step 3: Verify the app shows 'No internet connection'

What is the expected result of Step 3?

medium

A. App shows 'No internet connection' message

B. App logs user out automatically

C. App loads data from server normally

D. App crashes due to no network

Solution

1. Step 1: Analyze network condition

   Airplane mode disables all network connections, so the app cannot reach the internet.

2. Step 2: Understand expected app behavior

   The app should detect no internet and show a friendly message, not crash or load data.

3. Final Answer:

   App shows 'No internet connection' message -> Option A

4. Quick Check:

   Airplane mode disables network = D [OK]

Hint: No network means app shows offline message, not crash [OK]

Common Mistakes:

• Assuming app crashes without network
• Expecting normal data load offline
• Confusing logout with network loss

4. A tester wrote this mobile test step:

Step 1: Switch device to dark mode
Step 2: Open app
Step 3: Verify app UI uses dark colors

But the test always fails. What is the most likely error?

medium

A. The device was not actually switched to dark mode before testing

B. The app does not support dark mode at all

C. The tester used wrong device model

D. The app crashed on launch

Solution

1. Step 1: Check test setup correctness

   If the device is not switched to dark mode, the app UI won't change, causing test failure.

2. Step 2: Consider app support

   While app support matters, the question says test always fails, so setup is more likely the cause.

3. Final Answer:

   The device was not actually switched to dark mode before testing -> Option A

4. Quick Check:

   Incorrect setup causes test failure = A [OK]

Hint: Verify device mode before testing UI changes [OK]

Common Mistakes:

• Skipping device mode setup
• Assuming app supports dark mode without checking
• Ignoring device compatibility

5. You need to write a mobile-specific test case to verify the app's behavior when the device battery is low (below 15%). Which of the following is the best test step?

hard

A. Step 1: Connect device to chargerStep 2: Open appStep 3: Verify app loads data quickly

B. Step 1: Open appStep 2: Check if app crashes on startup

C. Step 1: Switch device to airplane modeStep 2: Open appStep 3: Verify app shows offline message

D. Step 1: Set device battery level to 10%Step 2: Open appStep 3: Verify app shows low battery warning and reduces background activity

Solution

1. Step 1: Simulate low battery condition

   Setting battery level below 15% tests app behavior under low power.

2. Step 2: Verify app response

   The app should warn user and reduce background tasks to save battery.

3. Final Answer:

   Step 1: Set device battery level to 10%
   Step 2: Open app
   Step 3: Verify app shows low battery warning and reduces background activity -> Option D

4. Quick Check:

   Low battery test = C [OK]

Hint: Simulate battery level, check app warning and behavior [OK]

Common Mistakes:

• Testing unrelated conditions
• Ignoring battery level simulation
• Confusing network and battery tests