Skip to main content

I wanted to share some tips on how I go about QAing or testing a Journey Orchestrator program, as it has taken me some time to standardize my processes and identify the “best” way for my org to test our new programs before launching.

  1. Design your program as you believe it needs to be designed.
  2. Create a Clone of the program and title it TEST - Ename of program]. This is the program you will use for testing.
  3. *Shorten any conditional wait times, wait timers, and/or reminder times to allow for quicker testing
  4. Use CSV import to upload yourself as a participant
  5. Set your Uniqueness Criteria so that “Participant with same unique criteria can enter after...” SELECT ALL participant states. This will allow you to test multiple pathways as the same participant.
  6. Create a QA checklist so you can test scenarios as you go. Some common checklist items for me include “Sender is sent from Sender Email” … “Email template format looks good” … “Mappings worked as expected” … “Survey link worked” … “Survey preview looks good” … “CTA was generated” and so on. Your QA checklist will look different depending on your program model and goals.
  7. Create separate QA checklists for each pathway. For example, if your program has conditional waits that may take a participant on a unique path based on a survey response
  8. When you’re ready to begin testing, you can either change your program to Active status and then sync participants, or sync participants and then change program to Active. If you sync participants first (which is just yourself through your CSV import), turning your program to Active will launch the participant on the program. If you turn your program to Active before syncing participants, you will be able to manually add yourself to the program after syncing participants.
  9. Run your first test with yourself as a participant. Follow one of your pathways through to completion.
  10. To test another pathway, re-sync participants and you will see yourself added again as another participant. Add yourself to the program to test the second pathway. To test a third pathway, repeat the steps above. Continue repeating the steps of re-syncing participants, adding yourself to a program, and completing a pathway over and over until all pathways have been tested.
  11. When all testing is complete, delete your TEST program.

 

To test participant queries, I will re-create a participant query source as a Rule (if it is more complex) or through Report Builder (if it is a simpler query).

 

*Edited to include Heather’s recommendation

 

All in all, the way you test a JO program may depend on your program model and your own individual instance configuration of Gainsight, but this is the way that I have found works for me!

Love this, Sarah! 

I also like to add the person I’m building for in the CSV as well so that they can get the emails, CTAs, etc, and see firsthand how everything looks.  Also, you’ll want to shorten any conditional waits, reminders times, etc depending on how you have those set.  

Also, you’ll want to shorten any conditional waits, reminders times, etc depending on how you have those set.  

 

GREAT call out and something I completely forgot to add! Edited to include it, as I do this also.

 

I love the idea of including your stakeholder in the CSV upload file for their visibility in program functionality.

Thanks for sharing this tip @sarahmiracle , @heather_hansen . I’ve featured this topic on the JO category.

cc @PavanCh , @sshroff 

This is great, I’m bookmarking this right now!
Thank you for sharing!

thanks @sarahmiracle - wouldn’t it be great if there was a button to have a test participant added to JO?  Like once you’ve mapped all the fields from a given source, be able to click a button to “Add a Test Participant” and manually type in all the data in an entry form, or provide a CSV with all the fields?  Adding a new source of a CSV then forces you to re-map all the fields, etc.

thanks @sarahmiracle - wouldn’t it be great if there was a button to have a test participant added to JO?  Like once you’ve mapped all the fields from a given source, be able to click a button to “Add a Test Participant” and manually type in all the data in an entry form, or provide a CSV with all the fields?  Adding a new source of a CSV then forces you to re-map all the fields, etc.

I’d vote for this idea! ☝️

@sarahmiracle, @heather_hansen -- these are all awesome tips! Bookmarked!

Especially love the QA checklists and shortening the wait steps! 😎

Reply


Terms & ConditionsCookie settings