Feature/prod throttle #285
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
Purpose
Reduce API load spikes and avoid false alarms during automated Selenium test runs against production.
Summary of Changes
Add new
prod_throttlefixtureSlow down the following tests:
test_navbars.pytest_login.pytest_institutions.pytest_search.pytest_preprints.py::TestBrandedProviderstest_registries.py::TestBrandedRegistriesPagesReviewer's Actions
git fetch origin pull/285/head:feature/prod_throttleRun this test on production using the
smoke testmarkertests/test_navbars.py -sv -m smoke_testtests/test_login.py -sv -m smoke_testtests/test_institutions.py -sv -m smoke_testtests/test_search.py -sv -m smoke_testtests/test_preprints.py::TestBrandedProviders -m smoke_testtests/test_registries.py::TestBrandedRegistriesPages -sv -m smoke_testTesting Changes Moving Forward
We can make future updates as necessary with the new fixture
Ticket
https://openscience.atlassian.net/browse/ENG-8215