Uploaded image for project: 'Red Hat Internal Developer Platform'
  1. Red Hat Internal Developer Platform
  2. RHIDP-3114

[QE] Define E2E Scenario - Bulk import from Git

Prepare for Y ReleasePrepare for Z ReleaseRemove QuarterXMLWordPrintable

    • 2
    • False
    • Hide

      None

      Show
      None
    • False
    • RHIDP-834 - Increase RHDH adoption with bulk import
    • RHDH QE 3259, RHDH QE 3260, RHDH QE 3261

      Story

      As a user of QE engineer, I want to to define prereqs and dependencies so that fully define the corresponding E2E scenario

      Background

      Dependencies and Blockers

       QE impacted work

      Acceptance Criteria

      Prerequisites if any are defined and required actions are listed as sub-tasks and completed

      The scenario is validated by engineering and any feedback is incorporated.

       

      E2E scenario : 

      • Navigate to Bulk Import:
        • From the sidebar, navigate to the Bulk Import section.
      • Add Repositories:
        • Click on the "Add" button.
        • Verify that the list of repositories is displayed.
      • Toggle to Organization:
        • Toggle the view to "Organization."
        • Verify that the list of organizations is displayed.
      • Select Repositories:
        • Select two or more repositories: one with an existing catalog.yaml file and another without it.
      • Create Pull Request (PR):
        • Click on "Create Pull Request"
        • Verify pre-filled PR details, including the title and annotations in the catalog.yaml file.
        • Click on "Save" to generate the PR.
      • Verify PR Creation on GitHub:
        • Open GitHub and verify that a PR is generated for the repository without the catalog.yaml file.
        • Ensure that no PR is generated for the repository that already has a catalog.yaml file.
      • Verify Repository Addition in Bulk Import:
        • Navigate back to the Bulk Import section and open the "Repository" tab.
        • Verify that the two selected repositories are listed: one with the status "Added" and another with the status "WAIT_PR_APPROVAL."
      • Re-add Repositories:
        • Click on "Add Repo" again.
        • Verify that the catalog.yaml files for the previously added two repositories are shown as already added.
      • Approve and Merge PR:
        • Approve and merge the PR with the catalog.yaml file on GitHub.
      • Verify Status Update in Bulk Import:
        • Navigate back to the Bulk Import section and verify that the status has changed to "ADDED."
      • Delete Repository:
        • Click on the "Delete" action to remove the already added repository.
        • Verify that the repository is no longer present in the UI.

              skhileri Subhash Khileri
              skhileri Subhash Khileri
              RHIDP - QE
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: