Last modified November 30, 2018 by Shelly Wolfe

QA testing Conversations

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

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

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 a Conversation:

  1. Set up the QA device.
  2. Assign the QA device to your Conversation on the Preview and test screen of the campaign workflow.
  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 and test screen of the Conversation campaign workflow. For more information about this workflow, see Creating Conversations.

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.

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 and test screen of the Conversation workflow, 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 any 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 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 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 report. For more information, see Managing Conversations.
  • Change the status of your Conversation using the options on the individual Conversation report. For example, you can edit, launch, pause, or finish a Conversation depending on its current status. For more information, see Managing Conversations.