Open topic with navigation
When to Use UFT Automation Scripts
Creating a useful UFT automation script requires planning, design time, and testing. You must always weigh the initial investment with the time and human-resource savings you gain from automating potentially long or tedious tasks.
Any UFT operation that you must perform many times in a row or must perform on a regular basis is a good candidate for a UFT automation script.
The following are just a few examples of useful UFT automation scripts:
- Initialization scripts. You can write a script that automatically starts UFT and configures the options and the settings required for testing a specific environment.
- Maintaining your tests and components. You can write a script that iterates over your collection of tests and components to accomplish a certain goal. For example:
- Updating values. You can write a script that opens each test or component with the proper add-ins, runs it in update run mode against an updated application, and saves it when you want to update the values in all of your tests or components to match the updated values in your application.
- Applying new options to existing tests and components. When you upgrade to UFT, you may find that it offers certain options that you want to apply to your existing tests and components. You can write a script that opens each existing test or component, sets values for the new options, then saves and closes it.
- Modifying Actions and Action Parameters (tests only). You can retrieve the entire contents of an action script, and add a required step, such as a call to a new action. You can also retrieve the set of action parameters for an action and add, remove, or modify the values of action parameters.
- Calling UFT from other applications. You can design your own applications with options or controls that run UFT automation scripts. For example, you could create a Web form or simple Windows interface from which a product manager could schedule UFT runs, even if the manager is not familiar with UFT.