QTP QuickTest Professional

QTP uses XML format for exporting and importing object repositories, making them human-readable and editable. MTS, TSR, and XLS are not used for object repository operations - TSR is a file extension, not the format itself.

Local object repositories are simpler for basic record and run tests because they don't require managing shared resources across multiple tests. Shared repositories add complexity better suited for modular, large-scale automation frameworks.

Object Spy is QTP's built-in tool specifically designed to view and retrieve object properties, methods, and identification properties. Recording captures actions, Net Spy doesn't exist in QTP, and Step Generator creates test steps.

SetTOProperty changes the property values of a test object dynamically during the run-time session only. It does not permanently modify or save these changes to the Object Repository on disk, making the statement false.

Scheme Validation is the recommended QTP functionality to verify object repository XML files conform to the QTP object repository schema. The other terms (Scheme Verification, XML Validation, XML Verification) are not actual QTP features.

QuickTest Professional (QTP) supports multiple file extensions for function libraries, including .qfl, .vbs, or even files with no extension at all. .bat files are batch execution files and are not supported as QTP function libraries.

TSR is the file extension for shared object repository files in QTP. MTR and MTS are not QTP file extensions, and QFL is for function libraries, not object repositories.

Both Datatable.Import and DataTable.ImportSheet can import data from .xls files during runtime. Excel.GetSheet is not a valid QTP method, and DataTable.GetSheet retrieves a sheet reference but doesn't import data.

QTP has three action types: Non-reusable (used only within the test), Reusable (can be called from other tests), and External (actions from other tests). 'End to End' is not a standard QTP action type.

In QTP/UFT automation, GetRoProperty ('Run-time Object Property') retrieves the actual property value from the application during test execution, while GetProperty retrieves values from the object repository. Options A, B, and D are not valid QTP methods for retrieving runtime properties.

In QTP (QuickTest Professional, which uses VBScript), both single quote (') and REM are valid comment markers. Option A shows the single quote method, and Option D shows REM, which is a legacy BASIC-style comment statement that VBScript supports. Options B (/*) is C-style syntax, and C (//) is C++/Java-style, neither of which work in VBScript.

Virtual objects in QTP (QuickTest Professional) allow you to map unrecognized custom objects to standard objects, enabling automation on non-standard controls. Options A (descriptive programming) and B (record) don't solve recognition issues for custom objects.

UCase() is the correct VBScript function to convert a string to uppercase. UpperCase and UpCase are not valid VBScript functions, and Upper is a method in some other languages but not VBScript.

ExitAction is the specific QTP statement that terminates execution of the current action and moves to the next action. Exit alone is used in procedures, 'Exit Action' with a space is invalid syntax, and Exit Now is not a valid QTP statement.

QTP (QuickTest Professional) does support VBScript classes. You can create and instantiate VBScript classes within QTP scripts for object-oriented programming and code reusability.

VBScript requires the 'Set' keyword when assigning object references. The correct syntax is 'Set CreatePage = New Pages'. Options A and B use incorrect syntax without Set or with wrong keyword order, and Dim cannot be combined with New in the same statement.

RowCount is the correct property/method to get the number of rows in a QTP WebTable object. 'Rows' is not a valid property, GetRows is an ADO method, and 'None of the above' is incorrect since RowCount exists.

DataTable.ExportSheet exports a specific sheet to a file, while DataTable.Export exports the entire Data Table. Both methods are valid in QTP for different export scopes. DataTable.Exports is not a valid method name.

Testing cannot prove software has no faults - it can only demonstrate the presence of faults. Complete absence of faults is theoretically impossible to prove through testing alone. Finding faults, building confidence, and identifying performance problems are all valid testing objectives.