Apparently I have to write a script to do some COM magic. Which I'd rather not do, and I don't even know if this would work with a machine with just TestExecute installed.
This is just inexcusable. The more I work with TestComplete, the sadder I get.
Further reading, I don't think this would work with TestExecute at all. This is using COM to drive TestComplete. OK fine, but the machine won't have TestComplete installed. I could use COM to drive TestExecute, but TestExecute has neither GUI functionality nor command line switches to run test items.
If you have both TestCompelte and TestExecute, then you can leverage Distributed testing to 'control' the test run from TestComplete while it executes on the remote machine using TestExecute.
That's not my scenario. Our development group needs to run a set of regression tests before pushing changes to the repository. I'm not involved in running their tests. The tests are run on from their development machines.
I have solved this by writing small driver scripts that in turn run a subset of our tests. Essentially duplicating the "functionality" provided by test groups (I use scare quotes because if TestExecute can't run test groups, then what's the point?)
Champion Level 3I think I would set up a separate project for the developers with just the tests they need. Then they just run "Regression Tests" from TestExecute and managing what's in there is separate and doesn't interfere with your testing project. Just use "Add Existing" to put the right groups/tests in their project so they'll be pointing to the original copies of the tests and won't get out of sync.
