Quick Test Professional and VBScript Fundamentals

In QTP/UFT, actions can be made reusable through the Action Properties dialog. This setting allows an action to be called from multiple tests, promoting code reuse and modularity. Call Properties (B) and general Properties (C) are not the correct locations for this setting.

The default browser navigation timeout in QTP/UFT is 60 seconds. This timeout controls how long the tool waits for a browser navigation operation (like page load) to complete before timing out. Options A (10s), C (20s), and D (30s) are incorrect default values.

The Wait method in QTP/UFT (inherited from VBScript) accepts seconds as a required parameter and milliseconds as an optional parameter. The syntax is Wait(seconds, milliseconds), where milliseconds can be omitted. Option B incorrectly states milliseconds are not supported, while option C incorrectly states they are mandatory.

QuickTest Professional (QTP) supports 8 standard checkpoint types (Standard, Image, Table, Text, Text Area, Bitmap, XML, and Database) and 6 output value types (Standard, Text, Text Area, XML, Database, and Image). Options A, C, and D show incorrect combinations of these numbers.

Using Option Explicit at the start of a VBScript file forces the developer to declare all variables before using them, preventing typos and bugs. Statements like Option Declare and Option Mandate do not exist in VBScript syntax, making them incorrect distractors.

VBScript supports only a single data type called Variant, which can contain different types of information depending on how it is used. Because of this, you cannot declare a variable of a specific type like Integer or String. This makes the statement true, rendering the false option incorrect.

GetROProperty (Run-Time Object Property) is used to retrieve the actual runtime value of an object's property, such as user input or dynamically generated values. GetTOProperty retrieves test object properties (descriptive properties), while SetTOProperty modifies test object properties but doesn't affect runtime objects.

Output values from functions, forms, or APIs can certainly be used to perform validation checks, such as verifying calculations or checking response status. Hence, the statement that they cannot be used is false.

A 2-dimensional array requires exactly 2 indices to reference an element: one for the row and one for the column (e.g., array(1,2)). Option B is incorrect because one index only works for 1D arrays. Option C is incorrect as 2D arrays don't use 3 indices. Option D is incorrect because all arrays require indices for element access.

Regular expressions CAN be applied to object repositories in QTP/UFT for flexible object identification. This allows matching objects with dynamic properties (like changing window titles or IDs) using pattern matching. This is a common technique for handling dynamic objects in automation.

In VBScript (and QTP/UFT), Functions DO return values, while Subroutines do NOT. The statement claims the opposite, which is incorrect. Functions use the function name to return a value, while Subroutines are used for procedures that don't need to return a value.

Local repositories are associated to tests through Test Settings (File > Settings > Resources), not through the Resources menu. The Resources menu is used for managing shared repositories (associating shared .tsr files). This statement is True - local repositories cannot be associated via the Resources menu.

The code creates a Description object for a Link (micclass="Link", name="username"), but then attempts to use it with WebEdit().Set method. This is invalid because a Link object cannot be treated as a WebEdit. The correct approach would be to either create a WebEdit Description or use a Link method like Click.

Breakpoints are a fundamental debugging feature in QTP that allow you to pause script execution at specific lines. This enables inspection of variable values and step-through debugging. The statement accurately describes this capability.

The Watch tab in QTP's debug viewer can monitor both simple variables and most object properties during runtime. It provides more comprehensive monitoring than just simple variables, but doesn't display every variable encountered - only those you explicitly add to the watch list.

Recovery scenarios in QTP follow a fixed sequence: first define the trigger event that detects the error, then specify recovery operations to fix it, and finally define post-recovery operations. This wizard structure ensures systematic error handling.

In software testing terminology, a 'bug' is most precisely synonymous with 'defect'. While 'error' refers to the human mistake that caused it and 'incident' refers to its manifestation, 'defect' is the standard term for the flaw in the software itself. 'Mistake' is too informal and 'incident' describes the observable behavior, not the underlying flaw.

Explaining test results neutrally is most critical for good tester-developer relationships. Understanding managers' values (A) is useful but secondary. Identifying workarounds (B) helps customers but doesn't directly maintain developer relationships. Neutral communication reduces defensiveness and promotes collaboration, making it the highest priority.

The question asks for a 'test type'. Component testing is a level, not a type. Functional testing and non-functional testing ARE test types. Acceptance testing is a level. Therefore 'Both 2 & 3' (Functional and Non-functional testing) is correct. These are the two main categories of test types based on what is being tested.