Contributions
Re: TestExecute exit code?
Hi Tanya, I do use the /SilentMode tag, but I still don't see the directory. Maybe that means that TestExecute isn't truly starting up, and OS is throwing 127 (ERROR_PROC_NOT_FOUND as mentioned by Gena. What could cause OS to throw this exception when trying to launch TestExecute? I can go onto this same VM after it happened and launch TestExecute using the same script or manually. Thanks Motoo1.5KViews0likes0CommentsRe: Running TestExecute on a headless VM
Hi Simon, The problem in our case is that everything is automated, so there is no chance to login to a headless machine, whether it is from RDP or VNC. I am looking for a way to maybe open a virtual gui session automatically, maybe? I am thinking about trying to call VNC in loopback, but that's not very elegant solution even if it works. There is a way to use RDP for automation. It doesn't work in my case, but maybe you'll find this useful. Creat a batch file with the following lines: tscon.esxe 0 /dest:console tscon.esxe 1 /dest:console tscon.esxe 2 /dest:console tscon.esxe 3 /dest:console When closing RDP connection from the host, don't just close it, but to call the batch file (you can keep the shortcut close by). The gui automated test keeps running even when you close RDP window.1.6KViews0likes0CommentsRunning TestExecute on a headless VM
Hi all, I am trying to run TestComplete scripts using TestExecute on a headless VM. The VM is created automatically in clean state, installs TestExecute and other software, then launches the script. I got this error: Possible reason:The Switch User command was used. The test is run on a computer that is controlled via Remote Desktop, and the Remote Desktop Connection was closed.Learn more about the problem and possible solutionsTested object:Sys.Process("rundll32").Window("#32770", "Internet Properties", 1).Window("SysTabControl32", "", 1) Obviously there is a issue because the test VM is headless. Is there a way to get around this issue? Is there a automatic way to start a GUI session, so TestExecute can properly execute the test? Thanks, Motoo2.9KViews0likes3CommentsRe: Why does TestExecute 9.3 want to overwrite Script.tcScript?
Believe me. If it was up to me, I'd simplify it more, but I am not in an organization where I can drop hints and expect to change. There is a source control in the back. It's not one of those standard ones, and it's tightly integrated to automated build and automated test system including launching tests in farm. As you can imagine, whenever something is tightly integrated, things just can't be changed. I came in fairly recently into the organization, so there isn't much I can do at this point. I just need to find a way around it.1.3KViews1like0CommentsRe: Why does TestExecute 9.3 want to overwrite Script.tcScript?
The system is unique. It may be in-house solution. Without getting in too deeply (not because it's a secret, but because it's hard to explain), the system launches a vania Windows in cloud (we call it farm), installs everything, and runs the test. All test files are mapped over network where all the latest files exists. Basically, I have absolutely no write access to this network area. Use of TestComplete is new to the organization. It's definitely not TestComplete friendly.1.3KViews0likes0CommentsRe: Why does TestExecute 9.3 want to overwrite Script.tcScript?
Hi. Thanks for the reply. I think you are right about the version difference. The script was created with version 9.2. That said, I feel that the runtime engine of any kind should do any type of writing to the source files. This would mean that as soon as we upgrade TestComplete and TestExecute, we have to go through each objects and update them. Unfortunately, there is absolutely no option to make files writable in our environment. The only way to do that would be copy the file over only at the time of execution, but that's not very intuitive considering that commonly used script files can be in different places. It would add a lot of complexities.1.3KViews0likes0CommentsWhy does TestExecute 9.3 want to overwrite Script.tcScript?
I am trying to do a silent execution of TestExecute 9.3. In test environment, I found that the TestExecue was exiting with code 3. When I removed the "/SilentMode" tag, I found that TestExecute was trying to save Script.tcScript. Why? The problem is that all the files are source controlled and read only, so the test fails. Is there any way to get around this, besides making files writable? Thanks, Motoo2.2KViews0likes6CommentsTestExecute exit code?
Hi all, We are trying to automate TestExecute execution using Perl. We are using Perl's system() to run it. The problem is that I keep getting the exit code, 32512, and not execute the intended project suite. Looking around the web, I found that it means usually that the program (in this case, TestExecute) is returning 127. Unfortunately, I still don't know what the code means (I checked help file). What does it mean when TestExecute returns 127? Or 32512? Also, is there some kind of TestExecute log (not project suite log) that can tell me why TestExecute fails to run? If so, where can I find it? Thanks, Motoo2.8KViews0likes6Comments