Maintenance: Planio will be observing a scheduled maintenance window this Sunday, November 10, 2024 from 20:00 UTC until 21:00 UTC to perform important network maintenance in our primary data center. Your Planio account will be unavailable for a few minutes during this maintenance window.
Test #6313
closedWrite tests to check sync optimization
Description
Scenarios to test:
- First scenario
- run sync (following our workflow docs) once,
- there should be no optimization progress report on the task
- Second scenario
- run sync a second time with no other changes,
- there should be an optimization progress report now on the task
- Third scenario
- run sync a third time adding the flag 'optimize=False',
- there should be no optimization progress report now on the task
- Fourth scenario
- create a new repo version,
- run sync again (remove 'optimize=False' flag),
- there should be no optimization progress report
- Fifth scenario
- change remote policy to immediate,
- run sync again,
- there should be no optimization progress report
- Sixth scenario
- ideally, we need a revision number change to the repomd in our fixtures (do we have a setup for this already? Is this within the scope of our automated tests)
- run sync
- there should be no optimization progress report now on the task
- Seventh scenario
- run sync with no changes
- there should be an optimization progress report now on the task
- Eighth scenario
- run sync using the same repo, but a different remote
- there should be no optimization progress report now on the task
- rerun this sync
- there should be an optimization progress report now on the task
All of these syncs should be run in succession without cleanup in between as a first time sync should always leave no optimization progress report. If for some reason you wanted to separate the tests and needed cleanup in between, every test scenario other than #1 will need to have sync run twice, once at the beginning, and once when specified after the stated changes for the test.
Updated by CodeHeeler over 4 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to CodeHeeler
Updated by CodeHeeler over 4 years ago
We will not be doing scenario 6 for now (revision number changes).
Also, scenario 1 is not explicitly checked for as other tests will fail if optimization incorrectly occurs during initial sync.
Updated by CodeHeeler over 4 years ago
- Status changed from ASSIGNED to POST
Added by CodeHeeler over 4 years ago
Updated by CodeHeeler over 4 years ago
- Status changed from POST to MODIFIED
Applied in changeset 43c20db13d24682c984e0591dae2120aab1afe81.
Updated by dalley over 4 years ago
- Status changed from MODIFIED to CLOSED - COMPLETE
Added Tests for Sync Optimization
fixes #6313 https://pulp.plan.io/issues/6313