• [Tech debt] Stabilize auditor e2e tests
    • False
    • Hide

      None

      Show
      None
    • False
    • To Do
    • QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
    • Release Note Not Required

      Our current implementation leads to a lot of instability when it comes to the auditor e2e tests. As such, I am creating a dedicated epic to track the work to make the tests more robust and hopefully increase the stability.

       

      Today, our tests perform an action within RHDH and then retrieve a set amount of the pod logs to look for appropriate event id for the action. As noticed with the RBAC auditor e2e tests, we need to increase the amount of lines that we capture dramatically to be able to retrieve the event id for an RBAC action. Even then, we still have moments where the event id is not captured and the test fails.

       

      We also have a number of catalog auditor and potentially scaffolder auditor tests that are either skipped or set to fixme.

       

      I propose that we have a better mechanism for retrieving the logs and insuring test stability

              gustavolira Gustavo Lira Silva
              rh-ee-pknight Patrick Knight
              RHIDP - Plugins
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: