The job to be done
How does TestDock help with release smoke tests?
Run the same short, ordered mobile workflow and preserve the observed pass, fail, skip, note, and screenshot evidence.
Testing stays close to the installed app. Open links or share/open-in flows through the operating system; inspect AASA and assetlinks configuration; validate and send through Expo Push, APNs, or FCM; and keep redacted results and scenario evidence on the device. TestDock has no account, sync service, analytics, or backend.
Recommended path
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.
Capabilities involved
The parts of TestDock used here.
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.
Its sections cover create a push setup, build a reusable payload, validate, send, and inspect, turn behavior into a scenario. Use it when you are ready to reproduce this workflow with your own project data.
Read the guideDirect answers
Questions about this use case.
How does TestDock help with release smoke tests?
Run the same short, ordered mobile workflow and preserve the observed pass, fail, skip, note, and screenshot evidence. The recommended path starts with exercise the installed app and uses push diagnostics and logs, persistent app profiles, reusable share inputs.
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.