HP QuickTest Professional (QTP) and Quality Center (QC) Essentials

Low-level recording in QuickTest requires you to first be in normal recording mode. This establishes the recording context before you can switch to the more detailed low-level recording option.

QuickTest supports two types of environment variables: built-in variables provided by the system, and user-defined variables created by testers. This combination allows flexibility in test configuration.

When QuickTest runs in update mode, it refreshes the object descriptions in the object repository. This helps maintain test stability by updating object properties to match the application under test.

In QuickTest Expert View, typing an object name followed by a dot triggers IntelliSense-style autocomplete. This displays child objects and available methods for that object, aiding code completion.

In Quality Center (QC/ALM), requirements can be mapped to test plans within the Test Plan module. This allows traceability between requirements and test cases. The mapping ensures test coverage for all requirements.

In HP Quality Center (QC/ALM), users can switch between different projects if they have access permissions. QC is designed to manage multiple projects within the same domain, allowing users to work on different projects as needed.

ALT+N is the standard keyboard shortcut in Quality Center/ALM to create a new defect. This shortcut opens the defect form with blank fields for entering defect details. CTRL+N is typically used for new folders or test cases, while SHIFT+N and CTRL+SHIFT+N are not standard defect creation shortcuts in QC.

In Quality Center/ALM, test scripts (test cases) typically have 5 possible statuses: Not Completed, Passed, Failed, No Run, and N/A. This covers the full lifecycle of test execution from not started to various completion states.

Quality Center allows linking defects directly from the Test Lab module. After running a test, you can link a defect to the test run to track failures. This integration between Test Lab and Defects modules is a core feature for defect tracking.

Requirement mapping can be done from the Test Plan module in Quality Center. You can associate test cases with requirements to establish traceability. This Coverage Analysis feature shows which requirements are covered by which tests.

Quality Center supports project switching - users with permissions can move between different projects within the same domain. This is typically done through the project selection interface or by changing the project context in the session.

ALT+N is the keyboard shortcut in Quality Center/ALM for creating a new defect. This opens the defect entry form where users can fill in defect details like severity, description, and steps to reproduce. The other key combinations serve different purposes or are not standard shortcuts.

Test scripts in Quality Center have 5 standard statuses covering their lifecycle: Not Completed (not run), Passed, Failed, No Run (skipped), and N/A (not applicable). These statuses allow teams to track test execution progress and results accurately.

In QTP scripts, there are two tables by default: the Local DataTable (for test-specific data) and the Global DataTable (for shared data across tests). These are part of the Data Table structure used for data-driven testing.

In QTP, the Local Object Repository file uses the .MTR file extension (Mercury Test Repository). The .TSR extension is for Shared Object Repository files, not local repositories.

In QTP, function libraries are associated with tests through the Test Settings dialog. This is where you configure test properties including associated function libraries that contain reusable functions. Run Options and View Options serve different purposes.

To answer this question, the user needs to know what parameterization is.

Parameterization is the process of defining an algorithm or function in terms of one or more parameters. These parameters can be manipulated to achieve different results without modifying the algorithm or function itself.

Now, let's go through each option to determine which one(s) are involved in parameterization:

A. Data table: Data tables are often used in parameterization to provide input data for a test script. By using a data table, we can easily modify the test data without changing the script itself. Therefore, option A is correct.

B. Random Number: Random numbers can also be used in parameterization to provide different inputs to a test script each time it is run. By generating random numbers within a certain range, we can test the behavior of the script under different conditions. Therefore, option B is correct.

C. Environment: The environment in which the test script is run can also be a parameter. By changing the environment, we can test the behavior of the script under different conditions. Therefore, option C is correct.

D. All of the Above: This option is correct, as all of the above options are involved in parameterization.

Therefore, the answer is: D.

Regression testing benefits most from test capture and replay facilities because it involves repeatedly running the same tests after code changes. Captured test scenarios can be automatically replayed to verify that existing functionality remains intact, which is the core purpose of regression testing.