Swrve’s push notification QA testing functionality has two main purposes:
- Your development team can use it to send test push notifications to your QA devices to ensure the push notification integration is complete before you create your first push notification.
- You can use it to test out new push notifications before you commit to launching them.
You can only assign push notifications that are in Draft status (not yet launched) for QA testing.
There are two steps involved in QA testing a push notification:
- Set up the QA device.
- Test your push notification.
Setting Up QA Devices
For detailed instructions on how to set up QA devices, and for troubleshooting information on setting up QA devices for push notification testing, see How Do I Set up QA Devices?
Testing Your Push Notification
To test a one time or recurring push notification:
Step 1: Navigate to the Preview & Test screen of the push notification campaign workflow. For more information about creating a new push campaign, see Creating Push Notifications.
Step 2: In the QA Users section, click Test Push to the right of the QA device you want to use to test the push notification. This sends the push notification to the QA device and plays the sound you selected when you created the push notification.
Transactional Push API Campaigns
To QA test transactional push notifications using a web API, you must first create a transactional push API campaign and get the campaign-specific API key. For instructions on how to use the API key to QA test a Push API campaign, see Transactional Push API Campaigns.