QuickTest Professional (QTP) Fundamentals

To enable Quality Center to execute QTP tests remotely, you must configure QTP to allow remote test execution by setting the 'Allow QC to run tests remotely' option. This permission must be enabled in QTP before Quality Center can control test execution.

In QTP/UFT, a WinObject representation indicates that QTP can detect the window handle of the object but cannot recognize its specific class or control type.

Descriptive Programming allows you to define objects dynamically in your code using property-value pairs, making it ideal for objects whose properties change at runtime. Regular Expressions have limited flexibility, while Parameterization is for test data, not object identification.

The Object Repository Manager handles both Local Object Repositories (test-specific .tsr files) and Shared Object Repositories (reusable .tsr files across multiple tests). This dual capability supports different test object management strategies.

Do...While loops evaluate the condition after executing the loop body, ensuring the code inside runs at least once before checking whether to continue. For loops, While loops, and basic Loop statements check conditions before execution.

In VBScript (used in QTP/UFT), placing Option Explicit at the top of a script forces the developer to declare all variables before using them.

Standard checkpoints in QTP verify object property values during test execution by comparing actual runtime values against expected values. This is the primary checkpoint type for property validation.

Output values can be directed to either the Local Data Sheet (action-specific) or the Global Data Sheet (shared across actions). The 'Either 1 Or 2' option correctly indicates both choices are available.

QTP supports parameterization across checkpoints (data-driven validation), test objects (dynamic property values), and database checkpoints (parameterized queries and expected results). This comprehensive parameterization enables flexible, data-driven testing.

The Exist(3) parameter adds 3 seconds to QTP's default object synchronization timeout. QTP first waits for the default timeout period, then adds the specified 3 seconds before returning false if the object is not found.

Object SPY is the dedicated QTP utility for investigating object properties, methods, and hierarchy. It provides detailed property information for any object in the application under test, distinct from the Object Repository which stores test objects.

The ChildObjects method returns a collection of all child objects that match the specified description properties from a parent object. This enables programmatic retrieval and manipulation of multiple similar objects.

The number '1' in DataTable.Value("Column1", 1) specifies the row index in the data sheet. The first parameter is the column name, the second parameter is the row number (1-based index).

In UFT (Unified Functional Testing), Object Identification is the feature where you define and configure the mandatory and assistive properties that the tool uses to identify and recognize test objects during runtime. The Object Spy is used to view the properties and methods of an object at runtime, while Object Repository Manager is used to manage shared object repositories. Only Object Identification lets you configure how the tool identifies objects.

In QTP (QuickTest Professional/UFT), the Properties tab in Test Settings displays associated add-ins available for the test. The Run tab controls execution settings, Resources manages shared files/objects, and Parameters handles test parameters. Properties is the standard location for add-in configuration.

The default browser navigation timeout in QTP is 90000 ms (90 seconds). This setting controls how long QTP waits for page navigation to complete before timing out. Options A (30s), B (60s), and D (40s) are incorrect defaults for this setting.

The shortcut key to Run from Step in QTP is CTRL + F5. This executes the test starting from the currently selected step. Options A (CTRL+F10), C (CTRL+F12), and D (CTRL+F2) are incorrect keyboard combinations for this action.

The Recovery Scenario Manager in QTP is available under the Resources menu. It allows defining scenarios for handling unexpected events or errors. Options A (File), B (Insert), and C (Automation) are incorrect menu locations for this feature.

Dynamic descriptive programming involves creating a Description object, adding properties and values to it programmatically, then passing this object to identify test objects. Static programming uses property-value pairs directly in statements. Scripting and Framework are not recognized categories of descriptive programming.