Forum Discussion
AlexKaras
12 years agoCommunity Hero
Hi Brad,
> The application which launched by TC runs as 'SYSTEM' user.
I think that the main idea of the thread referenced by Jared was that when testing applications with UI, both TestComplete and tested application must be started under the user account that have active desktop session. This is not TestComplete's requirement, but the feature of the Windows OS - the case is that the OS does not provide application with the desktop if application is started non-interactively and without desktop there is no place where UI can be displayed. TestComplete can run and execute test scripts without any problem when started from the command line even in non-interactive mode, but the test code fails to interact with the UI simply because there is no UI at all.
The solution for this problem is to start TestComplete (and, subsequently, the tested application) in the user session of the logged-on user with the desktop not been locked.
> The application which launched by TC runs as 'SYSTEM' user.
I think that the main idea of the thread referenced by Jared was that when testing applications with UI, both TestComplete and tested application must be started under the user account that have active desktop session. This is not TestComplete's requirement, but the feature of the Windows OS - the case is that the OS does not provide application with the desktop if application is started non-interactively and without desktop there is no place where UI can be displayed. TestComplete can run and execute test scripts without any problem when started from the command line even in non-interactive mode, but the test code fails to interact with the UI simply because there is no UI at all.
The solution for this problem is to start TestComplete (and, subsequently, the tested application) in the user session of the logged-on user with the desktop not been locked.