Forum Discussion
kchoudhury
13 years agoContributor
Oh cool ill try that thanks ...
One more thing that i am having a problem with is , we initiate the command line runs from teamcity which is a build management system , the tests get triggered fine and teamcity holds the process until the run is over and exits gracefully when the tests are completed but if i start a test run and i want to stop it from teamcity it doesnt stop which is not the case if i use the default exe provided by testcomplete . If i am using the Testcomplete exe i can start and stop tests directly from teamcity ., so when i do a stop from teamcity the testcomplete/testexecute app process is killed.
I am not sure how that is handled for a console application , the thing that i think i am missing is i have to add a cancel event handler or something to my customexe , so that it can take cancel requests . If you can help me with this too would be great. I need it to work the same way it works in the default exe provided by testcomplete
One more thing that i am having a problem with is , we initiate the command line runs from teamcity which is a build management system , the tests get triggered fine and teamcity holds the process until the run is over and exits gracefully when the tests are completed but if i start a test run and i want to stop it from teamcity it doesnt stop which is not the case if i use the default exe provided by testcomplete . If i am using the Testcomplete exe i can start and stop tests directly from teamcity ., so when i do a stop from teamcity the testcomplete/testexecute app process is killed.
I am not sure how that is handled for a console application , the thing that i think i am missing is i have to add a cancel event handler or something to my customexe , so that it can take cancel requests . If you can help me with this too would be great. I need it to work the same way it works in the default exe provided by testcomplete
Related Content
- 6 years agoSol
- 3 years agovaishalisaid