FTP Plugin - Target

What ?

A ftp target is exactly what you think it is.

Category-name : ftp.target

Configuration : A simple .properties file dropped in the ‘targets’ directory of your test project. The file must include the shebang on the very first line : ‘#!ftp’. It must also contain AT LEAST : ‘squashtest.ta.ftp.host’.

Available properties :

  • squashtest.ta.ftp.host : Supply the host name (mandatory).
  • squashtest.ta.ftp.username : The username to log to.
  • squashtest.ta.ftp.password : The corresponding password.
  • squashtest.ta.ftp.port : An alternate command port.
  • squashtest.ta.ftp.filetype : The default files type. Currently supported : ascii or binary (either uppercase or lowercase).
  • squashtest.ta.ftp.system : The host system type. Currently supported : unix, vms, windows, os/2, os/400, as/400, mvs, l8, netware, macos (either uppercase or lowercase).

Example of valid configuration file :

#!ftp
squashtest.ta.ftp.host = myhost
squashtest.ta.ftp.username = tester
squashtest.ta.ftp.password = _tester
squashtest.ta.ftp.port = 50000
squashtest.ta.ftp.filetype = ascii
squashtest.ta.ftp.system = os/400

Remark

During the download from / upload on the FTP server :

  • If the property ‘squashtest.ta.ftp.filetype’ has the value ‘binary’, the file is identicaly transfered.
  • If the property has the ‘ascii’ value, the file is converted during the transfer (encoding, end-lines and end-file characters). The transfer mode ‘ascii’ allows to transfer files between heterogeneous systems. The server converts the file from its original format to a standard ‘8-bit NVT-ASCII’ format. The client then converts the ‘8-bit NVT-ASCII’ format file to the output format. Consequently when a binary file is transferred in ‘ascii’ mode, generally it’s corrupted during the transfer.