Forum Discussion

Hanila's avatar
Hanila
Occasional Contributor
8 days ago

How to fully automate test complete UI test cases flow

I am running my test complete UI testcases via Azure dev ops pipe line. 

I have set up self hosted aged which is required to run in interactive mode. 

When I need to execute the pipeline, I need to manually RDP to my machine, run the agent. Even if I keep the agent running, I must be logged in to the machine till TsCon takes over the test session. 

To automate this starting step, I have requested my network admin team to set up a user account that does not require entering a username or password to log in to the machine. That request is considered too risky (Even with a dedicated VM).

Has any one of you had this issue? If so, how did you resolve?

 

  • Hanila's avatar
    Hanila
    Occasional Contributor
    7 days ago

    Thx for the reply Raghavani. Yes, I have gone through those documents. They all gave me the solution to let a user log in without authentication if I want to run the agent in interactive mode. My team put it down as it is not secure. Now I have found a way to run the agent without breaking any authentication process. Listing the solution in case anyone needs it in future. Created a Windows task to schedule a restart of my test machine. Create another regular task (Not basic) for agent to start on system restart, and in the actions -> arguments I have added the command /c start "" "folderstructure\run.cmd". This work as expected without the need to bypass any authentication protocols. 

    • rraghvani's avatar
      rraghvani
      Icon for Champion Level 3 rankChampion Level 3
      6 days ago

      On my VM, I've installed Azure pipeline agent, and I've configured it to automatically login my test user account (even after restarting the VM). I have task schedule, that launches a PowerShell script file. Within the PowerShell script file, I have all the necessary commands to do pre-request stuff, before calling SessionCreator. SessionCreator has all the necessary parameters, to launch the automation using specific screen resolution, exports logs and summary to a folder. All of this is done within the same account (test user account).

      I did this, to bypass the same IT issues you have.