[release-0.4] TRACING-5505: [Chore] Fix and improve Tracing UI plugin tests

[IshwarKanse]

• Implement seamless test reruns and handle test interruptions.
• Use RBAC TempoStack and TempoMonolithic tests.
• Use multiarch images so that we can run the tests on IBM P,Z and ARM cluster architectures.
• Simplifies login.
• Adds Patternfly element selector commands.
• Improved documentation.
• Supports HyperShift logins.
• Uses Patternfly version agnostic commands and test steps.
• Uses Cypress best practices.

[openshift-ci-robot]

@IshwarKanse: This pull request references TRACING-5505 which is a valid jira issue.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[IshwarKanse]

/lgtm
/label qe-approved
/label ux-approved

[openshift-ci]

@IshwarKanse: you cannot LGTM your own PR.

In response to this:

/lgtm
/label qe-approved
/label ux-approved

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci-robot]

@IshwarKanse: This pull request references TRACING-5505 which is a valid jira issue.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[IshwarKanse]

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

[openshift-ci]

@IshwarKanse: Overrode contexts on behalf of IshwarKanse: ci/prow/upstream-amd64-aws-e2e, ci/prow/upstream-amd64-aws-fips-image-scan, ci/prow/upstream-amd64-aws-images, ci/prow/upstream-amd64-aws-lint

In response to this:

/override ci/prow/upstream-amd64-aws-e2e ci/prow/upstream-amd64-aws-fips-image-scan ci/prow/upstream-amd64-aws-images ci/prow/upstream-amd64-aws-lint

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[openshift-ci-robot]

@IshwarKanse: This pull request references TRACING-5505 which is a valid jira issue.

In response to this:

• Implement seamless test reruns and handle test interruptions.
• Use RBAC TempoStack and TempoMonolithic tests.
• Use multiarch images so that we can run the tests on IBM P,Z and ARM cluster architectures.
• Simplifies login.
• Adds Patternfly element selector commands.
• Improved documentation.
• Supports HyperShift logins.
• Uses Patternfly agnostic commands and test steps.
• Uses Cypress best practices.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci-robot]

@IshwarKanse: This pull request references TRACING-5505 which is a valid jira issue.

In response to this:

• Implement seamless test reruns and handle test interruptions.
• Use RBAC TempoStack and TempoMonolithic tests.
• Use multiarch images so that we can run the tests on IBM P,Z and ARM cluster architectures.
• Simplifies login.
• Adds Patternfly element selector commands.
• Improved documentation.
• Supports HyperShift logins.
• Uses Patternfly version agnostic commands and test steps.
• Uses Cypress best practices.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[JoaoFula]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: IshwarKanse, JoaoFula

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [IshwarKanse]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment