There are a several undocumented pitfalls when using openmcp-testing from a end-user/developer perspective. The most common ones are:
- not having rebuild the image after making changes
- accidental reference to an outdated or incorrect local image
Anyone coming from traditional kubebuilder projects is probably 'missing' ginkgo/gomega envtest based testing. We need to document recommendations on when to use basic go unit tests vs ginkgo/envtest vs openmcp-testing/e2e-framework test.
Additionally debugging service providers is currently not documented. This creates a steep learning curve for new developers, especially given the multi-cluster architecture of openMCP and its impact on local debugging.
Acceptance Criteria
There are a several undocumented pitfalls when using openmcp-testing from a end-user/developer perspective. The most common ones are:
Anyone coming from traditional kubebuilder projects is probably 'missing' ginkgo/gomega envtest based testing. We need to document recommendations on when to use basic go unit tests vs ginkgo/envtest vs openmcp-testing/e2e-framework test.
Additionally debugging service providers is currently not documented. This creates a steep learning curve for new developers, especially given the multi-cluster architecture of openMCP and its impact on local debugging.
Acceptance Criteria