How to Test Deep Links on Android (Complete Guide)

Deep links are crucial for a seamless user experience, directing users directly to specific content within your Android application. Ineffective deep linking leads to user frustration, lost conversion

April 05, 2026 · 5 min read · How-To Guides · Updated August 22, 2026

# Practical Guide to Android Deep Link Testing

Deep links are crucial for a seamless user experience, directing users directly to specific content within your Android application. Ineffective deep linking leads to user frustration, lost conversion opportunities, and a damaged brand reputation. Testing these links thoroughly ensures they function as intended across various scenarios.

Why Deep Link Testing Matters

A broken deep link can manifest in several ways, each impacting the user negatively:

What to Test: Comprehensive Deep Link Test Cases

A robust deep link testing strategy involves covering happy paths, error conditions, edge cases, and accessibility.

Happy Path Scenarios

These tests validate the core functionality of your deep links.

  1. Direct Navigation to Content:
  1. Navigation with Parameters:
  1. Deep Link from External App:
  1. Deep Link to Non-Default Activity:

Error and Edge Case Scenarios

These tests uncover issues when things don't go as planned.

  1. Invalid or Malformed URL:
  1. Non-existent Content ID:
  1. Deep Link with Special Characters/Encoding:
  1. App Not Installed (Revisited):
  1. Deep Link to Foregrounded App:
  1. Deep Link to Backgrounded App:

Accessibility Considerations

Deep links must be accessible to all users.

  1. Descriptive Link Text:
  1. Content Accessibility Post-Navigation:

Manual Deep Link Testing Approach

Manually testing deep links requires careful execution of predefined steps.

  1. Prerequisites: Ensure the target Android app is installed on a test device or emulator.
  2. Generate Test Links: Create a list of deep links covering the scenarios outlined above.
  3. Trigger Links: Use various methods to trigger these links:

Replace "myapp://products/123" with your deep link URI and com.your.package.name with your app's package name. The -W flag waits for the activity to finish, which is useful for debugging.

  1. Observe and Verify:
  1. Accessibility Check: Use TalkBack to navigate the content on the target screen. Verify element announcements and focus management.

Automated Deep Link Testing

Automating deep link tests significantly improves efficiency and repeatability.

  1. Execute an ADB command to open the deep link.
  2. Wait for the app to launch and the target activity to become visible.
  3. Use Appium to interact with elements on the target screen to verify content and functionality.
  4. 
        from appium import webdriver
        import subprocess
    
        desired_caps = {
            "platformName": "Android",
            "deviceName": "emulator-5554", # Or your device UDID
            "appPackage": "com.your.package.name",
            "appActivity": "com.your.package.name.MainActivity", # Your app's main activity
            "automationName": "UiAutomator2"
        }
    
        # Launch deep link using ADB
        deep_link_uri = "myapp://products/123"
        package_name = desired_caps["appPackage"]
        subprocess.run(f"adb shell am start -W -a android.intent.action.VIEW -d \"{deep_link_uri}\" {package_name}", shell=True)
    
        # Initialize Appium driver (wait for app to launch)
        driver = webdriver.Remote("http://localhost:4723/wd/hub", desired_caps)
    
        # Now use driver to assert content on the target screen
        # For example:
        # product_title_element = driver.find_element_by_id("product_title")
        # assert "Awesome Widget" in product_title_element.text
    
        driver.quit()
    

Test Your App Autonomously

Upload your APK or URL. SUSA explores like 11 real users — finds bugs, accessibility violations, and security issues. No scripts.

Try SUSA Free

Frequently asked questions

How do I test deep links on Android?

Test Android deep links with one ADB command: adb shell am start -W -a android.intent.action.VIEW -d "https://yourdomain.com/path" your.package.name. The -W flag waits and prints which activity handled the intent, so you see immediately whether the link resolved, opened the wrong screen, or fell back to the browser. Verify three layers: the intent filter in the manifest matches the URI pattern, the assetlinks.json file on your domain verifies App Links, and the destination screen receives the parameters. Manual coverage misses regressions, so autonomous platforms such as SUSA fire every discovered deep link across personas and report links that crash, land on the wrong screen, or lose their parameters — with reproduction steps.

What ADB command tests deep links?

The command is adb shell am start -W -a android.intent.action.VIEW -d "<url>" <package>. It sends a VIEW intent for the URL to the device exactly as a tap in another app would. Reading its output: Status: ok plus your activity name means the link resolved; a chooser dialog means App Links verification failed (check assetlinks.json); Error: Activity not started means no intent filter matched. Two companions are worth knowing: adb shell pm get-app-links <package> prints the domain-verification state on Android 12+, and adb shell dumpsys package d lists every registered URI mapping on older versions.