Use patch deployments to add new or update changed files, drivers, or components in a previously installed full deployment. Patch deployments typically include only the files and installers you modified since creating the full deployment. Avoid using patch deployments when you need to reorganize files or add or modify a significant number of files on the test station computer.

Use full deployments to install a test system to a test station computer that does not include any previously installed version of the deployment. A full deployment includes all the required files and installers you configured in the TestStand deployment specification file (.tsd) for the deployment. Avoid using full deployments when you need to make only small changes or add or change only a few files on the test station computer.

Deployment Type Advantages Disadvantages Typical Use Cases Best Practices
Patch deployment
  • Smaller than full deployment it updates (Size is proportional to the size and number of changed files, drivers, components, and installers in the test system.)
  • Installs faster than full deployment it updates
  • Requires installed full deployment on test station computer to prevent installing files with missing dependencies
  • Creating patch installers requires the corresponding full deployment installer
  • Cannot uninstall the patch installer without uninstalling the full deployment installer
  • Can make only limited changes
  • Fixing bugs in full deployment
  • Adding new files or features to full deployment
  • Create cumulative patch deployments that include changes from all previous patch deployments you created from a full deployment
  • Create baseline patch deployments, from which you can create dependency patch deployments
  • Save the .tsd files to store information required to create dependency patch deployments
  • Validate the test system before deploying patch deployments
Full deployment
  • Installs to test station computer that does not have any previously deployed test system
  • Unlimited changes, such as deleting or moving files, when updating a previous full deployment on the test station computer
  • Inefficient for making changes to a subset of files in a previously deployed test system
  • Same or larger size as previous full deployment, even when you modify only one file
  • Same or larger size installer, which typically takes longer to install than patch deployments because installers for full deployments uninstall and then reinstall all the files in the deployable image
  • Providing foundation from which to create patch deployments
  • Frequently installing test systems to new test station computers (A single full deployment typically takes less effort to install than installing a full deployment and then installing several patches to update the test system.)
  • Changing a significant number of files, drivers, or components on the test station computer
  • Making changes beyond the limits of patches, such as deleting files or reorganizing the directory structure of files included in a previously deployed test system
  • Using different upgrade codes to install multiple versions of a test system side-by-side on test station computers
  • Save the .tsd file to store information required to create patch deployments
  • Back up .tsd files so you can revert changes if needed
  • Save the full installers to store information required to build patch installers