Swrve’s in-app message QA testing functionality has two main purposes:
- For your development team to test messages on a QA device to ensure in-app messaging is working properly before you create your first campaign.
- For you to test the content of new in-app messages before you launch a campaign. You can also pause active campaigns to QA test them.
QA testing is available for campaigns in any of the following states:
- Draft – You’ve created a new campaign but not launched it yet or unscheduled a Pending (scheduled) campaign.
- Inactive – You’ve paused an Active campaign.
There are three main steps involved in QA testing an in-app message:
- Set up the QA device.
- Assign the QA device to your message on the Preview & Test screen of the campaign workflow.
- Access the QA device logs.
You can also perform advanced QA testing for iOS devices by checking the output of your app using the Apple Configurator utility.
Setting up QA devices
For detailed instructions on how to set up QA devices, see How do I set up QA devices?
Assigning QA devices
To assign a QA device to an in-app message:
Step 1: Navigate to the Preview & Test screen of the in-app message campaign workflow. For more information about the campaign workflow, see Creating in-app messages.
Step 2: In the QA Users section, select the required QA device(s) from the Add QA user list and select Add (+).
Step 3: A Logging link appears for each assigned QA device. Select this link to display the QA User Logging screen and view the most recent events for the selected device.
Accessing QA device events
To access logging information for a QA device assigned to an in-app message, on the campaign Preview & Test screen, locate the device under the QA Users section and select Logging. The QA User Logging screen displays the most recent event data from the QA device, the device properties and errors encountered. For more information about this screen, see How do I set up QA devices?
Advanced QA testing
Several trigger rules control when in-app messages are shown and when they are not. Each rule is configured in Swrve and then honored by Swrve’s iOS, Android, and Unity SDKs. When you combine rules it can be difficult to figure out why a message is not displaying during QA testing. The best way to see what rules are being used is to check the output of your app.
To check the output of your app for iOS devices, perform the following actions:
Step 1: Download the Apple Configurator from the App Store.
Step 2: Connect your device and view the console output.
Step 3: Start up the Apple Configurator, connect your device and select the Console tab of the utility.
Step 4: Start your app. The Console tab is now populated with data.
Step 5: Examine the console to identify data specific to in-app messages. For example:
- Message shown – search for sending view event, which is displayed each time a message is shown to users.
- Message not shown – search for not showing message, which is displayed each time a message is not shown to users.
- Review some common issues you might encounter when testing in-app messages. For more information, see Troubleshooting in-app messages.
- Launch your in-app message campaign if you have not already done so or create a new campaign. For more information, see Creating in-app messages.
- View the campaign and its KPI data on the individual campaign report. For more information, see Managing in-app messages.
- Change the status of your campaign using the options on the individual message report. For example, you can edit, launch, pause, or finish a campaign depending on its current status. For more information, see Managing in-app messages.