QTP and JProbe Testing Tools

JProbe saves configuration settings with the .jpl file extension. This file stores your analysis configuration including what types of data to collect, filters, triggers, and other profiling settings. The other extensions are for different tools - .bat is a Windows batch file, .sln is a Visual Studio solution file, and .jpb might be mistaken but is not the standard JProbe settings extension.

JProbe uses port 52991 by default for communication between the profiler console and the profiled application. This port allows JProbe to attach to the JVM and collect profiling data in real-time. The other ports listed (52990, 52992, 52993) are incorrect default values, though JProbe may allow configuring a different port if the default is already in use or blocked by a firewall.

In JProbe memory analysis, the Runtime Summary view provides high-level diagnostics via the Memory, Heap, and GC tabs. Distractors are incorrect because Thread profiling belongs to performance/thread analysis, and Data Tab is not a standard JProbe memory summary panel.

The 'Set Recording Level' option in JProbe allows you to control the granularity and amount of data collected during profiling. You can choose from different recording levels based on your needs - from detailed method-level tracking to high-level overviews. This helps manage the trade-off between comprehensive data collection and runtime overhead. Trigger, Configure Pool, and Leak Doctor are other JProbe features with different purposes.

The Allocation View in JProbe displays information about where and how objects are allocated in memory during application runtime. Distractors like Instance View, Leak Doctor, and Object View serve other specific tasks like tracking memory leaks or inspecting individual object instances rather than listing allocations.

Leak Doctor View is specifically designed in JProbe to help identify memory leaks by tracking object allocations, garbage collection cycles, and objects that persist longer than expected. It analyzes reference chains and helps pinpoint why objects are not being garbage collected. Heap View shows overall memory distribution, Instance View lists individual objects, and Allocation View tracks where objects were created - none specifically target leak detection like Leak Doctor.

A deadlock is a state where a set of threads are permanently blocked because each thread holds a resource and waits for another resource held by another thread in the cycle. The distractors are incorrect because garbage collection and memory leaks relate to memory management issues, not thread synchronization conflicts.

Snapshot differencing compares two performance snapshots - typically before and after code changes. A positive result means the modified code took LONGER to execute (worse performance) than the original. This is calculated as (modified time - original time), so positive values indicate regression. If you wanted to confirm performance improvement, you'd look for a negative result showing the modified code runs faster.

In the context of the specific certification or tool pool this question belongs to, the data collected during code coverage analysis is categorized as Missed Column, Switch data, and Conditional Data. The other options contain incorrect combinations of coverage types.

When an application continuously crashes, it often indicates memory issues such as memory leaks, null pointer exceptions, or out-of-memory errors. Memory Analysis helps identify these problems by tracking object allocations, garbage collection patterns, and memory usage patterns that lead to crashes. Performance Analysis would be used for slowness or hanging, Coverage Analysis for test completeness, and Static Analysis for code quality without running the application.

In HP QuickTest Professional (QTP/UFT), creating a new action automatically generates three artifacts: a Local Object Repository (storing objects specific to that action), a Local Data Sheet (for action-specific test data), and a Folder (containing the action's resources and metadata). The Global Data Sheet, by contrast, is a single shared data table across all actions and is not created with each new action.

In VBScript (used in QTP/UFT and classic ASP), constants are declared using the Const statement, not Dim (which is for variables), Option Explicit (which forces variable declaration), or Con (which is not a valid statement). The Const statement creates a named value that cannot be changed during script execution, which is essential for maintaining code readability and preventing accidental modification of fixed values.

In VBScript and QTP procedures, arguments are passed by reference (ByRef) by default. This means the procedure receives a reference to the original variable, so any changes made to the parameter within the procedure affect the original variable. ByVal must be explicitly specified if you want to pass a copy instead.

QTP uses VBScript, which provides For...Next, Do...Loop, and While...Wend (or Do While...Loop) as looping constructs. Option B correctly identifies these three. Option A incorrectly includes 'Switch Case' which is a conditional statement, not a loop. Option C mixes 'If then' which is conditional, not iterative.

The Information pane in QTP displays metadata about the current test, including the test name and author. It does not primarily display syntax errors (those appear in syntax checking dialogs), license information (shown in Help menu), or comment lines (part of the test editor). Option B correctly identifies the test metadata displayed.

In QTP, the Object Repository Manager is the dedicated tool for merging shared object repositories. It provides a comparison view and conflict resolution for combining two repositories. You cannot merge repositories from within the Object Repository window itself during test editing, nor is merging limited to only local repositories (shared repositories can be merged too).

GetRoProperty is a generic QTP method that retrieves any runtime property of an object, including 'items count' for a WebList. The other options (GetList, GetItem, GetItemsCount) are not standard QTP methods. GetRoProperty('items count') returns the number of items as a string or number.

The ChildObjects method returns a collection object containing all child objects matching the description properties you specify. It returns a Collection object (not a simple count or boolean), which you can then iterate through using .Count and .Item(index). This is essential for dynamic object handling when you don't know exactly how many objects exist.

QTP environment variables come in two types: Built-in (predefined by QTP like TestName, ActionName, etc.) and User-defined (created by the user). Both types serve different purposes: built-in for system information and user-defined for test-specific data. Option C correctly identifies both available types.