-
Spike
-
Resolution: Done
-
Normal
-
None
-
None
-
None
Based on feedback jerzhang@redhat.com received in the September 2nd OCP arch call, we should reconsider which MCO tests should run in which test suites. Currently, we have tests running in the default `conformance/serial` and `conformance/parallel` test suites as well as the team MCO disruptive suite, with some tests running in multiple suites.
It seems like the guidance is that tests should run in one suite that most appropriately matches the nature of the test. Further, it seems to be preferred that tests that can run in the default suites do run in those suites since they allow the tests to run alongside other components' tests. This work would involve confirming that guidance, understanding the currently existing MCO tests, and planning any necessary follow up work to clean up the MCO test landscape.
Done when:
- We have a current accounting of all MCO team regression tests, including information on which test suite they run in and the nature of the test
- There is a proposal of which tests should run in which test suite
- Relevant stories and bugs are created to track the efforts for moving any tests as a result of this investigation
Additional information:
- Arch call recording: https://drive.google.com/file/d/1JXh1dM3e40931Y7yCykUf1NdqZTGH3me/view?usp=sharing
- Jerry's question starts around 20:49 in the recording
- Arch call notes: https://docs.google.com/document/d/1cRmFnWs8k_QNFQvlOFCf0Yvx1sKpHlsJhFBb5ahMyC4/edit?tab=t.9dlxixbv2sk0
- Arch call agenda doc with notes: https://docs.google.com/document/d/1z25jsBi9lZVvQdZICG3QrA6j2C-8UIF2lxpN-b4HM2c/edit?tab=t.0#heading=h.ga4pvdisd2cf
- Related Slack convo: https://redhat-internal.slack.com/archives/GH7G2MANS/p1756825113717699