Mobile-specific test cases in Testing Fundamentals - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to check if the app handles screen rotation correctly.

Testing Fundamentals

def test_screen_rotation():
    app.launch()
    app.rotate_screen([1])
    assert app.is_ui_stable()

Drag options to blanks, or click blank then click option'

A"landscape"

B"rotate"

C"portrait"

D"flip"

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid orientation strings like "flip" or "rotate" which are not recognized.

Forgetting to assert UI stability after rotation.

The correct orientation to test screen rotation is "landscape" or "portrait". Here, we use "landscape" to simulate rotation.

2fill in blank

medium

Complete the code to simulate a low battery condition in the mobile app test.

Testing Fundamentals

def test_low_battery_warning():
    device.set_battery_level([1])
    app.launch()
    assert app.shows_low_battery_warning()

Drag options to blanks, or click blank then click option'

A80

B15

C50

D100

Attempts:

3 left

💡 Hint

Common Mistakes

Setting battery level too high, so warning does not appear.

Not simulating battery level before launching the app.

Battery levels below 20% usually trigger low battery warnings. Here, 15 simulates a low battery state.

3fill in blank

hard

Fix the error in the code that tests app behavior when network is lost.

Testing Fundamentals

def test_network_loss():
    device.set_network_status([1])
    app.perform_sync()
    assert app.sync_failed()

Drag options to blanks, or click blank then click option'

A"no_network"

B"disconnect"

C"offline"

D"lost"

Attempts:

3 left

💡 Hint

Common Mistakes

Using unsupported network status strings causing runtime errors.

Not setting network status before syncing.

The correct network status to simulate no connectivity is "offline". Other options are invalid and cause errors.

4fill in blank

hard

Fill both blanks to create a test that verifies app behavior on different screen sizes.

Testing Fundamentals

def test_screen_size():
    device.set_screen_size([1])
    app.launch()
    assert app.layout_is_responsive([2])

Drag options to blanks, or click blank then click option'

A"small"

B"large"

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using incorrect screen size strings.

Asserting with wrong boolean values.

We set the screen size to "small" and expect the layout to be responsive, so True is used for the assertion.

5fill in blank

hard

Fill all three blanks to test app behavior when switching between Wi-Fi and mobile data.

Testing Fundamentals

def test_network_switch():
    device.set_network_type([1])
    app.sync_data()
    device.set_network_type([2])
    app.sync_data()
    assert app.sync_successful([3])

Drag options to blanks, or click blank then click option'

A"wifi"

B"mobile"

CTrue

DFalse

Attempts:

3 left

💡 Hint

Common Mistakes

Using invalid network type strings.

Asserting sync failure instead of success.

The test switches network from "wifi" to "mobile" and expects sync to be successful, so True is asserted.

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