Mobile Deep Link QA Test Plan Builder
Create a QA plan for universal links, Android app links, deferred deep links, web fallbacks, attribution SDKs, and edge cases across mobile apps.
Prompt Template
You are a senior mobile QA engineer. Build a deep link test plan for the mobile app below. App description: [app name and primary flows] Platforms: [iOS, Android, web] Deep link types: [universal links, Android app links, custom schemes, deferred deep links, magic links] Example URL patterns: [paste routes] Authentication states: [logged out, logged in, expired session, new user] Attribution or link SDKs: [Branch, AppsFlyer, Firebase Dynamic Links, Adjust, custom, none] Expected fallbacks: [app store, web page, error page, onboarding flow] Critical journeys: [invite, checkout, password reset, content share, referral, subscription] Release context: [new launch, migration, regression test, campaign support] Known issues: [paste bugs or concerns] Provide: 1. Deep link inventory table with expected behavior by route 2. Test matrix across platform, install state, auth state, browser, and app version 3. Step-by-step manual test cases for critical links 4. Automation recommendations and sample pseudo-tests 5. Debug checklist for AASA files, assetlinks.json, SDK config, redirects, and caching 6. Edge cases: expired tokens, region restrictions, duplicate installs, tracking consent, bad parameters 7. Release readiness checklist and go/no-go criteria 8. Bug report template for deep link failures Be precise and practical for a QA team preparing a mobile release.
Example Output
Deep Link QA Plan — Referral Invite Flow
Route Inventory
| Route | Example | Logged Out | Logged In | No App Installed |
|---|---|---|---|---|
| Invite | /invite/{code} | open signup with code preserved | open invite preview | web landing page + store CTA |
| Password reset | /reset/{token} | reset screen | force token validation | secure web reset fallback |
Critical Test Case
1. Install production app build 4.8.0 on iOS.
2. Open Safari and tap https://example.com/invite/ABC123.
3. Confirm the app opens without an interstitial.
4. Log out and repeat. The signup screen should show referral code ABC123.
5. Delete the app, tap the same link, install from TestFlight, and confirm deferred attribution preserves the code.
Debug Checklist
- AASA file served without redirects and with correct content type
- Android assetlinks.json includes the release certificate fingerprint
- Route parser handles trailing slashes and UTM parameters
- SDK dashboard has the correct bundle ID/package name
Tips for Best Results
- 💡List real URL patterns; deep link bugs usually hide in route-specific behavior.
- 💡Test install state and auth state separately, because deferred links and logged-out flows fail differently.
- 💡Include browser and app version in every bug report to avoid ghost-chasing cached association files.
Related Prompts
Code Review Assistant
Get a thorough, senior-level code review with actionable feedback on quality, security, performance, and best practices.
Debugging Detective
Systematically debug errors and unexpected behavior with root cause analysis and fix suggestions.
Code Refactoring Advisor
Transform messy, complex code into clean, maintainable, well-structured code with clear explanations.