LAUD-302 - Comprehensive Multisplit

[gitstart-app]

Description

Comprehensive multisplit

Refs

#302

Demo

Multisplit

test_multisplit.mp4

uploadCSV

uploadCSV.mp4

Fixes #302

[gitstart-laudspeaker]

Hey @abheek9 Please check out these notes

Notes

During the testing, I found it unnecessary to manually import CSV files since the process involves numerous steps and needs to be performed in multiple tests repeatedly. Instead, I created a dedicated test specifically for the import CSV functionality. In this multi-split test, I addressed the import CSV functionality by directly issuing the network requests it involves. However, we can still include the entire uploadCSV functionality directly in the multisplit test if you find it appropriate.

Regarding the ticket description, it states that we should issue network requests to the events endpoint for each user attribute in the multisplit. However, I am still unclear about how this is linked to the multisplit. I understand that the multisplit triggers webhooks when certain conditions are met, such as a 1-minute delay and conditions in the multisplit branches. These conditions, however, seem unrelated to the events API. Could you please clarify how the events API connects with the multisplit?

test_multisplit_conditions.mp4

[gitstart-laudspeaker]

The uploadCSV API call is failing in CI, any idea why?

[abheek9]

@gitstart-laudspeaker this test does not look correct, right now each branch is using the same webhook, but in the instructions, each branch uses a different webhook. This is important because we need to know which branch is triggered from a specific event

[gitstart-laudspeaker]

@gitstart-laudspeaker this test does not look correct, right now each branch is using the same webhook, but in the instructions, each branch uses a different webhook. This is important because we need to know which branch is triggered from a specific event

Hey @abheek9 The webhooks are mentioned in the video description of the video, but it only mentions that the webhook can be our events endpoint. If you look closely at the webhooks, you notice that 3 branches share a webhook, and 2 also share a webhook.

[gitstart-laudspeaker]

Hey @abheek9 Earlier I had asked for clarification on how the events and the webhooks are connected, now it makes sense. So, if we use the events endpoint in the webhooks, then the multisplit branches can each trigger a different event, we can then check the triggered events to confirm that the multisplit actually triggers the webhooks

[gitstart-laudspeaker]

Hey @abheek9
I've updated the tests as illustrated below

multi-split.mp4

• Each branch is attached to a different webhook
• When the branch calls the webhook, it will emit an event to the events endpoint

However, I cannot see the events in the event-tracker meaning the API calls are not actually made, at what point are the users enrolled in the journeys(I also see no users in the journey) so that the web-hooks are triggered. I also created the journey manually as a normal user would and still don't see the events. Perhaps you can provide some insight into how the various branches are triggered.

events.mp4