The job to be done
How does TestDock help with deep-link QA?
Exercise parameterized custom schemes, universal links, and Android app links without rebuilding each URL by hand.
Testing stays close to the installed app. Open links or share/open-in flows through the operating system; inspect AASA and assetlinks configuration; validate and send through Expo Push, APNs, or FCM; and keep redacted results and scenario evidence on the device. TestDock has no account, sync service, analytics, or backend.
Recommended path
Exercise the installed app
Open links or share sheets through the operating system, send a validated provider push, and run observable scenario steps on the device.
TestDock keeps the app profile, resolved link or push input, protected provider setup, scenario state, and redacted outcome together on the device where the check runs.
Capabilities involved
The parts of TestDock used here.
Related manual
Test deep links and app associations
Save reusable custom schemes and web links, resolve their parameters, open them on device, and inspect association files.
Its sections cover create a reusable link, review before opening, verify app-link configuration, use history deliberately. Use it when you are ready to reproduce this workflow with your own project data.
Read the guideDirect answers
Questions about this use case.
How does TestDock help with deep-link QA?
Exercise parameterized custom schemes, universal links, and Android app links without rebuilding each URL by hand. The recommended path starts with exercise the installed app and uses deep-link workbench, persistent app profiles, push diagnostics and logs.
Does TestDock switch the environment of the app under test?
No. An external app controls its own configuration. TestDock models the app identity and stores the links, push setups, payloads, and scenarios you can actually exercise from the device.
Does TestDock require an account or backend?
No. It has no TestDock account, synchronization service, analytics, advertising, or collaboration backend.