Micro Focus Quality Center Tutorial (Day 4) – Creating and Managing Test Cases

This is the 4th Tutorial in our Micro Focus Quality Center Training series. You can check all the previously published tutorials on this page.  Note: As the tutorial length is a little long we have divided our initial 4 days training into 6 tutorials. This will help you to learn Micro Focus Quality Center step by step with every minute detail.

In this tutorial you will learn:

  • How to Create Test cases in Quality Center
  • How to link test cases to requirements
  • Creating test suites in Quality Center

=> Click Here For ALM Quality Center Tutorials Series

=> Click Here For Complete Test Plan Tutorial Series

Creating and Managing Test Cases

Creating Test Cases In Micro Focus ALM/Quality Center

We are working our way through ALM and have discussed Release, Cycle, and Requirements. In our previous session we created a Release, added Cycles to them, created Requirements, mapped them back to Cycles and Releases and finally, we saw how the statistics are affected based on these mappings.

In our article today, we will move on to further steps.

We will keep referring to the same Gmail.com example that we did in the previous articles. If you are not familiar with the same, please refer to the below article that came out before this one.

Requirements and Release Cycle Management using Quality Center

If the following are the test conditions that you came up with for each of our features in the May Release:

#1) Login – with correct credentials

  • Launch Gmail, Enter the correct username, enter the correct password and click login
  • Launch Gmail, Enter the correct username, enter the correct password, select “Stay signed in” and click log in

#2) Login – incorrect credentials

  • Launch Gmail, Enter the correct username, incorrect password and click Login
  • Launch Gmail, Enter the incorrect username, correct password and click Login
  • Launch Gmail, enter an incorrect username, incorrect password and click Login.

How do you write a manual test case for the same? Either you would use a word doc or an Excel sheet. I used an Excel sheet to write the 1(a) test case as an example.

Quality Center Test cases

Let us see how to create the same test case in ALM.

Test Plan Tab In ALM

Steps to create Test cases under the Test Plan tab:

Step #1: Login to ALM into the right project. Create the Release, Cycles, and Requirements as described in the previous tutorials.

Step #2: Go to the Test Plan tab by choosing the “Testing->Test Plan” from the sidebar.

Step #3: Choose “Subject” as your home folder and create a subfolder “ALM training” under it. I am going to create “May Release” and “June Release” Subfolders under it.

Test Plan tab in Quality Center

Step #4: Go to the May Release folder and choose the option to create a new test.

Test Plan tab in Quality Center

Step #5: Enter the name and then choose the “type”. Choose “Manual” for our tutorial.

Test Plan tab in Quality Center

Step #6: Enter the other details. The designer’s name will be auto-populated based on your login credentials.  Click OK. The test gets added.

Test Plan tab in Quality Center

Step #7: Now you can add your steps. Click on the “Design Steps” tab. Click on the “New Step” icon.

Test Plan tab in Quality Center

Step #8: Enter the step details. The description and Expected Results fields come up complete text editing features that are self-explanatory.

Test Plan tab in Quality Center

Step #9: I am going to create all the steps as shown above. This is how the completed test case looks like:

Test Plan tab in Quality Center

This completes the process of adding Test cases and steps to them.

Step #10: Under May release I am going to add some more test cases.

Test Plan tab in Quality Center

Linking Test Cases To Requirements

Steps to link Test cases and Requirements:

#1) Select a Test case created and click on it. All the properties get displayed in the right-hand side tab. Go to the “Req coverage” tab and click on “Select Req”

Linking Test Cases to Requirements

#2) The requirements tree gets displayed on the side. Expand the tree and select the needed requirements.

Linking Test Cases to Requirements

#3) Once done, close the requirement tree. You can link a test case to as many requirements as you would like. This is how the added requirement looks.

Linking Test Cases to Requirements

#4) Let us now check, how this mapping affects the requirement. Go to the Requirements tab from the sidebar. Double click on the requirement that you just mapped and notice the “Test Coverage” details.

Linking Test Cases to Requirements

You see how the test details and it’s the test’s status is displayed. Since this test was just created and never run, the coverage status shows as “No Run”. Let us now move on in our tutorial and learn how to run a test.

“Test Lab” Tab In ALM

Imagine we have just begun the May release testing phase. The first cycle is the Smoke test. We are not going to execute all the Test cases we have.

  • Briefly, a Smoke test is a high-level test performed by the QA team on an AUT as soon as the code is deployed to make sure the application did not break. So we are only going to execute test cases 1-a and 2-c.
  • Similarly for Sanity testing, which is checking the key functionality of the AUT. We will execute 1-a, 1-b, and 2-e
  • Functional Testing is everything.

Test lab tab will help us create test sets that contain the test cases that we need to execute in each phase. This is where the tester can execute the tests and record the test results. Let’s see how.

Steps to create test suites in Quality Center:

Step #1: Go to the Test lab tab by navigating from the sidebar. Create the folders as shown below:

Create test suites

Step #2: Under May release, choose the option to create a new test set

Create test suites

Step #3: Enter the test set name. Click OK.

Create test suites

Step #4: Once it is created. Click on “Select Tests” from the menu

Create test suites

Step #5: Select the tests as required

Create test suites

Step #6: Alternately if you choose the “Requirements Tree” tab, you can choose requirement and all the tests that are linked to it get added to your test set.

Create test suites

Step #7: Go ahead and create all the test sets. As you can see from the above screenshot I have created a test set each for each cycle.

Step #8: Tip: You can choose to add the same test multiple times in a test case. In that case, the second instance of the test will appear with a prefix [2].

Points To Note

#1) If you observe, we have created our releases, requirements, tests etc all under the parent folder “ALM training”. There is no rule that you should do that. You can choose a different name for your folder in each section. But as you have seen, it makes so much sense to use the same folder name.

For a real-time project that you are working on and trying to use ALM for, try to come up with a name that you would want to consistently use across as the first step in your test management process.

#2) The columns in the test plan tab or any other tabs can be customized by your project’s ALM admin.


This finishes how we create tests, add steps to the tests, link the tests to requirements, create test sets, adding tests to test sets, and finally backtracking our way to see how each activity affects the statistics each time.

In our next Quality Center tutorial, we will learn how to execute Test cases and check the execution status using this tool.

=> Visit Here For ALM Quality Center Tutorials Series

=> Visit Here For Complete Test Plan Tutorial Series

Please let us know how we are doing. We value your opinion and will take all feedback very seriously.

PREV Tutorial | NEXT Tutorial

Recommended Reading

51 thoughts on “Micro Focus Quality Center Tutorial (Day 4) – Creating and Managing Test Cases”

  1. thanks for the simple and easy to understnad tutorial. looking forward for more tutorials like this.keep up the good work.
    ps:- when is the next session for defects and test execution?

  2. The above article is very easy and useful for everyone.I have done a software testing course from MindScripts. It’s a good Institute for testing course. Faculty helps us to build the basic concept of testing with practical knowledge.

  3. In above example:
    If Smoke Test has been set by more than 1 test case (here if we choose Login with Correct credentials and Login with incorrect credentials) then while Running the Test Set of Smoke test how will Result window differentiate at display?

  4. @Sonakshi: I am not sure I understand your question. What do you mean by test results? There is no test result in the ALM, only the status. Whether you have one or multiple tests in your test set, each test case(and step) has their own status field and will display if the test passed/failed/stopped etc. I hope this helps. Article 5 in the series is about execution. Please refer that for additional information.

  5. Very good – I love your website. I love the articles and tutorials you publish, you target testing in a practical, real-world and hands-on way.
    Thank you Vijay.

  6. Hi i have a doubt in the below explaination:

    Linking Test Cases to Requirements:
    Steps to link test cases and requirements:
    in Steps 3 and 4 if i want to link more than 1 test case then how do i do it?
    In my work i have around 100 test cases for the same requirement.
    Please let me know.

  7. Hi Vijay….This is Sravani. The information you shared on QC is really helpful to me. Can i expect SOAPUI knowledge postings from your site. If yes, kindly help me out with the belongings.

  8. I have a question, by chance do we have any facility in qc to upload the test case status (pass, fail or hold) from excel

  9. I want to thank you for the explicit and straight forward lesson on this topic. Please can tell me how to convert excel test cases into QC. Once again thank you and keep up the good work for shearing your knowledge.

  10. I want to know How do I manage Test Cases in QC ?

    I have a Core Product which is then updated as per customer needs. we have some 4 different customers who need customization of the core product

    Our Test Cycle consist of Core release testing this product my company sells under her name and then we start testing the customer product which is given to the customer for its clients

    We design our test cases for the core product as most of new functionality is added to the core once that product is released we start working on developing the customer test cases but most of the test cases come from the core bucket .

    Our Problem , We can not get a proper tracebility of requirements and the test cases also we are just creating duplicate test case in QC

    Hope I was able to explain it in detail

    thanks in advance

  11. I am trying to upload the test cases in ALM via template created by me, the ALM gives message that test cases were uploaded successfully but in actual only one step of one test case gets uploaded, that too not from beginning the issues does not seem to going anywhere.. Could some one help who has used excel for test case uploading in ALM?

  12. This is a great guide. Thank you! Just as a suggestion, effects in the last sentence should be affects. Otherwise, great job!

  13. Can u please help…How to add new step in the existing steps of the test case in the test plan module. Will the order changes by itself.


  14. Dear Team, I am very hurry to know “How to import/export xml file which content test cases to HP ALM ” ?

    have xml file contain “test cases” want to upload in HPALM .. how ???

  15. How come when I create a test step there’s always a break line. What should I do to remove the break line. It looks like everytime I create a new description of the test steps it has space or break line by default.

  16. Hi,

    It is a great article; however, the example provided indicates a misundertanding of the concept of release versus test subjects in the test plan module. I recommend against using naming convention such as releases or cycles in the test plan rather building a feature base structure. This will also enable user to automate the test plan document creation using a well structured application feature base product. Let’s keep project management and release management in the release module. In a large scale environment, using releases, cycles, sprints in the test plan module lead to lack of test case maintainability and test redundancy.


  17. In the QC Test Plan, why does it change the order of the test cases I write? Is there a way to write test cases without them switching the order, and without numbering the test cases?



Leave a Comment