Capability overview
What does portable non-secret profiles do in TestDock?
Export and import versioned profile definitions while omitting credentials and delivery logs and disabling imported push setups until restored.
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
Keep useful evidence
Review redacted logs and share completed scenario results or a non-secret profile package when another device needs the same setup.
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
Export and import app profiles
Move reusable non-secret app definitions between devices while understanding omitted credentials, logs, and destination setup.
The guide covers use the versioned profile package, understand what stays behind, import and restore locally, retire stale data. 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 portable non-secret profiles.
What does portable non-secret profiles do in TestDock?
Export and import versioned profile definitions while omitting credentials and delivery logs and disabling imported push setups until restored.
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.