Forum Discussion
The issue only happens when the PC is locked. If I start the task while logged in the testrun does start.
- rraghvani1 day ago
Champion Level 3
Hi MW_Didata as mentioned in Running Tests on Locked Computers,
Tests that do not interact with GUI can be run on locked computers. GUI tests or tests that simulate user actions cannot be run on locked computers, since when the computer is working in this mode, the user session is frozen (no windows can be shown) and the testing engine cannot simulate user actions
- MW_Didata1 day agoSuper Contributor
Hello rraghvani What do you mean?
The testrun does use the GUI, Taskscheduler starts a C# program (Or batch) and that starts the testrun with SessionCreator.exe.
Sessioncreator should create a session on the locked pc where TestExecute can preform the tests.
This worked for atleast the past 2 years, but suddenly I get back Exitcode 7 while I changed nothing.- rraghvani1 day ago
Champion Level 3
I have a VM which has TestExecute installed, and a PowerShell script, which has the following command, called by Task Scheduler at a given time.
& 'C:\Program Files (x86)\SmartBear\TestExecute 15\x64\Bin\SessionCreator.exe' RunTest /UserName:TestUser1 /password:'testuser1' /UseActiveSession /ScreenResolution:"1920*1080" /ProjectPath:"C:\Sandbox\TestComplete\ALS\ALS.pjs" /ExportLog:"C:\Sandbox\Log\TC_Automation_$tc_timestamp\index.html" /ExportSummary:"$summary_report" | Out-NullThe VM has been set up to automatically login user 'TestUser1', and the VM is always unlocked (this is my active session). When I invoke the script to launch SessionCreator, it will spool up another session to run the automation scripts.
SessionCreator
The utility opens interactive user sessions required for the TestComplete interaction with your tested application GUI. If an interactive user session is not opened, the test engine will not be able to access the GUI, and your tests will fail.