Create a reusable link
Save a custom-scheme URL, universal link, or Android app link with a descriptive name. Add parameter defaults, tags, and a favorite state when they make repeated testing faster.
Keep several routes in the same app profile so searches and recent history stay scoped to the target app.
Review before opening
Resolve required parameters and inspect the final URL before handing it to the operating system. TestDock records the accepted or rejected open request without claiming that a particular app or screen handled it.
When visual routing matters, record the observed destination in a manual scenario.
Verify app-link configuration
Use the association inspector for the exact host under test. Review Apple's AASA or Android's assetlinks data alongside the profile's platform identifiers and domains.
A valid association file is necessary configuration evidence, not proof that the installed build routed one specific URL correctly.
Use history deliberately
Recent opens make it easy to repeat a route and compare app behavior after a build change. Keep notes and parameters free of credentials because deep links can appear in operating-system and application logs.
Favorite stable release routes and remove obsolete links rather than building a general URL toolbox.
