Skip to content

test: prevent error in CTS personalization test on 429 HTTP code #1178

@aseure

Description

@aseure

The personalization API is now limiting the number of
set_personalization_strategy() successful calls to 15 per day. Because of
that, our integration tests against the real API is not returning the following
error very often on our testing application:

{
    "status": 429,
    "message": "Number of strategy saves exceeded for the day"
}

Because of that, if the CTS is implemented in the client, we need to perform
the set_personalization_strategy() call in our integration test like before
but to prevent the test from failing if the 429 error is returned (considered
it as a "success" and moving on with the get_personalization_strategy() call).

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions