Legacy Dev Forum Posts

 View Only

Sign Up

Back to discussions
Expand all | Collapse all

Creating end-to-end tests validating conversation payloads

  • 1.  Creating end-to-end tests validating conversation payloads

    Posted 06-05-2025 18:07

    jmeline | 2023-09-28 22:47:46 UTC | #1

    Hi,

    I'm trying to create a couple end-to-end tests that take a hard-coded conversationId and then call /api/v2/conversations/{conversationId}. The response is the validated against our assertions. These conversationIds represent different scenarios and conversation types with attributes (phone calls, web messages, twoWayText/sms, etc). I would typically create a unit test that would validate a stubbed response, but I am trying go through the workflow of a couple micro-services.

    I got done with a couple tests but recently rerunning them, it seems like the attributes are no longer on them. I ended up changing conversationIds to get me test working but then I began wondering about my approach. Not sure what has changed or why the attributes would be missing after a month, however it make wonder if there is a better way to handle these types of tests. I could write unit tests where I mock out the response from /api/v2/conversations, but since I am trying to test the behavior through a couple micro-services, can I rely on the response from /api/v2/conversations/{conversationId} to always return the same payload?

    I have looked into programmatically creating a conversation (in this case, web chat), but I have struggled to format the query correctly using CreateWebChatConversationRequest and PostWebchatGuestConversationsAsync. Then again, I'm not sure if this is even an appropriate use of the system. If this is a recommended path, could you link me to any documentation that could help?

    Thanks,

    Eos_Rios | 2023-09-28 23:15:36 UTC | #2

    Not sure what has changed or why the attributes would be missing after a month

    https://help.mypurecloud.com/articles/view-participant-data-attributes/

    Note: Time to live (TTL) is 60 days for participant data. After 60 days, the data can only be accessed when it is exported.

    system | 2023-10-29 23:15:48 UTC | #3

    This topic was automatically closed 31 days after the last reply. New replies are no longer allowed.

    This post was migrated from the old Developer Forum.

    ref: 22285



Related Content