This section describes how to configure Virtual File System (VFS) source control profiles.
A VFS is an abstraction layer on top of a more concrete file system.
The purpose of a VFS is to allow client applications to access different types of concrete file
systems in a uniform way. Apache Commons VFS provides a single API for accessing various file
systems. It presents a uniform view of the files from various sources. The protocols that are
currently supported for VFS by Silk Central are:
- Protocol
- Description
- http
-
Copies the given file. This protocol type is also supported for copying and unpacking ZIP, JAR, or other zipped files. It
is required to specify a .zip file on a http server. For example, zip:http://myTestServer/myTests.zip. The .zip file will be extracted on the execution server.
- ftp
-
Copies the given file. This protocol type is also supported for copying and unpacking ZIP, JAR, or other zipped files.
- smb
-
Server Message Block (smb) copies all files and folders. This protocol can be used instead of a UNC profile. For example,
the VFS smb path smb://server-name/shared-resource-path is equivalent to the UNC path \\server-name\shared-resource-path.
Note: When you create a new ProcessExecutor test that uses VFS for source control, you need to specify the complete path to the
executable in the Executable Name field.