Choose the app boundary
Create one profile for each mobile app identity you test. A profile is the durable home for that app's deep links, share fixtures, push setups, notification templates, scenarios, and local history.
Separate unrelated apps even when the same team owns them so schemes, tokens, and evidence never become ambiguous.
Add the app identity
Give the profile a recognizable name. TestDock scopes it to the platform currently running: add the iOS bundle identifier and associated-domain settings on iOS, or the Android package name and App Link settings on Android.
The profile describes the external app; it cannot change that app's build configuration or runtime environment.
Record every custom scheme
Add each URL scheme the installed app supports. Multiple schemes belong in the same profile when they route into the same app, such as a current scheme plus a compatibility alias.
Keep the scheme value exact and omit punctuation that is not part of the scheme itself.
Use profile readiness
The profile dashboard highlights missing reusable deep links, share fixtures, scenarios, active push setups, and notification templates. Treat these as setup cues, not generic utilities.
Start with only the capabilities the app exposes and add the rest when the target app is ready to test.
