HP Quality Center Tutorial (Day 6) – Defect Management

Through the series of these tutorials, we have seen how to create releases, cycles, requirements, tests and test sets in ALM. We also saw how we can establish logical relationships among these entities to make the metric collection as well as traceability an inbuilt activity in our testing process.

You can check all these tutorials listed in our first QC tutorial here.

Also in the Test lab, we executed some tests. If the test passed, then all is well. If it fails, there is a reason for the same. Commonly, any deviation from the expected value is a defect.

Apart from that, defects can be:

  1. Variation in expected and actual results
  2. Documentation errors
  3. Un-testable requirements that you want to report and track
  4. Environment failures that prevent you from testing

QC has a wonderful mechanism that lets you create and track any kind of defects. In the following steps, we will see how defect management is supported through ALM.

How to add a defect to ALM

Step #1: Login to ALM to the right project and go to “Defects” tab by navigating from the sidebar. The lists of defects under the project are displayed in a list here.

Step #2: Click on “New Defect”.  Enter the required details. As you can see all the fields in red are mandatory to enter. (click on any image to enlarge)

add defect ALM

Step #3: Choose defect type

add defect ALM

Step #4: Choose severity

add defect ALM

Step #5: Enter other details and describe the defect in the “Description” box. You can provide attachments. The other tabs in this dialog are for additional details. Again, project specific.

add defect ALM

Step #6: This defect will now appear in the list. It has a unique ID to be identified with.

add defect ALM

Step #7: You can now change its status.

add defect ALM

Step #8: Assign it to another user:

add defect ALM

Step #9: Or if this defect is linked to any other defect or you can do so, by choosing “Linked Entities” from the left sidebar and choose the other defect that is causing or affecting this defect.

add defect ALM

How to link the defect to a test case:

Step #1: Go to Test lab tab and choose the test that failed and the defect is related to that failure.

link defect in ALM

Step #2: Click on “Linked Defects”. Here you can either add a new defect and link it by click on this icon:link defect in ALM If you do so, follow the steps that you did in the above section and the defect created will get linked.

Step #3: I am going to choose the icon:  link defect in ALM To link already created defect

link defect in ALM

Step #4: Enter the ID and Click “Link”. The defect gets linked.

link defect in ALM

Step #5: The linked defect can be seen in the test plan as well as requirements.

link defect in ALM

link defect in ALM

That finishes our end to end flow from Release to defects.

Tip: Please take a moment and try to see all the field values in the defect details. This will help you get excellent insights into how QC has a field for everything you can ever think of to add to the description to make it completely complete. I especially emphasize on the “Status” field. This will show how QC is not just a tool to place all your defects at one place but it actually is at the crux of the defect management process. All the states that you would find in a defect life cycle can be set through the “Status” field. I find that it’s most wonderful feature.

For more details on how to write a good defect report, refer this sample defect report.

Points to note:

1) We have worked with adding a new cycle under a release in the tutorial number 3 and it is mainly a testing related activity. Similarly, you can add a “New Milestone” signifying a certain step in your Project Management Activities.

2) Even though ALM is test management tool, the development and other support teams also have access to it. One of the reasons is to update the defect status.

3) The attachments for a defect are not mandatory but always provide a screenshot of the error in the attachment whenever applicable and possible.

4) The mandatory fields to be entered during the creation of a defect are defined by your Admin and may differ from project to project.

5) The other drop-down values are also defined by your admin.

Conclusion:

Now you are equipped with everything you needed to know how to use QC for all your test management activities.  All we need to know now is how to use its analysis features to make the test reporting and metric collection activities an integral part of your QA process.

We will learn the “Dashboard” sidebar option that facilitates the same in the next tutorial which happens to be our last.

Again you may want to visit and bookmark our first Quality Center Tutorial page where we have listed all the tutorial in this training series.

Please provide your feedback and let us know if there any topic that you need more information on.


Further Reading

43 thoughts on “HP Quality Center Tutorial (Day 6) – Defect Management”

  1. Thanks for sharing this useful article.
    One question, can we link defects from other tools like bugzilla to test cases in QC?

  2. Can you explain how to prepare a bug report and sent it to anybody? and how to integrate QC with QTP? Whats the use of dashboard? Thank you

  3. @Amit: Using the search feature in the defect grid you can always look up a certain defect but while adding a new defect ALM does not look for a similar defect

  4. @Ashwin: No. ALM provides an end to end test management solution but as far as I know you cannot integrate another bug tracking tool with it.

  5. @Revathy: All the reporting and dashboard features are exclusively dealt with in the next article. QC and QTP integration is how ever not a part of this series. but, may be soon.

  6. @nagajothi: ALM is a test management tool. You can use it for both manual and automation testing activities.

  7. Thanks a lot, Swati for providing an absolutely amazing guide on ALM. One thing that I would like to know is that do we have a unique ID for every defect?

  8. HI Vijay,

    Thanks for the tutorial. But one thing i would like to know is that, some people say we use Bugzilla for logging a defect and HP-QC for task management. why to use both when there is a option for defect management in QC.

  9. @Inder: ALM or QC is sufficient to support your entire defect management process. The reason why some people might be using bugzilla or anything else might be that, they have been using it previously and want to ensure continuity.

  10. Hi

    can you tell me where is “Defect details” code located so i can change according to my company needs.
    i checked customize > workflow > script editor.

    regards
    Shakeel

  11. Can you please let me know ideally how many defects we can link to a test case. And is it a good practice to link as many defects as possible to a test case.

    Thanks,
    Rahini

  12. I have one problem in hp qc
    i want to stop email notifications to only particular users ,please help me in this one if you have any script please help me ..

  13. My question is :
    I raised a defect in HP QC and send to the developer. where we found the defect after resolving the issue developer send to us .

    Please help me

  14. Hi,
    Thank You, for most valuable information. Here I have one question.
    how to integrate QC with QTP ..? and What the use of dashboard ..?

  15. Hello, I liked the series of these tutorials. I have learned a lot.
    Would you please provide an Excel and a word template that will facilitate an import into HP ALM? I have existing Requirement created in Excel and test cases in Word.

    Thank you for your assistance and time,

    Mbuyi

Leave a Comment