< Previous | Next >

Lesson 4.4: Run a test and submit a defect

In the previous lessons of this module, you logged in as the tester and created a manual test script for the New Customer Order Test Case. In this lesson, you execute a test execution record and step through the manual test script.
  1. If you have not already done so, log in as the tester (Userid: tony, Password: tony).
  2. If you do not have the Classics Java™ Test Plan open, do the following:
    1. Point to the Planning icon (Planning), and click View Test Plans.
    2. In the View Builder window, deselect My test plans only, and click Run.
    3. From the list of test plans, click Classics Java Test Plan in the name column.
  3. From the Test Cases section, click the test case, New Customer Order Test Case, and then click the Test Execution Records section.
  4. Select the check box of the first test execution record, which tests the combination of Linux®, Tomcat, and Firefox 2.0.
  5. In the Test Script column, make sure New Customer Order Test Script is selected:
    Test script dialog
  6. Click the Run icon (Test Execution Record)

    The manual test script that you created in previous lessons opens in the execution page.

    Note: When you run a manual test script, you move to a statement and then switch to the application you are testing to perform the action in that statement. In this tutorial, the application is not available, so you can just practice stepping through the test script.
  7. In the Script Steps section of the execution window, click Apply (Apply verdict) for the first step to indicate that this step was performed successfully. The pointer moves to the next step.
  8. Step 2 is a verification point. Make sure Pass is selected in the field next to the toolbar, and then click Apply (Apply verdict) to indicate that the window opened. The step is marked with Pass.
    Note: If you added an image, the image displays next to the text, such as in step 2 in the below image.
  9. Click Apply (Apply verdict) for steps 3 through 5.
  10. Step 6 is a verification point. Make sure Pass is selected in the field next to the toolbar, and then click Apply (Apply verdict) to indicate that the dialog box opened.
  11. Click Apply (Apply verdict) for step 7.
    Note: If you included a comment, you can scroll over the Comment icon (Comment) to see the text, such as in step 7 in the below image.
  12. Step 8 includes the keyword that you added in Lesson 4.3. In the sample application, you would perform all of these steps, and then click Apply (Apply verdict) to pass them as a group.
  13. Step 9 is a reporting point. Because the previous steps were successful, click Apply (Apply verdict) to indicate that this step passed.
  14. Step 10 includes the test data variable that you added in Lesson 4.2. When you click Apply (Apply verdict), the test script will insert the first data record for the CardNumber variable in the Classics Java Test Data.
  15. Suppose step 10 fails because the credit card number format was not accepted. You can enter a defect directly in the manual test script:
    1. Click the Add Defects icon (Add defect). The blank defect form opens.
    2. Complete the form using the following information:
      1. Summary: Type Wrong credit card format.
      2. Severity: Select Blocker.
      3. Tags: Type credit, card, classics, java, ordering.
      4. Owned by: Select Amy.
      5. Priority: Select High.
      6. Due Date: Click the Calendar icon (Reserve), and select a date in the future.
      7. Description: Click edit, and add Entered 16–digit card number in credit card field. Format was not accepted.
      8. Click Save.
      Note: When you enter a defect against a statement, the Defect icon (Defect) is displayed to the right of that statement.
  16. Click Apply (Apply verdict) for steps 10 and 11.
  17. Click Apply (Apply verdict) for step 12.
    Note: If you included verification text, you can scroll over the Assisted Data Entry/Verification icon (Paste compare) to see the text, such as in step 12 in the below image.
  18. Click Apply (Apply verdict) for step 13.
  19. Step 14 is a reporting point. Because you could not complete step 10, the reporting point fails. Change the status to Fail, and click Apply (Apply verdict) to give the reporting point a failed status. The step is marked with Fail.
  20. Step 15 is another verification point. Click Apply (Apply verdict) to mark this step with Fail, since the order did not complete without the credit card number.
  21. Finally, click Apply (Apply verdict) for step 16.

    The first 16 steps of the test run look like the following image:

    Executing a manual test script

    Because you entered test data in step 10, the test script will run through all of the data records in the Classics_Java.csv file for the CardNumber field. You can see which iteration is being tested at the right of the page. When you click Apply, you will run through the previous steps four more times in addition to this first run because the data file has five records. You see the
    Tip: If you want to assign a Pass status to all of the steps, you can change the status to Pass, and then click the Apply All icon (Apply all verdict) to process these steps quickly.
  22. When you complete the steps, the test execution ends. Click Close and show results at the top of the page to view the results:
    Execution Result

    The image below shows the first 14 steps of the Results Details section; However, all steps are included in the Execution Result.

    Results Details
  23. Log out as tester.

You can view the results immediately or access them at a later time.

In the last lesson of the next module, you log in as the test manager and view these results.
< Previous | Next >

Feedback