Test Complete problem when program is opened by 'SYSTEM'
Hello,
Ran into a problem and could use some guidance...
When using Test Complete in a CI mode (using Smart Bear's Automated Build Studio with the CI task feature for example), this opens TestComplete and all programs Test Complete executes under the "SYSTEM" user.
Getting it to execute on screen is ok, as I have AutomatedBuildStudio set to being allowed to interact with the desktop.
The problem is, once the program I am testing is open, it always fails on the first real testing step because now the NameMapping doesn't match the program, even though it is the same program (running in simple mode).
I can run this same test script as multiple users on the same computer ok, its just when the program runs as "SYSTEM" that this error occurs.
I then go a different route, I leave the program open once it fails and try to remap it just incase the program windows run differently in SYSTEM, but after I map them, while the program is still running it says it can't find them again. So I am at a loss.
"SYSTEM" doesn't allow you to do a "RunAs", so I can't go that route. There is possibly the "Network Suite" route one could go for an issue like this (when system opens TestComplete, it remotes into another computer and runs the test under an actual user login). However, that seems more like a work around then an actual fix. Plus we would like to keep our "TestComplete" liceanse down to 1 and not have TestExecute (also with all the dependencies this program has, we simply don't have the space to create a virtual machine just for running test complete/TestExecute).
Any idea's? Also the program is Native VB6. Thanks in advance!
Ran into a problem and could use some guidance...
When using Test Complete in a CI mode (using Smart Bear's Automated Build Studio with the CI task feature for example), this opens TestComplete and all programs Test Complete executes under the "SYSTEM" user.
Getting it to execute on screen is ok, as I have AutomatedBuildStudio set to being allowed to interact with the desktop.
The problem is, once the program I am testing is open, it always fails on the first real testing step because now the NameMapping doesn't match the program, even though it is the same program (running in simple mode).
I can run this same test script as multiple users on the same computer ok, its just when the program runs as "SYSTEM" that this error occurs.
I then go a different route, I leave the program open once it fails and try to remap it just incase the program windows run differently in SYSTEM, but after I map them, while the program is still running it says it can't find them again. So I am at a loss.
"SYSTEM" doesn't allow you to do a "RunAs", so I can't go that route. There is possibly the "Network Suite" route one could go for an issue like this (when system opens TestComplete, it remotes into another computer and runs the test under an actual user login). However, that seems more like a work around then an actual fix. Plus we would like to keep our "TestComplete" liceanse down to 1 and not have TestExecute (also with all the dependencies this program has, we simply don't have the space to create a virtual machine just for running test complete/TestExecute).
Any idea's? Also the program is Native VB6. Thanks in advance!
