I know there is limitation to work with files inside SUT. Is there any updates on that?
I am looking for options to update a text file(consider like config files for the app installed inside the SUT) which will be present in the SUT machines. When I use the normal file updating code, it couldn’t find the respective folder or I am guessing, it’s looking inside the RunAgent’s machine.
Also, just trying to log error if no such folder until the above is achieved but it’s not working ie. not logging the error when running from DAI.
set base_path to "C:\Program files (x86)\MyApp"
If there is no folder base_path Then
LogError "Folder not exists"
End If
So, how I can access and update the file inside SUT? Appreciate any inputs.
You prefer a “background” way to do this without clicking buttons, the best approach is to use the shell command to run a remote script (via SSH or PowerShell) or use the ReadText function to have the SUT “read” the screen and confirm the folder is visible.
@clairehar557ris yes, I have done this by combining these approaches. But I was wondering if any updates from Eggplant side for easy files handling. Anyway, thanks for your inputs.
The ability to perform file manipulation across a SUT connection is highly dependent on the protocol being used and the permissions set by the administrator. For example, I have worked with customers who connect to a remote machine via Microsoft RDP (outside of Eggplant) to be able to access their Eggplant Functional environment. Some of them are able to copy files from their local machine and paste them to the remote machine, while others are not. I would recommend that you run a similar test: connect to your SUT machine using the same protocol that you use within Eggplant Functional (e.g. RDP, VNC), but using a tool such as MS RDP or RealVNC, and try the copy from local and paste to remote test. If it succeeds, work with your TCSM to submit a feature request. If it does not succeed, it is unlikely that Eggplant would be able to bypass that same restriction.