Forum Discussion
TanyaYatskovska
Alumni
12 years agoHi Jose,
The TestComplete Integration object can help you. However, you will need to learn at least the name of the project where your keyword tests are located. If it's possible, you can do this by adding the following script when parsing the command-line parameters:
var tc = Sys.OleObject("TestComplete.TestCompleteApplication.10");
tc.Integration.RunTestByName("projectName", "KeywordTests|Test2");
You can get project and keyword test names by using the approaches listed in the How To articles.
Now, if you don't know the project name.
I guess you can get the full structure of a project from project files (*.pjs, *.tcKDT, etc.). However, you will need to create a parser to obtain this information from the files. There are many disadvantages in this approach. Here are the main ones:
- The structure of these files isn't documented. So, you will have to parse them yourself.
- If the structure of the files is changed, you will have to recreate your parser.
The TestComplete Integration object can help you. However, you will need to learn at least the name of the project where your keyword tests are located. If it's possible, you can do this by adding the following script when parsing the command-line parameters:
var tc = Sys.OleObject("TestComplete.TestCompleteApplication.10");
tc.Integration.RunTestByName("projectName", "KeywordTests|Test2");
You can get project and keyword test names by using the approaches listed in the How To articles.
Now, if you don't know the project name.
I guess you can get the full structure of a project from project files (*.pjs, *.tcKDT, etc.). However, you will need to create a parser to obtain this information from the files. There are many disadvantages in this approach. Here are the main ones:
- The structure of these files isn't documented. So, you will have to parse them yourself.
- If the structure of the files is changed, you will have to recreate your parser.