Direct answer
What evidence can TestDock retain for a manual test case?
TestDock turns a short mobile QA checklist into an ordered scenario with observable outcomes. Each step can pass, fail, or skip, with notes and screenshot evidence, and a completed run becomes an immutable result that can be reviewed or shared.
Best for
Where this workflow fits.
- Release smoke tests that must be repeated consistently
- Capturing what was actually observed on a device
- Combining link, share, push, and ordinary UI checks in one scenario
Profiles and logs stay on the device, provider credentials use platform secure storage, and exports omit secrets.
Relevant capabilities
What TestDock brings to the job.
Practical workflow
From setup to a reviewed result.
Create an app profile
Record the app name, current-platform identifier, URL schemes, and verified-link settings that define the installed target.
Save reusable tests
Add deep links, share fixtures, push setups, notification templates, and manual scenarios to that app profile.
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.
Keep useful evidence
Review redacted logs and share completed scenario results or a non-secret profile package when another device needs the same setup.
Useful in practice
Related searches
One workflow, several common names.
This page focuses on manual test-case runner. People also describe the same or closely related job as mobile test case app, manual QA test runner, mobile smoke test checklist, test evidence capture.
Direct answers
Questions about manual test-case runner.
What evidence can TestDock retain for a manual test case?
TestDock turns a short mobile QA checklist into an ordered scenario with observable outcomes. Each step can pass, fail, or skip, with notes and screenshot evidence, and a completed run becomes an immutable result that can be reviewed or shared.
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.
Go deeper
Configure provider-specific push targets, reuse payload templates, and combine delivery checks with observable manual scenarios.
Read Test push delivery and repeatable app flows