Randomize (?) or otherwise improve the order of TestCases such that all cases are picked for action over time.

Randomization gets us so far. Better still might be to know historical test cases that have been executed and attempt to "fill in the gaps" first, before we run all possible tests.

No files, tests, or entry points are named. Start by locating the TestCase selection and execution flow, then determine whether execution history is stored; the issue needs a defined selection policy and completion criteria before implementation can be scoped.

Written by the indexing model from the issue text.