Currently each integration/e2e test file contains an init() loop over testBackends to register parameterized Describe blocks. This works but means every test file has to be touched when adding a new backend.
The ideal approach would be to drive the parameterization purely from the harness/suite level so individual test files stay backend-agnostic. One option: a RunWithBackends(t GinkgoTInterface, fn func(h *harness)) helper that each test file calls once, hiding the loop and harness construction internally.
The challenge is Ginkgo v2's init-time spec registration — worth exploring whether GinkgoWriter, shared container nodes, or a custom suite runner can absorb the loop without touching individual test files.
Currently each integration/e2e test file contains an
init()loop overtestBackendsto register parameterizedDescribeblocks. This works but means every test file has to be touched when adding a new backend.The ideal approach would be to drive the parameterization purely from the harness/suite level so individual test files stay backend-agnostic. One option: a
RunWithBackends(t GinkgoTInterface, fn func(h *harness))helper that each test file calls once, hiding the loop and harness construction internally.The challenge is Ginkgo v2's init-time spec registration — worth exploring whether
GinkgoWriter, shared container nodes, or a custom suite runner can absorb the loop without touching individual test files.