derek_gibson
12 years agoNew Contributor
TestExecute Automation
I didn't see a separate TestExecute forum so I'm hoping my question could be answered here. It's a rather complicated question so I'll describe the setup / problem in detail.
I have one TC Project Suite that contains a single Project with all my test scripts. Within this Project I have set up groups for Smoke Test & Regression Test and have other groups for Common Scripts & Old/Archived. When I run the tests manually I can right click the group (e.g. Smoke Test) and just execute those items but TestExecute doesn't appear to have anything supporting that. I read in another forum that you have written a .js script that is able to launch a specified group of tests but I don't think that solution is going to work for me. This is because I am intending to plug TestExecute into the build process (we use TeamCity) via a MSBuild script. If the build script were to call a .js file to launch the test group then the build software will not know if the tests pass or fail.
My best-case solution would be for TestExecute to add an ability to specify a Group instead of a Test Item or Project. An alternate solution would be to separate my groups into Projects and just execute whichever project I want from the MSBuild script. My concern with that is how much work would I have to do to each script by pulling it out of the Project into a new one? I'm guessing that would be a monumental job.
Do you guys have any suggestions?
I have one TC Project Suite that contains a single Project with all my test scripts. Within this Project I have set up groups for Smoke Test & Regression Test and have other groups for Common Scripts & Old/Archived. When I run the tests manually I can right click the group (e.g. Smoke Test) and just execute those items but TestExecute doesn't appear to have anything supporting that. I read in another forum that you have written a .js script that is able to launch a specified group of tests but I don't think that solution is going to work for me. This is because I am intending to plug TestExecute into the build process (we use TeamCity) via a MSBuild script. If the build script were to call a .js file to launch the test group then the build software will not know if the tests pass or fail.
My best-case solution would be for TestExecute to add an ability to specify a Group instead of a Test Item or Project. An alternate solution would be to separate my groups into Projects and just execute whichever project I want from the MSBuild script. My concern with that is how much work would I have to do to each script by pulling it out of the Project into a new one? I'm guessing that would be a monumental job.
Do you guys have any suggestions?