Capability overview
What does persistent app profiles do in TestDock?
Create a current-platform profile for each app with its custom schemes, platform identifier, verified-link settings, and reusable tests.
TestDock is organized around persistent app profiles rather than artificial environment switching. A profile is scoped automatically to the platform running TestDock and holds that app's platform metadata, URL schemes, verified-link configuration, saved deep links, share fixtures, push-provider setups, notification payloads, and repeatable scenarios.
In the workflow
Create an app profile
Record the app name, current-platform identifier, URL schemes, and verified-link settings that define the installed target.
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.
Useful in practice
Where this capability earns its place.
Related manual
Set up your first TestDock app profile
Create a persistent profile for an installed mobile app and record the schemes and platform metadata its tests depend on.
The guide covers choose the app boundary, add the app identity, record every custom scheme, use profile readiness. It is the best next step when you want to move from the product overview into a repeatable setup.
Read the guideDirect answers
Questions about persistent app profiles.
What does persistent app profiles do in TestDock?
Create a current-platform profile for each app with its custom schemes, platform identifier, verified-link settings, and reusable tests.
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.