Create a push setup
Choose Expo Push, APNs, or FCM for the selected app profile and add the target app's device token plus the stable provider credential required for a direct send.
Credentials remain scoped to the profile in operating-system secure storage. APNs accepts a .p8 key bundle with key ID and team ID; FCM v1 accepts Firebase service-account JSON. TestDock generates the short-lived APNs provider JWT or Google OAuth access token in memory when sending.
Build a reusable payload
Save alert or background-data templates with title, body, custom data, sound, badge, priority, time to live, collapse identifier, channel, or category as supported by the provider.
Use focused templates for behavior the app implements, such as opening a conversation, refreshing background data, or exercising a notification action.
Validate, send, and inspect
Pair an active push setup with a payload template. Before sending, TestDock measures the provider payload, checks provider-specific rules, and warns about known or approaching credential expiry.
The log keeps redacted provider results and translates common rejection codes into practical next steps. Provider acceptance still does not prove device delivery or target-app handling.
Turn behavior into a scenario
Write ordered steps with an observable expected result and mark each pass, fail, or skip during the run. Add concise notes and screenshot evidence where the status alone is not enough.
Completed runs remain immutable; start a new run when testing a fix so the earlier result is preserved.
- Keep one primary outcome per scenario.
- State what pass looks like.
- Avoid credentials in notes and screenshots.
- Share only reviewed result exports.