Issue with Test Execute closing processes
Hi All,
I am facing an interesting issue which i would like to detail out below:
- I have around 20 projects in test complete which does functional automation. Each project in test complete points to a feature in our application under test.
- We use cruise control to execute by invoking test execute command line as mentioned below:
"c:\Program Files (x86)\SmartBear\TestExecute 9\Bin\TestExecute.exe" C:\sand\FunctionalTest\<<category1>>.pjs /r /p:project1 /testitemgroup:feature1 /exit /DoNotShowLog /SilentMode /el:"reports.mht"
- We have been executing / scheduled tests execution for the past 5 months and was completely working fine. For the past 1 week, we have been facing the following issue:
1. Cruise control .net expects test execute to complete execution and pass on the success code so that the project build (Cruise Control terminology) completes and moves on to the next scheduled execution in the queue.
But sometimes, test execute process hangs (basically closes the project after execution) and waits for a long time (not sure what it waits for) and the execution used to complete after we manually kill the process.
After doing R & D on why this issue used to occur, i figured out that cmd.exe process was opened by one of the tests (many tests may be) and since that doesnt close, test execute keeps waiting and hence the issue - in order to fix this issue, in the clean up method of every project, i have implemented a small code snippet which looks for cmd.exe and kills it so that test execute can complete execution.
But this issue still persists - although close cmd.exe works, test execute still hangs. I have checked the automation server and upon manually closing cmd.exe (end process tree from task manager) would complete execution. once this issue occurs, this continues for other categories and when we restart, it doesnt occur for a while.
I guess test execute is trying to close all processes opened by it and hence the wait. Is there any way that i can solve this issue - may be an option which can kill all processes opened by test execute which can complete its execution.
Note: cmd.exe is added as a tested application in test complete project.
Kindly help me resolve this issue.
Regards,
Chethan
I am facing an interesting issue which i would like to detail out below:
- I have around 20 projects in test complete which does functional automation. Each project in test complete points to a feature in our application under test.
- We use cruise control to execute by invoking test execute command line as mentioned below:
"c:\Program Files (x86)\SmartBear\TestExecute 9\Bin\TestExecute.exe" C:\sand\FunctionalTest\<<category1>>.pjs /r /p:project1 /testitemgroup:feature1 /exit /DoNotShowLog /SilentMode /el:"reports.mht"
- We have been executing / scheduled tests execution for the past 5 months and was completely working fine. For the past 1 week, we have been facing the following issue:
1. Cruise control .net expects test execute to complete execution and pass on the success code so that the project build (Cruise Control terminology) completes and moves on to the next scheduled execution in the queue.
But sometimes, test execute process hangs (basically closes the project after execution) and waits for a long time (not sure what it waits for) and the execution used to complete after we manually kill the process.
After doing R & D on why this issue used to occur, i figured out that cmd.exe process was opened by one of the tests (many tests may be) and since that doesnt close, test execute keeps waiting and hence the issue - in order to fix this issue, in the clean up method of every project, i have implemented a small code snippet which looks for cmd.exe and kills it so that test execute can complete execution.
But this issue still persists - although close cmd.exe works, test execute still hangs. I have checked the automation server and upon manually closing cmd.exe (end process tree from task manager) would complete execution. once this issue occurs, this continues for other categories and when we restart, it doesnt occur for a while.
I guess test execute is trying to close all processes opened by it and hence the wait. Is there any way that i can solve this issue - may be an option which can kill all processes opened by test execute which can complete its execution.
Note: cmd.exe is added as a tested application in test complete project.
Kindly help me resolve this issue.
Regards,
Chethan
