Software Testing: QTP and Quality Center

According to standard testing methodologies (like ISTQB), key test planning activities include scheduling test analysis, design, implementation, execution, and evaluation. Initiating corrective actions and monitoring progress fall under test monitoring and control.

Functional testing validates that the system functions according to requirements and can be conducted at any testing level from component through acceptance testing levels including unit, integration, system, and acceptance testing.

To solve this question, the user needs to know about the software development process and the roles of different team members involved in the process.

Debugging is a process of identifying and fixing errors or bugs in software code. It is an essential part of the software development process and is usually performed by developers who write the code.

Option A: Developers- This option is correct. Debugging is a task that developers usually perform. They are responsible for writing the code and testing it for errors. When an issue is identified, they need to debug the code to fix the problem.

Option B: Analysts- This option is incorrect. Analysts are responsible for understanding business requirements, creating functional specifications, and validating that the software meets the requirements. They are not directly involved in debugging activities.

Option C: Testers- This option is incorrect. Testers are responsible for verifying that the software meets the requirements and performs as expected. They are not responsible for identifying and fixing errors in the code.

Option D: Incident Managers- This option is incorrect. Incident managers are responsible for managing and resolving incidents that occur during the software development lifecycle. They are not responsible for identifying and fixing errors in the code.

The Answer is: A

Exit criteria are predefined conditions that must be met to declare a test level complete, such as coverage targets or defect rates. They apply to the entire test level rather than individual test completion.

To understand what determines the level of risk, the user needs to know what risk is and how it is measured. In general, risk is the likelihood that an event will occur and its potential impact.

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

A. The cost of dealing with an adverse event if it occurs: This option is partially correct but incomplete. The cost of dealing with an adverse event is a factor in determining the level of risk, as it is related to the impact of the event. However, it does not take into account the likelihood of the event occurring.

B. The probability that an adverse event will occur: This option is partially correct but incomplete. The probability of an adverse event occurring is a factor in determining the level of risk, as it is related to the likelihood of the event. However, it does not take into account the potential impact of the event.

C. The amount of testing planned before release of a system: This option is incorrect. While testing is an important aspect of risk management, the amount of testing planned does not determine the level of risk. Testing helps to identify and mitigate potential risks, but it does not impact the inherent risk level.

D. The likelihood of an adverse event and the impact of the event: This option is correct. The level of risk is determined by both the likelihood of an adverse event and the potential impact of the event. The likelihood and impact are often combined to create a risk rating or score, which is used to prioritize risk mitigation efforts.

Therefore, the correct answer is: D. The likelihood of an adverse event and the impact of the event.

The team's existing skills and experience with testing techniques are most critical because test approaches require deep understanding to apply effectively, regardless of tool availability or training budget. Without appropriate skills, even the best techniques fail.

In Quality Center's alert system, a red flag visually indicates that an alert is new and unread, while a gray flag shows that the alert has already been read. This color coding provides immediate visual feedback about alert status, helping users quickly identify which notifications require attention.

Quality Center's 'Follow up' flag feature allows users to set personal reminders on specific records, independent of automatic traceability notifications. These flags are user-specific, meaning only the person who set them can see them, enabling personalized task tracking without affecting other users' views.

A Favorite view in Quality Center is a saved configuration of a window's settings, including filters, column selections, sorting, and other display preferences. Users can create multiple favorite views for the same window and quickly switch between them, providing personalized workflows for different tasks or projects.

Quality Center features automatic email notification and alerts (traceability alerts) that trigger when associated requirements, tests, or defects change, keeping responsible stakeholders updated on modifications.

Quality Center supports using URLs as attachments, allowing users to directly link to specific QC records including defects, requirements, or test cases. This provides traceability and direct access to related items without creating duplicate attachments.

Follow-up flags in Quality Center are tied to individual user accounts, meaning they are personal and only visible to the user who created them. This privacy ensures that personal reminders don't clutter other users' views, allowing each team member to maintain their own task tracking system.

HP/ALM Quality Center projects store their data and entity information in a dedicated relational database (such as Oracle or MS SQL Server) alongside a repository for physical files. Flat files or root folders alone do not support the structured project information.

In Quality Center, user groups are used to manage access control and permissions. Each user belongs to a group, and that group's configuration determines what privileges the user has within a project - including which modules they can access, what operations they can perform, and what data they can view or modify.

The HP Unified Functional Testing Test Fusion report aggregates comprehensive execution results. It displays detailed information about test steps, failures encountered, the input test data utilized during the run, and the status of any defined checkpoints.

QTP (QuickTest Professional, now UFT) uses object properties stored in the Object Repository to identify test objects. Logical Name and Class are key properties used for object identification.

QTP uses VBScript as its scripting language, so test script files are saved with .vbs extension, which is the standard Visual Basic Script file extension.