Defect Management Life Cycle in HP ALM (Quality Center)

โšก Smart Summary

Defect Management Life Cycle in HP ALM enables testers to log, track, and report defects across a release. The Defects module records each defect from New to Closed, links defects to requirements, and supports Excel upload and email alerts.

  • ๐Ÿ”„ Defect Life Cycle: A defect moves through New, Open, Rejected, Fixed, Reopen, and Closed statuses, which teams can customise.
  • ๐Ÿ†• Create a Defect: Testers log defects from the Defects tab, set severity, attach files, and submit to generate a defect ID.
  • ๐Ÿ”— Link to Requirements: Linking defects to requirements enables coverage analysis graphs and the traceability matrix.
  • ๐Ÿ“Š Bulk Excel Upload: The Export to HP ALM add-in maps Excel columns to ALM fields for importing many defects at once.
  • ๐Ÿ” Search and Alerts: The Find dialog locates defects by field, and email notifications alert assigned users on status changes.

Defect Management Life Cycle in HP ALM

What is Defect Management in HP ALM?

  • A Defect is logged during the test execution, when the expected result and actual result do not match with each other.
  • The Defect module in HP ALM not only helps users to post the defects but also enables them to track and gives the overall quality of the release at any stage of the development process.

Defect Management Life Cycle in HP ALM

Default Defect Life Cycle in ALM:

Default Defect Life Cycle in ALM

StatusExplanation
NewWhen a defect is posted, the default status is ‘New’.
OpenWhen the defect is accepted by developers, it is moved to ‘Open’ status.
RejectedWhen the defect is rejected by developers, it is moved to ‘Rejected’ status.
FixedWhen the defect is fixed by developers, it is moved to ‘Fixed’ status. Testers would pick up all defects for Testing that are in status ‘Fixed’.
ReopenIf the testing has failed, the defect is moved to ‘Reopen’ status.
ClosedIf the testing has passed, the defect is moved to ‘Closed’ status.

Note: Users can also configure the defect life cycle by adding new defect statuses. Adding a new defect status would be dealt with in the project customization chapter.

How to Create a New Defect

Step 1) Navigate to the Defects tab in Quality Center and click on the “New Defect” button.

Create a New Defect

Step 2) The “New Defect” dialog opens up. Fill in the following mandatory information.

  • Enter the Detected By field.
  • Enter the Detected on Date โ€“ by default, the current date would be picked up.
  • Set the severity level of the defect.
  • The user can also enter other information and a brief description about the defect.

New Defect dialog

Step 3) The tester can also attach screenshots or other relevant files associated with the defect using the ‘Attachments’ tab.

  1. Click ‘Attachments’ tab.
  2. Click ‘Attachments’ button.
  3. Select a file from the File explorer dialog.
  4. Click ‘Open’.

Attach files to defect

Step 4) Upon clicking ‘Open’, we will be able to see that the file is attached under the attachment section.

  1. The selected file has been uploaded.
  2. Click ‘Submit’ to post a defect, after which it generates a defect ID.

Submit defect

Step 5) The defect is posted, and the same can be accessed in the Defects tab as shown below. You can also notice that the defect ID is generated upon posting the defect.

Defect posted with defect ID

How to Link Defect to a Requirement

Users can link a defect with other defects or link a defect with requirements. By linking defects and requirements, we can generate a coverage analysis graph and traceability matrix.

Step 1) After creating the defect, testers can map the linked requirements against it. To do the same:

  1. Click on ‘Defect ID’.
  2. The defect details dialog opens as shown below.

Defect details dialog

Step 2) To link entities:

  1. Navigate to ‘Linked Entities’.
  2. Click ‘Others’ for linking requirements against this defect.
  3. Click ‘Link’ button and choose ‘by Id’ (we can also select based on a requirement name).
  4. Enter the Requirement ID against which this defect has to be mapped.
  5. Click ‘Link’ button.

Link requirement to defect

Step 3) After clicking the link button, the defect details window is displayed back to the user with the added link as shown below.

Defect with added link

Step 4) Once the requirement is linked against a defect, the requirement displays with the link symbol against it as shown below.

Requirement with link symbol

Step 5) Once the requirement is linked against a defect, the requirement Traceability Matrix can be generated. To generate the Traceability Matrix, navigate to the view menu of ‘Requirements’ and select ‘Traceability matrix’. The generated Traceability Matrix would be generated as shown below.

Note: Please refer to the tutorial ‘Requirements Module‘ for generating a traceability matrix where the steps are elaborated in detail.

Traceability Matrix

How to Upload Defect using Excel

  • Every time, users would not be in a position to create each one of those defects manually.
  • This module helps users to upload the defects from Excel into ALM. This really helps when users want to migrate from one defect management system to ALM.
  • The process remains the same as that of uploading Tests and requirements.
  • One has to ensure that the Excel file is prepared in a format such that ALM allows importing of the data.

Step 1) Create the Excel file with the required columns that the user wishes to upload as shown below.

The field ‘attachments’ takes the local path where the screenshot or any other attachment is kept. Users have to just mention the path of the attachment so that it would be picked up for uploading into ALM along with the other details of the defect.

Excel file with defect columns

Step 2) Now:

  1. Navigate to the ‘Add-ins’ tab.
  2. Select ‘Export to HP ALM’.

Export to HP ALM add-in

Step 3) The ALM Export Wizard opens. Enter the HP ALM Server URL and click ‘Next’.

ALM Export Wizard server URL

Step 4) Enter the user name and password for authentication and click ‘Next’.

ALM Export authentication

Step 5) Select the Domain and Project Name into which we would like to upload the tests and click ‘Next’.

Select domain and project

Step 6) Select the type of data that we would like to upload. In this case, it is Defects.

Select data type Defects

Step 7) Enter the new map name. The first option, ‘Select a map’, is disabled because we have not created a map so far for uploading defects. Hence, we should create a new map name and click ‘Next’. We have not selected ‘Create a Temporary map’ as we would like to reuse it every time for uploading defects.

Enter new map name

Step 8) Upon clicking ‘Next’, the mapping dialog opens as shown below.

  1. The left pane grid items that are listed correspond to the fields that are available for upload in HP ALM. Please note that the fields marked in ‘RED’ should be mapped as they are mandatory fields.
  2. The right pane grid items refer to the fields that are mapped so that values in Excel will flow into those corresponding fields of ALM.

Mapping dialog

Step 9) Now let us understand how to map the fields in Excel against the fields in ALM.

  1. Select the field that the user would like to map and click on the arrow button as shown below.

Select field to map

  1. Enter the column name in Excel that corresponds to the appropriate column name in HP ALM.

Enter Excel column name

  1. Map all the required columns in Excel against the appropriate fields in HP ALM. After mapping all the required fields, click ‘Export’.

Map columns and export

Step 10) Upon successful upload, ALM displays the message as shown below.

Successful upload message

How to search a Defect

The Defect module contains all the defects that are logged, right from the very first defect that has been logged. Hence, a user would be in a position to search defects based on certain criteria.

Step 1) Navigate to the ‘Edit’ menu and choose ‘Find’.

Edit menu Find option

Step 2) The Find dialog would be displayed.

  1. Enter the field name based on which the search has to be performed (in this case we use Defect ID to search).
  2. Enter the value.
  3. Click ‘Find Next’.

Find dialog

Step 3) ALM displays the item in the background as shown below.

Search result highlighted

Email Notification of Defects

  • Assigned users will automatically receive an email if there is a change in the status or assigned-to fields, provided the email configurations are set appropriately by the ALM admin.
  • The email would be triggered based on the setting under the ‘Alerts’ tab of the project customization module (refer to Project Customization for details).

Let us say the assigned user ‘Glenn’ has to receive an email when the defect status moves to ‘Fixed’ status. The email would be sent as shown below. The screenshot is taken after receiving an email (from MS Outlook).

  1. The mail is sent to ‘Glenn’.
  2. The mail has the details about the defect.
  3. The mail is triggered because the status has moved from ‘Reopen’ to ‘Fixed’ as shown below.

Email Notification of Defects

Video on Defect Management

Click here if the video is not accessible

FAQs

AI helps by clustering duplicate defects, predicting defect-prone modules, and auto-classifying severity from the description. It can route new defects to the right team and forecast which areas need more testing, reducing manual triage in tools like HP ALM.

Yes. Machine learning models trained on past defects can flag likely bugs from logs and code changes, then rank them by predicted impact. A human tester should still confirm the priority before it drives release decisions.

An error is a mistake made by a developer in the code. That error can cause a defect, which is a mismatch between expected and actual behaviour found in testing. A bug is simply an informal name for a defect.

Severity measures how badly a defect affects the system’s functionality, while priority defines how soon it should be fixed. A defect can be high severity but low priority, or low severity but high priority, depending on business impact.

Summarize this post with: