Lesson 7: Configure operation behavior (QM)

In this lesson, you will learn how to configure preconditions for operations in a quality management project area. A precondition requires that a condition be true before members can complete an operation. You can use preconditions to enforce best practices in your organization.

1. Go to the administration interface of the Quality Management (QM) application at https://hostname.example.com:9443/qm/admin, where hostname.example.com is the fully qualified domain name of your Jazz Team Server.
2. Log in as Bert by typing bert for both the user ID and password.
3. For the Customization Tutorial project area, open the Preconditions and Follow-up Actions page:
   1. Click the Project Areas menu, and then click Browse Active Project Areas.
   2. Click the Customization Tutorial (Quality Management) project.
   3. In the list on the left, click Preconditions & Follow-up Actions.
4. Create a precondition that prevents test team members from running unapproved test cases:
   1. Click Configure, and then click Create New Configuration.
   2. Under Quality Management, select Execute Test Case, and then click Next.
   3. Select Test Team Member, and then click Next.
   4. Verify that Always is selected, and then click Finish.
   5. Above the list of preconditions, click Add.
   6. Select Disallow Execution until Test Case is Approved, and then click OK.
   7. In the Actions column, click the pencil icon to collapse the precondition configuration.
5. Add a precondition that prevents all users from advancing a test case to the Approved state until at least two test team members have approved the test case:
   1. Click Configure, and then click Copy Existing Configuration.
   2. Verify that Copy from within the same project area and Customization Tutorial (Quality Management) are selected, and then click Next.
   3. Select Save Test Case - Everyone (default) - Always, and then click Next.
   4. Select Test Team Member, and then click Finish.
   5. Above the list of preconditions, click Add.
   6. Select Required Approvals, and then click OK.
   7. In the Transition Rules section, click Add.
   8. From the Target State / Group list, under State Groups, select Approved.
   9. From the Required Approval Type list, verify that Approval is selected.
   10. In the Test Team Member field, type 2, and then click OK.
   11. In the Actions column, click the pencil icon to collapse the precondition configuration.
6. Remove the precondition that requires all users to provide an E-signature when they lock or unlock a test case:
   1. In the list of precondition configurations, find the Save Test Case - Everyone (default) precondition configuration. In the Action column, click the pencil icon.
   2. From the Preconditions list, select E-Signature Required for Lock/Unlock, and then click the Delete icon.
7. Save the project area.
   You are now ready to see your configured operation behavior in action.
8. Add Wilma as a member of the Customization Tutorial Project (Quality Management) project area:
   1. In the list on the left, click Overview, and then scroll to the Members section.
   2. Click Add. Type Wilma. In the Matching users list, double-click Wilma, and then click Next.
   3. In the Available Roles list, double-click Test Team Member, and then click Finish.
   4. Save the project area.
   5. When you are prompted to send an invitation to Wilma, click Cancel.
9. Log out, and then go to the QM application at https://hostname.example.com:9443/qm/web.
10. Log in as Wilma by typing wilma for both the user ID and password.
11. Click the Customization Tutorial Project (Quality Management) project area.
12. Create a test case by clicking Construction > Create Test Case. Name the test case TC1, and then save it.
13. Try to run the test case by clicking the Run icon () and then selecting Run. You cannot run the test case because it is not approved.
    
14. From the Action list, select Ready for review, and then save the test case.
15. From the Action list, select Approve, and then save the test case. You cannot set the test case as Approved because the test case is not approved by at least two test team members.
    
16. Define an approval:
    1. In the list to the left of the test case, click Formal Review.
    2. In the Formal Review section, click Approval, and then select a due date that is one week from today.
    3. In the Description field, enter Final Approval.
    4. Click Add approver.
    5. In the Select Users window, click Show All.
    6. From the Matching users list, select Bert and Wilma, and then click Add and Close.
    7. From the Action list, select Return to Under Review, and then save the test case.
17. Log on as Bert and approve the TC1 test case:
    1. From the User Profile menu (), click Log Out.
    2. Log on as Bert by typing bert for both the user ID and password.
    3. If the TC1 test case is not already open, open it.
    4. In the list to the left of the test case, click Formal Review. If this test case was a completed test case, you could review the contents by clicking each section in the list on the left.
    5. Click the Pending down arrow for Bert, and then select Approved.
    6. Save the test case.
18. Log on as Wilma and approve the TC1 test case:
    1. From the User Profile menu (), click Log Out.
    2. Log on as Wilma by typing wilma for both the user ID and password.
    3. If the TC1 test case is not already open, open it.
    4. In the list to the left of the test case, click Formal Review. If this test case was a completed test case, you could review the contents by clicking each section in the list on the left.
    5. Click the Pending down arrow for Wilma, and then select Approved.
    6. Save the test case.
    7. Lock the test case by clicking the Set to locked icon (). You are not prompted for an E-signature because it is not required.
       The next step is to approve the test case, but the Action list is not visible to the right of State because the test case is locked.
    8. Unlock the test case by clicking the Set to unlocked icon (). You are not prompted for an E-signature because it is not required.
    9. From the Action list, select Approve, and then save the test case. The test case is saved and its state is changed to Approved.
19. Run the test case:
    1. Click the Run icon ().
    2. In the Run Test Case window, select Create Result without Execution, and then click OK. Now that the preconditions for running a test case are met, the test case runs successfully.