Is there any way to copy a file from Eggplant's Resources folder to the SUT's any Local Folder?

Eggplant Functional
, ,
1

I want to copy (Transfer) a file from Eggplant’s Resources folder to the SUT machine.

I tried the below command taken from the Eggplant Documentation but it is not working.

copy file “C:/MyRepoFolder/Main.suite/Resources/TestFile.txt” to “SUT:C/Temp”

Its not recognizing the Remote machine (SUT Path) Path.

Is there any other way to achieve this?

2

You can try this, but make sure you have a shared drive accesible on the SUT side.

//Moving Drive from Resources Section to Shared Drive.
set global reportExcelName to “MovedReport1.xlsx” – That is the name of the new report that will be moved to shared drive
copy file ResourcePath(“MyNewreport.xlsx”) to ResourcePath(global reportExcelName) – Make sure you have a report already created to copy in the resourcepath

set myExternalStoragePath to “C:\Users\blanscot\OneDrive - Keysight Technologies\Documents”
copy folder ResourcePath(global reportExcelName) into myExternalStoragePath

If it does not work for you, a peer suggested this:

Shell “c:\windows\system32\cmd.exe”,“/c”&&“robocopy”&&“/MIR”&&quote&“\TESTING-SRV\Users\Testing-SRV\Documents\Surath Durgaprasad”&quote&&quote&“C:\Users\DurgaPrasad S\Desktop\Temp”

3

A pretty big workaround, but you could put the file contents in the remote clipboard, then use eggplant scripting to go through the steps to create a new file on the SUT and put the contents of the clipboard in it.

2 Likes
4

The way I achieve this is with a git repo.
If I know a test needs a resource available on the local sut then that resource gets commited to a “sutresources” git repo.
A clone of that "sutresources repo is made on the sut.
At the beginning of every run I do a git pull to ensure the resource will be available.
Then the test can interact with that repo on the sut.
Hope that makes sense.

5

The file and folder commands within SenseTalk reference the client machine (i.e. the machine running Eggplant Functional) and not the SUT machine. The simplest way to move/copy files from your client machine to any other machine, SUT or not, is to make that location available as a lettered drive on the client machine. For example, you could map your S: drive to c:\temp on your SUT machine. I will say that your mention of the SUt machine makes me wonder what you will do with the file on the SUT. Knowing the answer to that might allow the forum to provide a more complete answer.