Uploaded image for project: 'Automation Hub'
  1. Automation Hub
  2. AAH-1701

Extend the sync tests suite in galaxy_ng repository

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Obsolete
    • Icon: Major Major
    • None
    • None
    • QE
    • None
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide
      • New settings added to the tests to configure a "Sync Source", a Hub instance to test from. This will usually be an Ephemeral or Stage environment.
        • Sync URL
        • Auth URL
        • Auth Token
      • To test basic sync functionality, we'll need to:
        • Verify the configured Sync Source and its credentials work
        • Fetch the list of collections from the source, so we know what content will be synced
        • Configure the rh-certified remote with the source settings
        • Initiate a sync job
        • Wait for the sync job to complete, which can be >1 hr
        • Verify the contents of the rh-certified repo match the expected content list fetched earlier
      • We also will want to a test variation that tests sync list behavior:
        • Will require the credentials be for an org admin user
        • Would use the synclist API to disable some (random?) set of the collections.
        • Will then run the sync testing like above, using the modified content list
      • Stretch goals:
        • Test sync with and without the namespaces already existing
        • Validate that existing content in the rh-certified repo is gone post-sync
        • Validate behavior of syncing collections with deprecated content
      Show
      New settings added to the tests to configure a "Sync Source", a Hub instance to test from. This will usually be an Ephemeral or Stage environment. Sync URL Auth URL Auth Token To test basic sync functionality, we'll need to: Verify the configured Sync Source and its credentials work Fetch the list of collections from the source, so we know what content will be synced Configure the rh-certified remote with the source settings Initiate a sync job Wait for the sync job to complete, which can be >1 hr Verify the contents of the rh-certified repo match the expected content list fetched earlier We also will want to a test variation that tests sync list behavior: Will require the credentials be for an org admin user Would use the synclist API to disable some (random?) set of the collections. Will then run the sync testing like above, using the modified content list Stretch goals: Test sync with and without the namespaces already existing Validate that  existing content in the rh-certified repo is gone post-sync Validate behavior of syncing collections with deprecated content

      Problem Description: We have no tests in our integration suite that exercise the sync capabilities between Private Automation Hub and ConsoleDot Automation Hub.

      Proposed Solution: We need tests implemented that can exercise and validate a sync performed between the usual test instance and a second, cloud-based instance to test from.

      Reminders:

      • Set the affected Component(s): Backend, Infrastructure, Pulp, QE, Security, UI
      • Apply labels "crc-automation-hub" and/or "private-automation-hub" to indicate if the issue is for Cloud Automation Hub, Private Automation Hub, or both

              ctorrens@redhat.com Christian Torrens
              cspealma@redhat.com Clara Spealman (Inactive)
              Archiver:
              ranumula@redhat.com Raju Anumula

                Created:
                Updated:
                Resolved:
                Archived: