HP Quality Center Fundamentals

Quality Center allows users to export grid view data to several formats including plain text files, Microsoft Excel spreadsheets, Microsoft Word documents, and HTML files. The other options omit one or more of these standard export choices supported by the platform.

Favorite views in Quality Center can be saved in either 'public' or 'private' folders. Public folder views are accessible to all users in the project, while private folder views are only visible to the user who created them. This distinction allows for both collaborative and personal view management.

Follow up flags in Quality Center are user-specific - they are tied to your individual login and are not visible to other users viewing the same record. This means each user can set their own follow up reminders independently without seeing or affecting other users' flags. The statement is false, making 'False' the correct answer.

The site administrator handles overall Quality Center management tasks, including server configuration, licensing, and broadcast messaging to alert connected users about maintenance. Other options represent misspelled terms or non-existent roles without site-wide broadcasting permissions.

In Quality Center, user access privileges within a project are determined by the 'user group' to which the user is assigned. User groups define what actions and features a user can access (permissions, roles, capabilities). Terms like 'QC group', 'user_Account group', and 'Account group' are not the correct terminology used in Quality Center.

Quality Center (now HP ALM) follows a sequential test management process. First you define releases and requirements, then plan test cases based on those requirements. After planning comes test execution, and finally defect tracking to log issues found during testing. Options A and C are incorrect because they list 'Run Tests' (redundant with Execute Tests) or 'Analyze Tests' (not a standard phase) instead of 'Track Defects'. Option D incorrectly places Track Defects after Analyze Tests and omits Execute Tests.

HP Quality Center allows customization via the Script Editor. The Script Editor provides access to VBA/VBScript events where administrators can write code to dynamically control field visibility, read-only status, and values in defect grids, whereas notepad or generic QC editors lack active scripting execution capabilities.

The Automatic Runner is Quality Center's feature for executing test sets concurrently across multiple remote host machines. Each test set requires its own Automatic Runner dialog instance to run in parallel. Options A and B are not correct Quality Center terminology, and Manual Runner (D) is for single-machine execution.

Quality Center allows you to delete any or all execution conditions attached to a test. The question asks for the maximum scope of deletion, which is 'All'. Options A, B, and C incorrectly limit deletion to specific numbers of conditions.

In Quality Center's Test Lab module, F9 is the designated shortcut key to access the Menu Bar. This is a standard UI shortcut specific to the Test Lab interface. Options A, B, and C are incorrect function keys for this particular menu.

The Quality Center sidebar contains a 'Defects' button that opens the Defects module for tracking and managing bugs. This is the primary entry point for defect-related activities. Options A, B, and D describe actions but are not the actual button name in the sidebar.

Quality Center is accessed through a web browser and can be deployed over either the public Internet or a corporate intranet, depending on organizational security requirements. Option D correctly captures both deployment models. Options A, B, and C are individually incomplete.

HP QC (Quality Center) is a comprehensive Test Management Suite that covers test planning, execution, defect tracking, and reporting. It is not merely a defect tracking tool (B), test design suite (A), or release management suite (D).

HP Quality Center was originally developed by Mercury Interactive and called Mercury Quality Center. After HP acquired Mercury Interactive in 2006, it was rebranded as HP Quality Center. Test Director was an earlier Mercury product.

In HP Quality Center, requirements can be mapped to test cases through two primary methods: the Requirements module (direct mapping) and the Test Plan module (coverage mapping). This bidirectional traceability is a core feature.

In HP Quality Center's permission model, both Project Admins and Site Admins have the authority to customize project settings. Quality Analysts typically have execution permissions without admin rights. The hierarchy places Site Admins above Project Admins.

HP Quality Center (HPQC) supports importing test cases and requirements from both Excel spreadsheets and Word documents. This feature allows migration of existing test artifacts into the HPQC system. Option B is false because HPQC provides these import capabilities as part of its standard functionality.

In HPQC, developer privileges typically do not include permission to delete defects - this is usually restricted to QA managers or administrators to maintain audit trails. Deletion would destroy defect history and metrics. Option A is false - developers can usually only create or modify defects, not delete them.

The 'Call to Test' option in HPQC enables test case reuse by allowing one test case to be invoked from within another test case. This promotes modularity and reduces duplication. Options A, C, and D are incorrect - 'Call' is generic, 'Template' is for structure, and 'Test Call' is not the correct terminology.

Test case names must be unique within a test management system to prevent confusion, ensure proper identification, and maintain referential integrity when defects or requirements link to specific test cases. Option B is false - duplicate names would create ambiguity and tracking problems.