At present, Gating consists of a shell that checks whether the latest Jenkins build passed and then compares the version hashes of each component it is trying to promote with the versions saved in the attributes of the latest launch in the report portal.

We should investigate how to expand on this gating to automatically test UI changes before pushing changes to production. Note that it will not be possible for any significant suite of UI tests to achieve a 100% reliable 100% passing results. 

Things the project might be missing:

• SOPs / procedures to be followed when enabling/disabling tests in the various environments:
  • documentation of procedures that can be handled by anyone on the team, here you find the SOPs for Service Registry as an example: https://gitlab.cee.redhat.com/service-registry/srs-sops
• SRE awareness of the tests running:
  • When SREs are on-call for issues they normally run so-called playbooks, I think is important that UI E2E tests are mentioned there as a source of information about the status of the system
• Team's organizations and accounts pool for the various environments:
  • Regarding Orgs and accounts, I miss a place(Vault? Bitwarden?) where someone can look up for account credentials to safely run(for example) in development mode. I'm not aware of a document that explains, for each environment, the credentials that can be used and their quotas/limits. We discussed a bunch of times to have a pool for the team, but I haven't seen it happening.
• A process to keep track of and validate resolved issues (e.g. https://issues.redhat.com/browse/RHCLOUD-23176?focusedCommentId=21643899&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-21643899 )