Skip to content

test(perso): work around limitations on setPersonalizationStrategy #1179

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 23, 2020

Conversation

Haroenv
Copy link
Contributor

@Haroenv Haroenv commented Jul 23, 2020

fixes #1178

Basically the perso API has a limit of 15 calls per day, per application, which will make all tests fail. We prepare ourselves for this now, and also accept the 429 response to be correct

Copy link
Contributor

@eunjae-lee eunjae-lee left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This fix looks good to me.

I don't have much context (I did read #1178 though), but I feel like this way some test cases will be just skipped randomly (depending on how many times you run it on the day).
Ideally there should be an exception where a specific appId is allowed to call the api unlimittedly.

@Haroenv
Copy link
Contributor Author

Haroenv commented Jul 23, 2020

There's more context on slack (it's still an expensive operation, even if only for our test application), and we only accept this specific 429 (anything else will still error), so I think this makes the most sense

@Haroenv Haroenv merged commit 7101afe into master Jul 23, 2020
@Haroenv Haroenv deleted the chore/test-perso branch July 23, 2020 15:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

test: prevent error in CTS personalization test on 429 HTTP code
2 participants