Project

Profile

Help

Test #6313

Write tests to check sync optimization

Added by CodeHeeler 5 months ago. Updated 4 months ago.

Status:
CLOSED - COMPLETE
Priority:
Normal
Assignee:
Sprint/Milestone:
Version:
Platform Release:
Tags:
Sprint:

Description

Scenarios to test:

  1. First scenario
    1. run sync (following our workflow docs) once,
    2. there should be no optimization progress report on the task
  2. Second scenario
    1. run sync a second time with no other changes,
    2. there should be an optimization progress report now on the task
  3. Third scenario
    1. run sync a third time adding the flag 'optimize=False',
    2. there should be no optimization progress report now on the task
  4. Fourth scenario
    1. create a new repo version,
    2. run sync again (remove 'optimize=False' flag),
    3. there should be no optimization progress report
  5. Fifth scenario
    1. change remote policy to immediate,
    2. run sync again,
    3. there should be no optimization progress report
  6. Sixth scenario
    1. 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)
    2. run sync
    3. there should be no optimization progress report now on the task
  7. Seventh scenario
    1. run sync with no changes
    2. there should be an optimization progress report now on the task
  8. Eighth scenario
    1. run sync using the same repo, but a different remote
    2. there should be no optimization progress report now on the task
    3. rerun this sync
    4. 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.

Associated revisions

Revision 43c20db1 View on GitHub
Added by CodeHeeler 5 months ago

Added Tests for Sync Optimization

fixes #6313 https://pulp.plan.io/issues/6313

History

#1 Updated by CodeHeeler 5 months ago

  • Description updated (diff)

#2 Updated by CodeHeeler 5 months ago

  • Description updated (diff)

#3 Updated by CodeHeeler 5 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to CodeHeeler

#4 Updated by CodeHeeler 5 months 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.

#5 Updated by CodeHeeler 5 months ago

  • Status changed from ASSIGNED to POST

#6 Updated by CodeHeeler 5 months ago

  • Status changed from POST to MODIFIED

#7 Updated by dalley 4 months ago

  • Sprint/Milestone set to Pulp RPM 3.3.0

#8 Updated by dalley 4 months ago

  • Status changed from MODIFIED to CLOSED - COMPLETE

Please register to edit this issue

Also available in: Atom PDF