Forum Discussion
- kevin_kapell9 years agoFrequent Contributor
Tanya - I understand what you are saying. Fortunatly I would be working with a local copy of the MDS file while all files are in a code repository that would not be changed so project corruption is not a problem.
Alex - Thanks for the pointer but that still does not solve the issue where I have a number of scripts that I may or may not want to run. To determine how many command line entries I need to make i still need to open TestComplete. That starts to limit the benifits of have TestExecute to allow me to distribute the execution of the scripts.
All I am looking for is the tree view with the enable/disable checkboxes that I get in TestComplete that I can use to set in the MDS file what is run. Something like that would make my life so much easier.
- TanyaYatskovska9 years agoSmartBear Alumni (Retired)
I guess that following approach should help you - you can create a simple text file where you will write the name of tests you want to execute. In TestComplete, you will need to create a function that will read that file and execute the tests by their names. Will it work for you?
- AlexKaras9 years agoChampion Level 3
I would agree with Kevin.
Text file is an option (like the mentioned ATR utility), but they both require either additional text file maintained manually and not from the same machine where TestExecute is expected to be run, or custom parsing of the project file, the action that is also not the best one.
Related Content
- 4 years ago
- 6 years ago
- 6 years ago
Recent Discussions
- 15 hours ago