QTP/UFT Automation Testing Fundamentals

In testing tools like QTP/UFT, low-level recording captures granular user interactions as tracks, recording detailed mouse movements, clicks, and keystrokes. This is distinct from normal recording which operates at a higher abstraction level.

Object Spy in test automation tools like UFT/QFT is specifically designed to inspect and retrieve run-time properties and values of application test objects.

In QTP/UFT, shared object repositories are associated to tests through the Resources menu. The Associate Repositories option allows you to link shared .tsr (object repository) files to your test for reusable object identification across tests.

Object Identification in QTP/UFT is used to define and configure the properties used to uniquely identify objects during test execution. It does not retrieve runtime values - for that, you would use methods like GetROProperty to retrieve runtime object properties.

In QTP/UFT, the Step Generator (sometimes called Step Factory in documentation) is the feature used to construct test steps by selecting operations on test objects. Function Generator is used for inserting functions, not constructing steps with object operations.

In QTP/UFT DataTable object, the GetRowCount method is used to retrieve the number of rows in a sheet. Common alternatives like GetCount, Count, or RowCount do not exist or serve different purposes in the DataTable object model.

In QTP/UFT, under Test Settings > Run, the default configuration for DataTable iterations is to 'Run on all rows'. 'Run one iteration only' is a common alternative option but not the default.

The default object synchronization timeout in QTP/UFT is 20 seconds. This setting determines how long the tool waits for an object to appear or become available before timing out during synchronization operations like WaitProperty or Sync.

To retrieve a value from the DataTable in QTP/UFT, you need all three elements: the column/parameter name, the sheet name (global or specific action sheet), and the current row must be set as active. Without any of these, the value cannot be uniquely identified and retrieved.

In QTP/UFT, actions can be made reusable through the Action Properties dialog. This setting allows the action to be called from other tests, making it modular and reusable across multiple test scripts.

In QTP/UFT, the default setting for the Web browser navigation timeout is 60 seconds. Other options like 10, 20, or 30 seconds are common user modifications but not the default installation setting.

The Sync method in QTP/UFT is designed primarily for web applications to wait for page loads and navigation to complete. For Windows applications, different synchronization methods like WaitProperty or Exist are more appropriate and reliable.

The WaitProperty method in QTP/UFT takes three parameters: the property name to check, the expected value, and the timeout in milliseconds. It waits for the specified property to attain the expected value within the given timeout period.

The Wait method in QTP/UFT creates a pause for the specified number of seconds. While seconds are the primary parameter, the method can also accept optional milliseconds for more precise timing control, though this is less commonly used.