Software Testing and Quality Control

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.

Actions are marked as reusable in the Action Properties dialog in QTP. This is done by accessing the action's properties and checking the 'Reusable action' checkbox. Action Settings typically contain different properties (like name, description), Action Run Settings handle runtime parameters, and Action Call Properties manage how actions are called - none of these contain the reusable setting.

The DataTable.Value property (or shortcut DataTable("ParameterName", dtLocalSheet)) is the standard method to retrieve or set data in a QTP/UFT DataTable during a run. Import imports external sheets, while GetCell or GetValue are not standard DataTable retrieval methods.

Action iteration settings (number of iterations, which rows to run) are configured in the Action Call Properties dialog when you call an action from another test. Action Properties/Settings are for other configurations like object repositories.

The source property of a database checkpoint object in QTP represents the SQL query that retrieves data from the database. This query is used to fetch the result set that will be compared against expected values. The source is NOT the connection string (that's stored separately), not an identification number, and not the row count (though it may return rows).

QTP/UFT recovery scenarios support four trigger events: Pop-up window, Object state, Test run error, and Application crash (often referred to as QTP crash). Options A and B are incomplete and include VBScript events, which are not native recovery trigger types.

In VBScript (used by QTP), the 'Step' keyword controls the For loop counter increment (e.g., 'For i = 1 To 10 Step 2' increments by 2). '++' is C-style syntax, 'Next' just marks loop end, and 'Skip' isn't a VBScript keyword.

To handle unpredictable testing exceptions, one can use recovery scenarios.

Option A, Do Loop, is a programming construct used to execute a block of code repeatedly. It is not relevant to handling unpredictable testing exceptions.

Option B, Recovery Scenario, is a feature of automation testing tools that allows you to define a set of actions to be taken when a particular exception or error occurs during test execution. This option is the correct answer.

Option C, IFTHEN statement, is a conditional statement used in programming to execute a block of code based on a particular condition. It is not directly relevant to handling unpredictable testing exceptions.

Option D, Selectase statement, is not a valid programming construct or feature of automation testing tools.

Therefore, the correct answer is:

The Answer is: B. Recovery Scenario.

In QTP/UFT, typing a dot after an object in Expert View triggers the statement completion feature, which displays a drop-down list containing the child objects, methods, and properties available for that object.

Browser navigation timeout settings are configured in the Web tab of the Test Settings window (accessed via File > Settings). Properties typically contains general test settings, Resources manages test assets, and Web Settings would not be the standard tab name in most testing tools.

The Date function in Visual Basic returns the current system date from your computer. It does not return past dates, future dates, or just the concept of 'current date' without system context - it specifically retrieves the date set in your system.

The Now() function returns both the current date AND time as a single timestamp. Unlike Date() which returns only the date, Now() provides complete temporal information including hours, minutes, and seconds along with the calendar date.

Month(Now) extracts just the month number (1-12) from the current date and time returned by Now(). It does not return the full date, time, or year - only the numeric month component.

Component testing absolutely does involve regression testing to ensure code changes don't break existing functionality within the component. The statement 'Component testing does not involve regression testing' is false, making option D the correct answer to this negative question.

To solve this question, the user needs to understand what inspections are and what they are used for. Inspections are a type of static testing that involves a team of individuals examining code, documents, or other deliverables to identify defects or areas for improvement.

Now, let's go through each option and explain why it is right or wrong:

A. Variables not defined in the code: This option is correct. Inspections can help identify variables that have not been defined in the code, which can cause errors or unexpected behavior when the code is executed.

B. Spelling and grammar faults in the documents: This option is correct. Inspections can also help identify spelling and grammar errors in documents, which can affect the readability and clarity of the document.

C. Requirements that have been omitted from the design documents: This option is correct. Inspections can also help identify requirements that have been omitted from the design documents, which can lead to incomplete or incorrect designs.

D. How much of the code has been covered: This option is incorrect. Inspections are not typically used to determine code coverage. Code coverage is typically measured using tools such as test coverage analyzers or profiling tools.

Therefore, the answer is: D. How much of the code has been covered.