Use cases
It is built for recurring mobile QA work that only makes sense close to the installed app: opening routes, invoking share/open-in flows, validating link associations, sending diagnosed push payloads, and recording observable outcomes.
Exercise parameterized custom schemes, universal links, and Android app links without rebuilding each URL by hand.
Create an app profile: Record the app name, current-platform identifier, URL schemes, and verified-link settings that define the installed target.
Read the complete use-case guideReuse the exact text, URL, or file inputs an app is expected to accept through the operating system's share/open-in flow.
Save reusable tests: Add deep links, share fixtures, push setups, notification templates, and manual scenarios to that app profile.
Read the complete use-case guideSend alert and background-data payloads directly through Expo Push, APNs, or FCM with per-app target setup.
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.
Read the complete use-case guideRun the same short, ordered mobile workflow and preserve the observed pass, fail, skip, note, and screenshot evidence.
Keep useful evidence: Review redacted logs and share completed scenario results or a non-secret profile package when another device needs the same setup.
Read the complete use-case guideKeep unrelated schemes, domains, push tokens, payloads, and test histories separated by app profile on one testing device.
Create an app profile: Record the app name, current-platform identifier, URL schemes, and verified-link settings that define the installed target.
Read the complete use-case guideReady for the implementation details?
Open the TestDock manual