QTP / Unified Functional Testing

Browser Navigation Timeout is configured in the Properties tab of the Test Settings window in QTP/UFT. This tab contains various timeout settings and configuration options for test execution. Resources, Web, and Web Settings tabs do not contain this particular configuration.

The Information Pane in QTP/UFT displays Syntax Errors that occur during test creation and execution. Semantic Errors, Common Errors, and Logic Errors are not the standard error types shown in this pane. Syntax errors relate to code structure and grammar violations.

The Expand All option from the View menu expands all steps in the Keyword View of QTP/UFT. Expand is not a valid menu option. Expand Items and Expand Rows are not standard options for this purpose.

Environment variables in shell/operating systems come in two main types: built-in variables provided by the system (like PATH, HOME, USER) and user-defined variables created by the user. Option D correctly identifies both types. Option C is incorrect because 'User-function' is not a type of environment variable.

The overall test iterations are controlled by the Global Data sheet settings. If the Global sheet contains no data, the test runs exactly once by default. The local data sheet's row count only controls iterations within that specific action, not the overall test run.

When creating a Recovery Scenario in QTP/UFT, the Recovery Scenario Wizard first requires you to define the Trigger Event that interrupts the test run (e.g., a pop-up window or application crash). Recovery operations and scenario names are defined in subsequent steps.

Bitmap checkpoints in QTP compare pixel-by-pixel captures of UI elements, so they fail when screen resolution changes (different pixel density) or image size varies (different capture area). Object type alone doesn't affect bitmap comparisons; this is about visual rendering, not object recognition.

By default, QTP/UFT action call settings are configured to Run one iteration only. Even if the action's local data sheet contains multiple rows of data, it will not iterate through them unless the action properties are explicitly configured to run on all rows.

To solve this question, the user needs to know about output parameters in test automation. When running a test that contains both input and output parameters, the output parameter values are stored in the Run-time Data Table.

Option A: Local DataSheet is incorrect. A Local DataSheet is used to store data that is specific to a single action or component in a test script. It does not record the output parameter values.

Option B: Global DataSheet is incorrect. A Global DataSheet is used to store data that can be accessed by multiple actions or components in a test script. It does not record the output parameter values.

Option C: Run-time Data Table is correct. The Run-time Data Table is used to store input and output parameter values during the execution of a test. It records the output parameter values that are generated during the test run.

Option D: Design-time Data Table is incorrect. The Design-time Data Table is used to store input parameter values that are entered while designing a test. It is not used to record output parameter values.

Therefore, the correct answer is:

The Answer is: C. Run-time Data Table

The Object Repository Manager is the standalone tool in QTP/UFT used to manage, edit, and merge shared object repositories (.tsr files). The standard Object Repository tool is for local repository editing, whereas Test Settings and Associate Object Repository only link repositories.

Virtual objects in QTP/UFT are recognized based on exact pixel coordinates. If a virtual object is resized or moved, its coordinates change, rendering the existing definition invalid. Therefore, you must relearn the object to update the boundary definition.

In QTP, procedures created in the Function Library editor are saved with the .QFL extension (QuickTest Function Library). This is QTP's standard file format for storing reusable functions and procedures that can be associated with multiple tests. .INI files are configuration files, .TXT are plain text, and .VBS are standalone VBScript files - none of these are used for Function Library procedures in QTP.

The Step Generator in QTP categorizes steps into Test Objects (UI elements), Utility Objects (built-in objects like DataTable, Reporter), and Functions (user-defined or built-in functions). This categorization helps organize test steps and available actions in the Step Generator window. Options A and C list individual components rather than categories, and Option B's categories are incorrect.

New objects are primarily configured in QTP using the Object Repository, where you can add, modify, and manage test objects. While Virtual Object Manager exists, it's specifically for virtual objects (a special case), not general object configuration. Option C 'All the Above' is incorrect because the question asks for the standard method, and Option D is clearly wrong.

In QTP, block commenting can be done using Ctrl+M to comment out multiple selected lines of code. This shortcut adds comment markers to all selected lines simultaneously. Ctrl+T is typically used for other purposes (like merging), Ctrl+J is not a standard commenting shortcut, and 'None' is incorrect.

QTP (QuickTest Professional) has a technical limit of 255 reusable actions plus 1 default action, totaling 256. This is a hard architectural constraint in the tool; adding a 257th action will fail.

QTP uses VBScript syntax for loops: Do...Loop (with Until/While), While...Wend, and For...Next. Option C lists Select..Case (a conditional, not a loop), and Options A/B mix incorrect combinations.