Ok, here is where you could leverage again the Eggplant OpenSuite() command. Try putting your tests in suites named by category, and use OpenSuite(/path/to/CategoryName.suite). You then can make your calls or use your category type resources.
You are getting the right ideas, and moving to the logical solution is moving to a more modular and designed solution. You may want to sit back on a white board with some software engineers and see how you would either factor out functionality, or design and assign responsibilities and functionality to SenseTalk objects within a suite. This can save a lot of time, and allow the data abstraction occur that allows simplified maintenance and ease of factoring out later.
One thing to keepin mind, try and keep your handlers simple, small and embracing some very modular functionality to occur. This lends itself often to a more simplified implementation that has less bloat and more functionality as well as small meaningful handler names that are not easily forgotten or confused with others like it with minor changes.
Question, Answer, Formulate, Test, Implement, Test, Refine, Test, start over
The test building cycle is short and quick, the results are often astonishingly pleasing.
Sorry can’t speculate on future features of product or functionality, at least in public without NDAs in place