Exporting/Importing Best Practices - Folder Structure, Naming, Clips & Results

Creating a consistent folder structure for projects is very important, particularly when projects may be shared amongst a number of people. Naming can also play a significant role for each project. Without proper naming, projects may become confusing, clips may be created in the wrong place and results may be harder to associate.

The general standard for folder structure should be like so:

While the structure of the sub-folders should almost always be the same, the name of the project should be followed by something distinct like "Project X - April 2013" or "Project X - Release 3.2."

Using this type of folder structure, and storing your items accordingly, reduces the chance that someone will modify one of your assets which may have an impact on your tests. For example, if you store a javascript at the root level rather than in the subfolder of a project, someone may modify that javascript and have an impact on your project without you knowing.

Exporting items is very simple if you follow the above naming guidelines and folder structures.

To export a project, simply right-click on the upper most project folder (in this case Project Name) and select export. Then check the boxes for "Also export objects that this object uses" and "Use a ZIP file (for faster download times)." and click OK.

Using these options ensures that all of the necessary objects are included in your export and that the file size will be more transportable, particularly if you are emailing the project to support.

These same options apply whether you are exporting a project, clip, target, etc...

To export results, the options are slightly different. Simply right-click on the results that you want to export and check the box for "Use a ZIP file (for faster download times)." and click OK.