Packaging a Silk Test Classic Project

You can package your Silk Test Classic project into a single compressed file that you can relocate to a different computer. When you unpack your project you will have a fully functional set of test files. This is useful if you need to relocate a project, email a project to a co-worker, or send a project to technical support.

Source files included in the packaged project

When you package a project, Silk Test Classic includes all of the source files, meaning the related files used by a project, such as:
Description Extension
plan files .pln
script files .t
include files .inc
suite files .s
results files (optional) .res and .rex
data files -

Silk Test Classic takes these files and bundles them up into a new file with an .stp extension. The .stp file includes the configuration files necessary for Silk Test Classic to set up the proper testing environment such as project.ini, testplan.ini, optionset .opt files, and any .ini files found in the …\Silk Test Classic projects\<Project name>\extend directory.

You have the option of including .res and .rex files when you package a Silk Test Classic project because these files are sometimes quite large and not necessary to run the project.

Relative paths in comparison to absolute paths

When you work with Silk Test Classic projects, the files that make up the project are identified by pathnames that are either absolute or relative. A relative pathname begins at a current folder or some number of folders up the hierarchy and specifies the file’s location from there. An absolute pathname begins at the root of the file system (the topmost folder) and fully specifies the file’s location from there. For example:
Absolute path
C:\Users\<Current user>\Documents\Silk Test Classic Projects\<Project name>\options.ini
Relative path
..\tesla\Silk Test\options\options.ini or SUSDir\options.inc

When you package a project, Silk Test Classic checks to make sure that the paths used within the project are properly maintained. If you try to compress a project containing ambiguous paths, Silk Test Classic displays a warning message. Silk Test Classic tracks the paths in a project in a log file.

Including all files needed to run tests

Files associated with a project, but not necessary to run tests, for example bitmap or document files, which you have manually added to the project are included when Silk Test Classic packages a project.

If Silk Test Classic finds any include:, script:, or use: statements in the project files that refer to files with absolute paths, c:\program files\Silk\Silk Test\, Silk Test Classic verifies if you have checked the Use links for absolute files? check box on the Export Project or on the Email Project dialog boxes.

  • If you check the Use links for absolute files? check box, Silk Test Classic treats any file referenced by an absolute path in an include, script, or use statement as a placeholder and does not include those files in the package. For example, if there are use files within the Runtime Options dialog box referred to as "q:\qaplans\SilkTest\frame.inc" or "c", these files are not included in the package. The assumption is that these files will also be available from wherever you unpack the project.
  • If you uncheck the Use links for absolute files? check box, Silk Test Classic includes the files referenced by absolute paths in the packaged project. For example, if the original file is stored on c:\temp\myfile.t, when unpacked at the new location, the file is placed on c:\temp\myfile.t.

The following table compares the results of packaging projects based on whether there are any absolute file references in your source files, and how you respond to the Use links for absolute files? check box on the Export Project or on the Email Project dialog boxes.

Any absolute references in source files? Use links for absolute files? Results
No Checked or unchecked Package unpacks to any location.
Yes Checked Files referenced by absolute paths are not included in the packaged project.
Yes Unchecked Files referenced by absolute paths are put into a ZIP file within the packaged project.
Note:
  • If there are any source files located on a different drive than the .vtp project file, and if there are files referenced by absolute paths in the source files, Silk Test Classic treats the source files as referenced by absolute paths. The assumption is that the absolute paths will be available from the new location. Silk Test Classic therefore puts the files into a zip file within the packaged project for you to unpack after you unpack the project.
  • Files not included in the package - The assumption is that since these files are referenced by absolute paths, these same files and paths will be available when the files are unpacked. On unpacking, Silk Test Classic warns you about these files and lists them in a log file (manifest.XXX).
  • ip files – Because you elected not to use links for files referenced by absolute paths, these files are put into a zip file within the packaged project. The zip file is named with the root of the absolute path. For example, if the files are located on c:/, the zip file is named c.zip.

Tips for successful packaging and unpacking

For best results when packaging and unpacking Silk Test Classic projects:

  • Put your .vtp project file and source files on the same drive.
  • Use relative paths to reference the following:
    • include statements
    • options sets
    • use paths set within the Runtime Options dialog box
    • use statements in 4Test scripts
    • script statements
  • Uncheck the default Use links for absolute files? check box if your source files are on a different drive as the .vtp project file and if there are files referenced by absolute paths in your source files.

Packaging with Silk Test Classic Runtime and the Agent

If you are running Silk Test Classic Runtime, you may not package or email a project.

If you are running the Agent, you may package or email a project.