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

Split E2E tests into multiple steps for CPU efficiency

    • False
    • Hide

      None

      Show
      None
    • False

      Task

      Our E2E tests are configured with 9 CPUs for the whole CI run time, for the main step. This includes the setup of the cluster, deploying RHDH, Playwright test run, and then the cleanup.

      The only CPU-intensive part is where Playwright runs (around half of the main job step). The other parts would be working fine with as few as 100 mCPUs.

      Splitting it into multiple steps would be much more CPU efficient.

      Background

      Dependencies and Blockers

      QE impacted work
      Documentation impacted work 

      Acceptance Criteria

       

       

              Unassigned Unassigned
              zdrapela@redhat.com Zbynek Drapela
              RHDH Install
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: