Relevant for: GUI tests and components
This task describes how to update your test or component data so that it is accurate for subsequent runs.
Specify the settings for the update run process.
For details, see Update Options Tab (Update Run Dialog Box).
In the Run dialog box, enter any required input parameter values in the Input Parameters tab.
When UFT One updates tests, it runs through only one iteration of the test and one iteration of each action in the test, according to the run option selected.
When a test runs in Update Run Mode, it does not update parameterized values, such as Data pane data and environment variables or property values of existing object descriptions in the object repository. To fix the object property values to match your application, use Maintenance Run Mode.
When UFT One updates tests or components, it always saves the updated objects in the local object repository, even if the objects being updated were originally from a shared object repository. The next time you run the tests or components, UFT One uses the objects from the local object repository, as the local object repository has a higher priority than any shared object repositories.
After using Update Run Mode to update the test or component, you may want to use the Update from Local Repository option in the Object Repository Manager to merge the objects from the local repository back to a shared object repository. For details, see Update a shared object repository from a local object repository.
The run results for an update run session are always saved in a temporary location.
Test objects that cannot be identified during the update process are not updated. As in any run session, if an object cannot be found during the update run, the run session fails, and information on the failure is included in the Run Results. In these situations, you may want to use Maintenance Run Mode to resolve these problems.
Because Update Run does not support updating complex checkpoint types such as File checkpoints and XML checkpoints, then these checkpoints run as they would in a regular run session and will fail if there are differences between expected and actual values.
When the update run ends, the run results show:
Updated values for checkpoints.
Updated test object descriptions.