QuickTest Professional (QTP) Fundamentals

Object repositories in QTP/UFT are exported and imported as XML files. XML format preserves the repository structure and object properties. TSR, MTS, and XLS are not standard formats for object repositories - TSR might be confused with test resource files, but repositories use XML.

When you create a new test in QTP, it automatically includes a single action by default. You can add more actions later, but the initial test has one. Tests with multiple actions are created by explicitly adding them, not by default.

The ImportSheet method in QTP's DataTable object imports a sheet from an external Excel file into the runtime Data Table. The syntax is DataTable.ImportSheet(filename, sheetSource, sheetDest). ImportTable and SheetImport are not valid methods.

The ObjectRepositories property (part of the Automation Object Model) returns a collection of all object repository files associated with an action. This allows programmatic access to manage repositories. Object Property and OR Property are not standard AOM properties.

The Wait statement in QTP pauses test execution for a specified number of seconds. WaitProperty waits for a property value, Sync waits for navigation, and Exit terminates a loop/action. Only Wait creates a simple time-based pause.

The Sync method (applied to Browser objects) waits for the browser to complete the current navigation before proceeding. This ensures the page is fully loaded. Wait is a time delay, WaitProperty checks object properties, and Exist checks for object presence.

Checkpoint results are viewed in the Test Results window after a test run completes. This window shows all checkpoint outcomes, screenshots, and pass/fail status. The Checkpoint window is for creating checkpoints, not viewing results.

Reusable actions can be called by other tests or actions, enabling modularity and code reuse. You call them using the 'Call to Copy' or 'Call to Existing' options. Split actions divide an action, Non-reusable actions cannot be called externally.

The GetCellData(Row, Col) method retrieves data from a specific cell in an HTML Table object in QTP. You pass row and column indices as parameters. GetData and GetRowValue are not standard QTP table methods.

Low-Level recording mode captures mouse clicks and keyboard input at screen coordinates when QTP cannot recognize an object using standard identification. It works around unrecognized objects by recording raw input actions instead of object-based operations. Normal recording requires object recognition, while Low-Level provides a fallback for difficult-to-identify objects.

The Object Repository is the central storage location where QTP maintains test objects along with their identification properties and corresponding values. It enables QTP to recognize and interact with application objects during test execution by mapping test script references to actual application objects. Other options like Data Table store test data, not object definitions.

GetROProperty retrieves the actual runtime property value of an object during test execution, reflecting the current state of the application. This differs from GetTOProperty which fetches property values from the Object Repository (test object definition), not the live application. SetROProperty is incorrect as it doesn't exist: RO properties are read-only runtime values.

F1 is the universal keyboard shortcut for accessing help documentation in most Windows applications, including QuickTest Professional. It launches the context-sensitive help system. F5 is typically for Run/Refresh, F2 for editing, and F3 varies by application but is not standard for help.

GetTOProperty retrieves property values from the Test Object definition in the Object Repository, while SetTOProperty can modify these property values temporarily during runtime. This differs from RO (Runtime Object) properties which are read-only values from the actual application. The TO properties control how QTP identifies and interacts with objects.

Object Spy is a QTP tool feature located in the Tools menu that allows you to view the properties and methods of any object in the application. It's used to inspect objects to understand their identification properties for building effective test scripts. The Tools menu contains utilities and configuration options.

The Test Settings dialog (File→Settings) in QTP contains 8 tabs that configure various aspects of test execution: Properties, Run, Resources, Parameters, Environment, Web, Recovery, and one more. This dialog allows comprehensive configuration of test behavior, execution parameters, and recovery scenarios. The number of tabs has varied across QTP versions.

The 7 tabs in Test Settings are Properties, Run, Resources, Parameters, Environment, Web, and Recovery. These tabs provide comprehensive control over test configuration from basic properties to recovery scenarios. Option A correctly lists all 7 tabs. Option B incorrectly adds 'Settings' to Web, and Option C says 'Run Options' instead of 'Run', while Option D says 'Input Parameters' instead of 'Parameters'.

QTP maintains a bidirectional relationship between Keyword View and Expert View: every operation in Keyword View corresponds to VBScript code in Expert View, and vice versa. Each object and method call in Expert View generates a corresponding row in Keyword View's table format. This synchronization allows testers to work in either view seamlessly.