Run test modules in repeatable order

**What is the problem your feature is trying to solve?**
I believe the current functionality is that the test modules don't always run in the same order each time. For example sometimes the Services module tests run before the Connection module tests, yet on the next test the Connection module tests could run before the Services module tests. The exception seems to be the Protocol module tests, which always seem to get run first every time.

What is the reasoning behind this/what's the methodology?

**Describe the solution you think would solve the problem**
It would seem more consistent across reports to run the tests in the same order each time, or at a minimum print the results in the results table in the same order each time, irrespective of test module run order.

Start by tracing how test modules are discovered and executed, then inspect how the results table is assembled. The issue does not name files or tests; done means module execution or result display is deterministic across repeated runs, with the chosen ordering documented or reflected consistently.

Written by the indexing model from the issue text.