Test complete does not launch Tested Application
Hello,
I had a functioning suite of scripts that I was developing in one machine, and then executing them in a second machine.
The directory of the application under test has changed, so I updated the information on the TestedApp node. After the change, the scripts run with no problem in my development machine (Win 7 Enterprise). However, if I copy the test suite to the test machine (Win Server 2008 R2) then Test Complete is unable to launch the application.
(Note: I have only TestExecute installed in the test machine, so I launch it through the command line)
- If the tested app is already launched in the test machine, then test complete is able to execute the tests
- I have checked and rechecked the path of the tested application and the calls in the scriots in the test machine, and they match
- Tested application path are the same in both test and development machines
- When starting my scripts in the test machine, testexcute stops at the line invoking the tested application.
In an act of desesperation I have shorten the path of the test application, from about 69 characters to 47 characters lenght. The scripts this time were able to run with no trouble.
Is this a documented behaviour? Is there a way to get more debug information from TestExeucte? Any other idea of what could be wrong?
Thanks,
Carles Roch-Cunill
I had a functioning suite of scripts that I was developing in one machine, and then executing them in a second machine.
The directory of the application under test has changed, so I updated the information on the TestedApp node. After the change, the scripts run with no problem in my development machine (Win 7 Enterprise). However, if I copy the test suite to the test machine (Win Server 2008 R2) then Test Complete is unable to launch the application.
(Note: I have only TestExecute installed in the test machine, so I launch it through the command line)
- If the tested app is already launched in the test machine, then test complete is able to execute the tests
- I have checked and rechecked the path of the tested application and the calls in the scriots in the test machine, and they match
- Tested application path are the same in both test and development machines
- When starting my scripts in the test machine, testexcute stops at the line invoking the tested application.
In an act of desesperation I have shorten the path of the test application, from about 69 characters to 47 characters lenght. The scripts this time were able to run with no trouble.
Is this a documented behaviour? Is there a way to get more debug information from TestExeucte? Any other idea of what could be wrong?
Thanks,
Carles Roch-Cunill
