I agree with you in a lot of ways. I think changing the mindset of TestComplete in that way would be beneficial. I don't think it's a prerequisite though, at least not for the first suggestion (I can see where it would become a problem for the latter suggestions).
Where you can right click on a test group and run a focused test it should just be a matter of calling that function from the command line.
We've played with the idea of modifying the config files to tick test groups on and off (a small change that would be relatively easy). For now we've decided it best to consolidate our shared code. If there's more than two or three scripts we might want to rethink what code is being shared anyways (that is in our circumstance, other circumstances might simply need more sharing).
Still would be nicer if we could do things with one project and executing seperate test groups. And if it would load smoother even have all three of our platforms in one project suite (but that's too much for TestComplete in it's current state.....)
