Currently the TableProgramsTestBase allows to run tests on a collection environment and a MiniCluster by setting a testing parameter. This was done to cover different execution path. However, testing on a MiniCluster is quite expensive and should only be done in rare cases.
I propose to split the TableProgramsTestBase into
- TableProgramsCollectionTestBase and
to have the separation of both execution backends more clear.