Purpose

Use this test plan before sharing a Smart Link publicly. It verifies routing behavior across platforms and installation states.

Prerequisites

• An activated Smart Link.
• Access to at least one iOS or Android test device when mobile routing is configured.
• A production-like app build with the required platform association.
• The expected web, in-app, and store destinations written down before testing.

Test Matrix

Scenario	Expected destination
Desktop browser	Configured web destination or fallback
Mobile with app installed	Mapped route inside the app
Mobile without app installed	Correct App Store, Google Play, or web fallback
Unsupported platform	Safe web fallback
Shared in messaging or social media	Configured title, description, and image

Step 1 — Verify the Web Destination

1. Open a private browser window.
2. Paste the Smart Link directly into the address bar.
3. Confirm that the final destination, path, and approved query parameters are correct.
4. Repeat in a desktop and mobile browser when both experiences are supported.

Step 2 — Test With the App Installed

1. Install a production-like build on the device.
2. Open the Smart Link from a real clickable surface such as a message, email, or web page.
3. Confirm that the operating system opens the app without an unnecessary chooser or browser detour.
4. Confirm that the expected in-app route and content appear.

Step 3 — Test Without the App

1. Remove the app from the test device or use a clean device.
2. Open the same Smart Link.
3. Confirm that the correct store or web fallback opens.
4. If deferred routing is configured, install and launch the app, then verify the documented post-install destination.

Step 4 — Verify the Social Preview

1. Paste the Smart Link into a private draft or preview surface.
2. Confirm the title, description, and image.
3. Do not send the test message publicly until the preview is correct.

Pass Criteria

The test passes only when every configured platform and installation state reaches its expected destination without exposing private data or creating a routing loop.

Troubleshooting

• The browser opens instead of the app: verify the platform association, signing identity, domain, and path match.
• The wrong store opens: verify the iOS and Android fallback URLs separately.
• The app opens the wrong screen: verify the route mapping and parameter parsing inside the app.
• A redirect loops: remove circular fallback rules and retest in a private session.
• The share preview is stale: update the metadata and allow the sharing platform to refresh its cache.