Last modified July 7, 2015 by Shelly Wolfe

QA Testing Conversations

Swrve’s Conversation QA testing functionality has two main purposes:

  • Your development team can use it to send test Conversations to your QA devices to ensure that Conversations are up and running before you create your first Conversation.
  • Your product and marketing teams can test and preview Conversations on real devices, before they commit to launching the campaign.

You can only assign the following types of Conversations for QA testing:

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

There are three main steps involved in QA testing a Conversation:

  1. Set up the QA device.
  2. Assign the QA device to your Conversation on the Preview & Test screen of the Conversation 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 a Conversation:

Step 1: Navigate to the Preview & Test screen of the Conversation wizard. For more information about this wizard, see Creating Conversations.

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 Conversation at a given time.

Accessing QA Device Events

To access logging information for a QA device assigned to a Conversation, on the Preview & Test screen of the Conversation 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 Conversations are shown and when they are not. Each rule is configured in Swrve and then honored by Swrve’s iOS and Android SDKs. When you combine rules it can be difficult to figure out why a Conversation 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 Conversations. For example:

  • Loading Conversations – you can identify which in-app Conversations the SDK downloaded by searching for campaign download success. This includes the full JSON (JavaScript Object Notation) of the Conversation including rules and trigger points.
  • Conversation shown – search for sending view event, which is displayed each time a Conversation is shown to users.
  • Conversation not shown – search for not showing message, which is displayed each time a Conversation is not shown to users.

Next Steps

  • Launch your Conversation if you have not already done so or create a new Conversation. For more information, see Creating Conversations.
  • Edit the content of a new or existing Conversation. For more information, see Editing Conversations.
  • View the Conversation and its KPI data on the individual Conversation screen. For more information, see Managing Conversations.
  • Change the status of your Conversation using the buttons on the individual Conversation screen. For example, you can edit, launch, pause or finish a Conversation depending on its current status. For more information, see Managing Conversations.