This page controls the activities that are performed when the Build Process is initiated for a Unified Functional Testing project.
The following general settings are available:
|Build startup script||Indicates if the Startup Script defined on the HPE UFT Page should be rebuilt with current settings.|
|Create object repository XML export shadow copies||
When selected, all object repositories will automatically be exported to XML. This is useful to always have a backup of your file in the event the binary data is corrupt. It
is also beneficial to provide object repository-based IntelliSense on machines without Unified Functional Testing installed.
Note: This option is only available when at least QuickTest Pro version 9.2 or higher is installed on the machine executing the build process. Otherwise it is ignored.
|Generate documentation||Utilizes the Documenter to build documentation for the project based on the information defined on the Documenter Page.|
When the Build Process is initiated, all tests that are part of the project can be processed with the options below.
Tip: You can exclude a file from processing by setting the Build Action property in the Properties tool window to
Note: Test Processing is only available on machines that have Unified Functional Testing installed because the Unified Functional Testing API is required to make these modifications.
|Associate function libraries||All libraries in the project will be associated to every test to ensure that functions from those libraries are available.|
|Associate object repositories to actions||All object repositories in the project will be associated to each action of every test to ensure object are available.|
|Update required add-ins||Ensure the necessary add-ins for every test are property configured based on the addin selection on the HPE UFT Page.|
|Use relative paths for file references||When possible, paths for file references will be relative to the location of the test from which it is referred.|