-
Notifications
You must be signed in to change notification settings - Fork 6
How to test channel related issues
Julien Portalier edited this page May 30, 2023
·
5 revisions
This was originally written to help testing the channel broker, but it might be also useful for other channel related issues.
- Get the Twilio Simulator up and running on STG 🆗
- Get the LGWSim up and running on STG
Without these simulators it will not be possible to run a survey with a realistic scale. (> 20000 respondents)
The sim channels should already exist in verboice and nuntium (if not go to Simulators readme files to learn how to do it)
- Set up a low limit to the channels (e.g. 5 to 10), to force the channel broker to work. For some realistic behavior, the channel capacity in surveda should be twice the channel limit in nuntium/verboice.
- For LGWSim follow these rules
- For Twilio simulator these rules
- Select the sim questionnaire
- Define the mode primary and fallback
- Add 50 to 100k respondents (make sure phone_numbers are unique and different from other tests so the contact attempts are easy to identify)
- Select the SIM channels (for each mode)
- Setup the schedule (the survey should run in a time window in which the testers can review the logs)
- The survey should last more than 1 day, ideally a few days 3 to 7.
- To guarantee that the survey will run several days we should take into consideration: Simulator env variables (SLEEP_SECONDS, DELAY_REPLY_PERCENT, DELAY_REPLY_MIN_SECONDS, DELAY_REPLY_MAX_SECONDS) contact window (from, to in survey schedule) and number of respondents. Adding more delay to the responses and a small contact window will help.
- Define cutoff rules, at least number of completes, ideally some quotas to evaluate if the channel broker somehow impacts in the quota completion