Share this page
Relevant for: GUI tests and components
Use Maintenance Run Mode to update the test objects in the object repositories associated with your test or component when OpenText Functional Testing cannot locate one or more objects in your application during a run session.
When do you use Maintenance Mode?
When you run a test or component in Maintenance Run Mode, the Maintenance Run Wizard opens each time it encounters any of following problems and provides the described solutions:
|
Problem |
Solution |
|---|---|
|
Object cannot be identified in application |
If you point to an object in the application being tested, the Maintenance Run Wizard compares that object to the objects in the associated object repositories. Depending on how the property values of the object to which you point compare to the property values of the objects in the associated repositories, the Maintenance Run Wizard suggests one of several options for updating your test or component to reflect the changes in the application. You can also choose to add a comment to your test or component before the failed step. |
|
Object is missing from the object repository |
The Maintenance Run Wizard helps you add the missing object to the repository. You can also choose to add a comment to your test or component before the failed step. |
|
Object exists but can only be identified through Smart Identification |
Identifying objects using Smart Identification may cause tests or components to run slower. The Maintenance Run Wizard helps you modify the description of the object, so that Smart Identification is not needed. For more details, see Smart identification. |
Note: Maintenance Run Mode does not support complex checkpoint or output value types such as File and XML checkpoints and output values.
During the Maintenance Run, these checkpoints and output values run as they would in a regular run session and will fail if there are differences between expected and actual values.
Tip: Alternatively, update individual test object descriptions from the object in your application using the Update from Application option in the Object Repository window or Object Repository Manager.
For details, see Maintain test objects in an object repository.
Maintenance Run Mode prerequisites
|
Install Microsoft Script Debugger |
If it is not installed, you can use the OpenText Functional Testing Additional Installation Requirements Utility to install it. Access the Additional Installation Requirements Utility from the Start menu or the <Installdir>\bin\UFTInstallReqs.exe. |
| Normal test run mode |
Maintenance Run Mode can be run only when OpenText Functional Testing is set to use the Normal run mode. For details, see Test Runs Pane (Options Dialog Box > GUI Testing Tab). |
| User interface | Maintenance Run Mode can only be run on applications that have a user interface. |
Determine OpenText Functional Testing wait time
Determine how long OpenText Functional Testing waits for an object to be displayed before determining that it cannot be found. The default setting is 20 seconds.
Change the object synchronization timeout in the Run pane of the Test Settings dialog box.
For more details, see Run Pane (Test Settings Dialog Box).
Tip: After Maintenance Run Mode finishes you may want to return this setting to its previous value for regular test runs.
Run the test or component in Maintenance Run Mode
-
Click the down arrow next to the Run button in the toolbar and select Maintenance Run Mode.
-
Specify the results location and the input parameter values (if applicable) for the Maintenance Run Mode session.
-
Follow the steps in the Maintenance Run Wizard.
The run results open by default when the run session ends.
Merge changes to your shared object repository
After using the Maintenance Run Wizard, you may want to merge the objects from the local repository back to a shared object repository.
Use the Update from Local Repository option in the Object Repository Manager.
For details, see Update a shared object repository from a local one.
