kylegogtp
Contributor
Joined 6 years ago
User Profile
User Widgets
Contributions
TestExecute logs out before tests run
Running our tests on Azure Pipelines using VMs that we disconnect from for the tests to run at night. Sometimes when tests run at night they cannot because TE needs to get logged back in. Is there a way to make sure it stays logged in or to have the pipeline sign in? I'm guessing this is just a standard login time out but this affects our nightly runs when it does time out. When they run and it logs out it just has this login page open when we check them.Log into windows automatically on Azure Pipeline
Hi, I have setup running our tests nightly on a Azure pipeline. This works if we disconnect using the tscon command. That said sometimes the VMs restart or get locked so tests fail. I setup an Interactive agent with auto-logon and it does not log in after restart. I went through MS documentation and the agent seems to be setup correctly and works with logged in and running. Is there any documentation to get tests running on pipeline if the VM is locked and not disconnected using the tscon command to keep it open? Thanks,Running test execute on pipeline causes 2 screens on vm
I have our test complete tests setup on an Azure pipeline. Our testers disconnect from their VMs at night using the https://support.smartbear.com/testcomplete/docs/testing-with/running/via-rdp/keeping-computer-unlocked.html When the tests run at night it is showing multiple screens: This happens to 2 different people.Issue with merging in branches where conflicts or changes do not show in the commit
Running the latest Test complete and Tortoise GIT. Lately, when pulling in the latest master or trying to merge in a branch the merge will not show any changes in the commit or it will show there are conflicts but not show or list any conflicts. I've tried reverting changes and merging in branches in different order or using different machines to try and merge. I have also re-cloned the repo on the machines and nothing seems to allow merges once in this state. I have to resort to manually merging tests and name mappings into a single branch and merge it in a single PR. I haven't had any issues like this until recently.
