QTP and Quality Center Testing

HP Quality Center (now Application Lifecycle Management) is based on the Test Documentation Lifecycle (TDLC). This framework organizes testing activities around documenting test plans, requirements, execution, and defects throughout the testing process.

The correct QC testing process begins with specifying the release (defining scope), then specifying requirements (detailing what to test), preparing the test plan (designing tests), executing tests, and finally managing defects. Options A and B have incorrect ordering.

A requirement defines what needs to be tested in an application. Requirements specify the functionality, features, and behaviors that must be verified during testing. They form the basis for creating test cases and determining test scope.

The Execution Grid Tab is the standard interface in test management tools for declaring test sets, executing test runs, and reviewing execution results. This tab provides the comprehensive grid view needed for managing test lifecycles. The Link defect Tab is for linking defects, Live analysis is for real-time analytics, and Execution flow is for workflow visualization.

The standard defect life cycle follows: New→Open→Fixed→Rejected→Closed. A defect starts as New, moves to Open when assigned, to Fixed when resolved, to Rejected if the fix is rejected, and finally to Closed. Option A is incorrect because Fixed comes before Open. Option C is missing the Open state. Option D is missing the Rejected state.

QTP (QuickTest Professional, now UFT) does have two views: Keyword View and Expert View. The statement is true.

QTP (QuickTest Professional) has two types of object repositories: Local Object Repository (specific to a single action/test) and Shared Object Repository (reusable across multiple tests). These are the two primary repository types in QTP.

QTP provides direct integration with Quality Center (now Application Lifecycle Management/ALM), allowing testers to connect, store tests, and manage resources from within the QTP interface.

LoadRunner consists of several key components: Virtual User Generator (for creating scripts), Controller (for running scenarios), and Analysis (for examining results). 'Monitor Over Firewall' is not a standard LoadRunner component. LoadRunner does have monitoring capabilities, but not under this specific name.