Monday, December 29, 2008

Important Points Regarding Maintenance Run Mode

1. Microsoft Script Debugger should be installed to run the tests in Maintenance Mode. If it is not installed, you can use the QuickTest Additional Installation Requirements Utility to install it. (Select Start > Programs > QuickTest Professional > Tools > Additional Installation Requirements.)

2. When your application changes, you need to perform maintenance on all steps and test objects related to those changes. Maintenance Run Mode helps you to solve these types of problems during a test or component run.

3. In Maintenance Run Mode, QuickTest Professional identifies discrepancies between the objects in the repository and those in your application and then offers a solution for updating your objects and steps in real time.

4. The run (Maintenance Run Mode) pauses each time an object is not found. You can point to the required object in your application, and QuickTest will recommend a solution for updating your object repository and step to match the selected object. Alternatively, you can select to add comments to a problematic step and address it manually at a later time.

5. When the Maintenance Run Mode ends, Maintenance Mode wizard provides a summary of the changes it made to your test. The main Test Results window also contains a Maintenance Summary which displays details of the changes made to your test, including updated and added objects, updated and commented steps, and a summary of changes to the object repository.

6. You generally run Maintenance Run Mode when you know your application has changed and you expect that QuickTest will be unable to identify objects.

7. After you resolve the issue (with Maintenance Run Mode) the run continues.

8. You can run in Maintenance Run Mode only when QuickTest is set to use the Normal (displays execution marker) run mode. It cannot run in Fast mode.

9. You cannot run in Maintenance Run Mode on applications that do not have a user interface, such as Web services.

10. Maintenance run mode is designed for the production phase where tests need to be maintained as the application changes.

11. Maintenance Mode makes changes to the local object repository only.

12. Maintenance Mode does not remove the original step from your test or component. The original step is converted into a comment and the updated step is added below it.