Most tests in the config-policy-controller have been updated to allow many of them to be run in parallel. However, most if not all of the OperatorPolicy tests are in one long Ordered container: https://github.com/open-cluster-management-io/config-policy-controller/blob/main/test/e2e/case38_install_operator_test.go . This was simpler for initial development, because the tests might re-use the same operators and by not running in parallel they can't interfere with each other, but the number of tests has grown a lot. It may already be at a point where these tests are the limiting factor for how quickly the tests can run overall.

This issue is open to any solutions that help those tests run quicker, while still verifying the same behaviors and providing sufficient code coverage. For example, some tests might be able to run in parallel already, and just need to be orchestrated better. Some tests might overlap with setup and tear down, and could be combined.