Testing the Android SDK

This page provides a testing checklist to verify your Blueshift SDK integration. The most important thing is to ensure that your app works as it did before integrating with the SDK.

Testing overview

There are several components to verify:

1. SDK initialization - Ensure the SDK starts correctly and key events fire properly
2. Event tracking - Confirm events appear in the Blueshift dashboard
3. Push notifications - Verify notifications render correctly on devices
4. In-app messages - Test message display and triggering
5. Mobile inbox - Confirm inbox functionality works
6. Universal links - Verify deep linking works correctly

Each feature has detailed testing instructions in its respective documentation page.

Testing checklist

SDK initialization

What to verify:

• SDK initializes without errors
• Device ID is generated
• API key is valid
• Default events fire (identify, app_open)

Where to find detailed steps:

• SDK setup documentation

---

Push notifications

What to verify:

• Permission request appears (Android 13+)
• FCM token is generated and logged
• Test notifications are received
• Notifications render correctly
• Notification clicks are tracked
• Deep links work from notifications

Where to find detailed steps:

• Push notifications → Test section

Dashboard verification:

• Use Push Studio to create and send test messages
• Verify push delivery and click stats appear in campaign reports

---

In-app messages

What to verify:

• Activity is registered for in-app messages
• Test messages display correctly
• Event triggers work as configured
• Message clicks are tracked
• Deep links work from in-app messages
• Frequency capping works

Where to find detailed steps:

• In-app notifications → Test section

Dashboard verification:

• Use In-App Studio to create and send test messages
• Verify that in-app delivery and engagement stats appear in campaign reports

---

Mobile inbox

What to verify:

• Inbox displays messages correctly
• Unread count updates correctly
• Messages can be opened and marked as read
• Messages can be deleted
• Pull to refresh syncs messages

Where to find detailed steps:

• Mobile inbox → Test section

Dashboard verification:

• Send test messages to the inbox
• Verify inbox message stats appear in campaign reports

---

Universal links

What to verify:

• Intent filters are configured correctly
• Custom scheme test works (local testing)
• assetlinks.json is hosted and accessible
• Production universal links open the app
• Deep link routing works correctly

Where to find detailed steps:

• Universal links → Test section

Dashboard verification:

• Create campaigns with universal links
• Verify link clicks are tracked in campaign reports

---

Event tracking

What to verify:

• Events appear in Logcat
• Events appear in the Blueshift dashboard
• User attributes are set correctly
• Custom events are tracked
• Event parameters are captured

How to confirm in the dashboard:

1. Get your device ID from Logcat
2. Go to Blueshift dashboard → Users
3. Search by device ID
4. Check the user's activity timeline
5. Verify your events appear with correct timestamps and attributes

---

Campaign testing

Once individual features are verified, test complete campaigns:

1. Create a test campaign targeting your test device
2. Run the campaign
3. Verify campaign statistics appear correctly
4. Check that targeting and segmentation work as expected

For information on creating and managing campaigns, see Blueshift campaign guides.

👍

Need help?

Have questions or running into issues with your setup? Reach out to the Blueshift Support team for troubleshooting and guidance.

Reference documentation

For more information on using Blueshift, refer to the User Guides.