Mobile testing types in Testing Fundamentals - Build an Automation Script

Verify mobile app launches and displays home screen

Preconditions (3)

Step 1: Launch the mobile app on the device

Step 2: Wait for the home screen to load

Step 3: Verify the home screen title is visible

Step 4: Verify the main menu button is present

Step 5: Close the app

✅ Expected Result: The app launches successfully, home screen title and main menu button are visible, and app closes without errors

Automation Requirements - Appium with Python unittest

Assertions Needed:

Home screen title is displayed

Main menu button is present

Best Practices:

Use explicit waits to wait for elements

Use accessibility IDs or resource IDs for locating elements

Close the app session properly after test

Automated Solution

Testing Fundamentals

import unittest
from appium import webdriver
from selenium.webdriver.common.by import By
from selenium.webdriver.support.ui import WebDriverWait
from selenium.webdriver.support import expected_conditions as EC

class MobileAppLaunchTest(unittest.TestCase):
    def setUp(self):
        desired_caps = {
            "platformName": "Android",
            "deviceName": "Android Emulator",
            "appPackage": "com.example.myapp",
            "appActivity": ".MainActivity",
            "automationName": "UiAutomator2"
        }
        self.driver = webdriver.Remote('http://localhost:4723/wd/hub', desired_caps)
        self.wait = WebDriverWait(self.driver, 10)

    def test_home_screen_display(self):
        # Wait for home screen title to be visible
        home_title = self.wait.until(
            EC.visibility_of_element_located((By.ACCESSIBILITY_ID, "home_screen_title"))
        )
        self.assertTrue(home_title.is_displayed(), "Home screen title should be visible")

        # Verify main menu button is present
        main_menu_btn = self.wait.until(
            EC.presence_of_element_located((By.ACCESSIBILITY_ID, "main_menu_button"))
        )
        self.assertIsNotNone(main_menu_btn, "Main menu button should be present")

    def tearDown(self):
        self.driver.quit()

if __name__ == '__main__':
    unittest.main()

This test script uses Appium with Python's unittest framework to automate a mobile app launch test.

setUp(): Sets desired capabilities for Android emulator and app details, then starts the Appium driver and a wait helper.

test_home_screen_display(): Waits explicitly for the home screen title to appear using accessibility ID, asserts it is visible, then waits for the main menu button and asserts it is present.

tearDown(): Closes the app session properly after the test.

This approach uses explicit waits to avoid timing issues and uses accessibility IDs for reliable element location, following best practices for mobile test automation.

Common Mistakes - 3 Pitfalls

Using hardcoded sleep delays instead of explicit waits

Locating elements by fragile XPath expressions

Not closing the app session after test

Bonus Challenge

Now add data-driven testing with 3 different app activities to verify their launch

Show Hint

Practice

1. Which type of mobile testing focuses on checking if the app works correctly on different devices and operating systems?

easy

A. Compatibility Testing

B. Performance Testing

C. Security Testing

D. Usability Testing

Solution

1. Step 1: Understand the goal of compatibility testing

   Compatibility testing ensures the app works well across various devices, OS versions, and screen sizes.

2. Step 2: Match the testing type to the description

   Since the question asks about different devices and OS, compatibility testing fits best.

3. Final Answer:

   Compatibility Testing -> Option A

4. Quick Check:

   Different devices = Compatibility Testing [OK]

Hint: Devices and OS differences? Think compatibility testing [OK]

Common Mistakes:

• Confusing performance testing with compatibility testing
• Choosing usability testing which focuses on user experience
• Selecting security testing which checks app safety

2. Which of the following is the correct syntax to describe a test that measures how fast a mobile app responds under load?

easy

A. Security Testing

B. Performance Testing

C. Functional Testing

D. Compatibility Testing

Solution

1. Step 1: Identify the testing type for speed and load

   Performance testing measures app speed, responsiveness, and stability under load.

2. Step 2: Match the correct testing type

   Performance testing fits the description of measuring how fast the app responds.

3. Final Answer:

   Performance Testing -> Option B

4. Quick Check:

   Speed under load = Performance Testing [OK]

Hint: Speed and load? Choose performance testing [OK]

Common Mistakes:

• Mixing functional testing with performance testing
• Confusing security testing with performance
• Selecting compatibility testing which is about devices

3. Consider this code snippet describing a mobile test scenario:

test_scenario = {
  "type": "Security Testing",
  "check": "Data encryption and secure login"
}
print(test_scenario["type"])

What will be the output when this code runs?

medium

A. "Security Testing"

B. "Data encryption and secure login"

C. KeyError

D. None

Solution

1. Step 1: Understand dictionary access in Python

   Accessing test_scenario["type"] returns the value for the key "type" which is "Security Testing".

2. Step 2: Confirm the printed output

   The print statement outputs the string "Security Testing" exactly as stored.

3. Final Answer:

   "Security Testing" -> Option A

4. Quick Check:

   Dictionary key 'type' = "Security Testing" [OK]

Hint: Print dictionary key value directly for output [OK]

Common Mistakes:

• Confusing key and value causing KeyError
• Printing the wrong key's value
• Assuming None if key missing

4. A tester wrote this test step for mobile app testing:

1. Open app
2. Enter username and password
3. Click login button
4. Verify user is logged in

Which type of mobile testing is this example missing?

medium

A. Compatibility Testing

B. Usability Testing

C. Security Testing

D. Performance Testing

Solution

1. Step 1: Analyze the test steps

   The steps check basic login functionality but do not measure speed or load.

2. Step 2: Identify missing testing type

   Performance testing, which measures speed and responsiveness, is missing here.

3. Final Answer:

   Performance Testing -> Option D

4. Quick Check:

   Speed check missing = Performance Testing [OK]

Hint: Check if speed/load tests are included for performance [OK]

Common Mistakes:

• Assuming security testing is covered by login steps
• Confusing usability with performance
• Ignoring compatibility which is about devices

5. You want to test a mobile app's behavior when the network connection is lost during a purchase. Which combination of mobile testing types should you apply?

hard

A. Functional Testing and Compatibility Testing

B. Performance Testing and Usability Testing

C. Functional Testing and Network Testing

D. Security Testing and Performance Testing

Solution

1. Step 1: Identify the scenario requirements

   The test involves app function during network loss, so functional and network testing are relevant.

2. Step 2: Match testing types to scenario

   Functional testing checks if purchase works correctly; network testing simulates connection loss.

3. Final Answer:

   Functional Testing and Network Testing -> Option C

4. Quick Check:

   Network loss + function = Functional + Network Testing [OK]

Hint: Network issues? Combine functional and network testing [OK]

Common Mistakes:

• Choosing compatibility which is about devices, not network
• Confusing performance with network testing
• Ignoring network testing for connection problems