Champion Level 3Here you go: http://support.smartbear.com/viewarticle/54705/
/project:project_name /test:test_name
TestExecute will run the specified test. Project_name specifies the name of the project that holds the desired test (use the same name as the one shown in the Project Explorer panel). Test_name specifies the full name of the desired test. The full name should include the test name, the name of the parent project item and (for scripts) the unit name separated by the pipe character ( | ) and enclosed in quotation marks. For example,"KeywordTests|Test1" or "Script|Unit1|Main". The test name should not contain the name of the Advanced folder or the names of other logical project folders.
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?)
