Forum Discussion
How is TestExecute being launched, Batch or PowerShell script file? What parameters are you using?
The TestExecute is launched by QAComplete with information filled in the above window. The important part here is the Project path in the box "Project or Test to Run". I know using command line to run TestExecute could involve the "/exit" to make sure TestExecute to be closed, but in QAComplete, I don't see that option.
Additionally, the exactly same setting can works for TestExecute in Window10 PC, but cannot work for TestExecute on Windows Server version... So it is really a pain here.
- rraghvani4 months agoChampion Level 3
I'm not familiar with QAComplete at all, but I was going to suggest /exit parameter if you were using a batch file. Someone else may be able to give you a better answer.
- beginTC4 months agoOccasional Contributor
Thanks. I am using batch file sometimes and I agree that it is very important to remember having the "/exit" in there.
- rraghvani4 months agoChampion Level 3
I suggest creating a batch file with the appropriate parameters, to run TestExecute, and to test that there are no issues.
Do not use parameters such as start, which invokes another process.
- Hassan_Ballan4 months agoFrequent Contributor
To narrow it down, what happens if you manually run TestExecute command line? will it complete test run and terminates (you can use Windows Task Manager to validate)?
If it does not, it would be specific to Windows server.
If it does, it would be specific to QAComplete formulated command line and better to ask SmartBear support.
Related Content
- 4 years ago
Recent Discussions
- 3 days ago
- 3 days ago
- 6 days ago