test:run-hypershift

Running E2E tests on a HyperShift cluster requires executing specific test scripts that validate MLflow, Phoenix, and authentication modules. You need a configured HyperShift cluster environment to perform pre-merge regression testing successfully.

Validating OpenShift features before merging is best achieved by running comprehensive end-to-end tests on a HyperShift cluster. This automation catches integration issues and regressions specific to OpenShift environments, ensuring platform stability before code changes are merged.

Yes, a configured HyperShift cluster is required to execute authentication validation. The end-to-end test scripts depend on the specific cloud-native environment provided by HyperShift to properly validate authentication modules and OpenShift-specific configurations.

Yes, you can use these scripts to test MLflow integration in an OpenShift environment. The full E2E testing suite specifically covers MLflow validation alongside Phoenix and authentication modules to ensure functionality within your HyperShift cluster.

A key limitation is that pre-merge validation for HyperShift requires a fully configured HyperShift cluster and specific test scripts. The automation is focused on OpenShift-specific functionalities and modules like MLflow, meaning tests may not cover unsupported external integrations.