Last modified November 22, 2014 by Gordon Glauser

QA Testing In-App Messages

Swrve’s in-app message QA testing functionality has two main purposes:

  • Your development team can use it to send test messages to your QA devices to ensure that in-app messaging is up and running before you create your first message.
  • You can use it to test out new in-app messages before you commit to launching them. You can also pause active in-app messages to QA test them.

You can only assign the following types of in-app messages for QA testing:

  • A new message that is currently in Draft status (not yet launched).
  • A message that was in Scheduled status but which you have unscheduled by clicking Unschedule on the individual in-app message screen.
  • A message that is currently in Paused status (that is, it was Active, but has been paused by clicking Pause & Edit on the individual in-app message screen).

There are three main steps involved in QA testing an in-app message:

  1. Set up the QA device.
  2. Assign the QA device to your message on the Preview & Test screen of the in-app message wizard.
  3. 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 wizard. For more information about this wizard, 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 click Add (+).

Step 3: A Logging link appears for each assigned QA device. Click this link to display the QA User Logging screen and view the most recent events for the selected device.

You can assign a QA device to only one in-app message at a given time. The same applies if you are A/B testing an in-app message — you cannot test multiple variants at the same time on the same QA device. If you assign a QA device to one variant and then try to add it to another, it is automatically removed from the first variant. To view message variants on the same device, switch the QA user on the relevant variant tab, and then close and reopen the app between switches.

Accessing QA Device Events

To access logging information for a QA device assigned to an in-app message, on the Preview & Test screen of the in-app message wizard, locate the device under the QA Users section and click 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 click 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:

  • Loading messages – you can identify which in-app messages the SDK downloaded by searching for campaign download success. This includes the full JSON (JavaScript Object Notation) of the message including rules and trigger points.
  • 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.

Next Steps

  • Launch your in-app message if you have not already done so or create a new message. For more information, see Creating In-App Messages.
  • View the message and its KPI data on the individual message screen. For more information, see Managing In-App Messages.
  • Change the status of your message using the buttons on the individual message screen. For example, you can edit, launch, pause or finish a message depending on its current status. For more information, see Managing In-App Messages.