Capability overview
What does reusable share inputs do in TestDock?
Save text, URL, and local-file fixtures per app profile and open the operating system's real share or open-in flow.
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
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.
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
Test push delivery and repeatable app flows
Configure provider-specific push targets, reuse payload templates, and combine delivery checks with observable manual scenarios.
The guide covers create a push setup, build a reusable payload, validate, send, and inspect, turn behavior into a scenario. 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 reusable share inputs.
What does reusable share inputs do in TestDock?
Save text, URL, and local-file fixtures per app profile and open the operating system's real share or open-in flow.
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.