< Previous | Next >

Lesson 3.1: Cover a new requirement with a test case

In the previous lesson, you logged in as the test manager and rejected the test plan because it did not meet its quality objectives. In this lesson, you log in as the test lead and create a new test case to cover the requirement. A test case describes a scenario of something that you are going to test.
To begin the coverage process:
  1. Log in as the test lead (Userid: carmen, Password: carmen) when prompted with the login dialog box. Carmen's dashboard opens.

    Notice that the work item that you created in the previous lesson is now listed in the test lead's My Tasks viewlet:

    My Tasks for the test lead

  2. To open the work item, from the My Tasks viewlet, click Ensure that all requirements are covered by test cases. Click the Overview tab to display the work item details:

    Work item for test manager to look at new requirement

    The work item informs Carmen to cover all requirements with test cases.

  3. Return to the Carmen's dashboard by clicking Back to Home at the upper, left corner of the page.
  4. To open the test plan, click Classics Java Test Plan in the Artifact column of the My Tasks viewlet.
  5. To create a test case to cover the new requirement:
    1. Click the Test Cases section.
    2. Click the Add New Test Case icon (Add new test case).
      Important: You can use the installed test case sample to decrease the time it takes you to complete this lesson. Click the Add Existing Test Cases icon (Add). In the View Builder window, deselect My test cases only, and click Run. From the list of test plans, select New Customer Order Test Case (Sample), and click OK. Skip to step h.
    3. In the Name field, type New Customer Order Test Case.
    4. In the Description field, type Test the ordering functionality of the Classics Java application.
    5. Type 20 as the weight.
    6. Choose the category (Web UI), function (Execution), and theme (Functionality) from the lists.
      Note: You can use the category, function, and theme attributes to organize your test cases into various groupings that can later be sorted. Your team can define these attributes any way that makes sense. You can use the weight as a means of tracking the relative difficulty or importance of the test case. A test case that requires twice as much time to execute might have double the weight as another test case, which will factor into reports that measure your progress.
    7. Click OK.
    8. Save the test plan.
    You now have a test case that addresses the new requirement:
    Test case section of the test plan
  6. The next step is to associate the new test case with the new requirement:
    1. Click New Customer Order Test Case to open the test case.
    2. Click the Requirements section.
    3. Click the Add Requirement(s) icon (Add requirement), select the requirement, New Customer Order Requirement, and click OK.
    4. Save the test plan.
    The test case, New Customer Order Test Case, is now associated with the requirement, New Customer Order Requirement.
  7. Now assign the test-script creation task to the tester:
    1. Click the Test Scripts section.
    2. In the upper, right corner of the Test Scripts section, click Create.
    3. In the Summary field, replace the default text with Test case is ready for manual test script.
    4. In the Owned By field, select Tony, Tester.
    5. Click the Calendar icon (Reserve) next to the Due field, and select a future date.
    6. Click OK.
  8. Click Save to save the changes to the test case.
In the next lesson, you continue as the test lead and plan the test environment.
< Previous | Next >

Feedback