< 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 run 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, point to Planning (Planning), and click View Test Plans. From the list of test plans, click Classics Java Test Plan in the name column.
  3. From the Test Cases section, click the New Customer Order Test Case test case, and then click the Test Execution Records section.
  4. Select the check box for the combination of Linux®, Firefox, and Tomcat.
  5. In the Test Script column, select New Customer Order Test Script:
    Test script dialog
  6. Click the Run icon (Run)

    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 the Pass icon (Apply pass) for the first step to indicate that the Classics CD window opened correctly. The step is marked with the Pass icon (Apply pass) and the pointer moves to the next step.
  8. For steps 2 through 5, continue to click the Pass icon (Apply pass) for each step to indicate that all steps are performed as expected.
    Note: If you included a comment, you can scroll over the Comment icon (Comment) to see the text, such as in step 5 in the following image.
  9. Step 6 includes the keyword that you added in Lesson 4.3. You perform each step in the keyword. Click the Pass icon (Apply pass) to pass the first two steps in the keyword.
  10. Notice that the third step in the keyword, Click OK, is a reporting step. Because the previous steps were successful, you can confirm that the order was placed correctly. Click Pass (Apply pass) to indicate that this step passed.
  11. Step 7 includes the test data variable that you added in Lesson 4.2. The test script inserts the first data record for the CardNumber variable in the Classics Java Test Data. Suppose step 7 fails because the user entered the correct credit card number format, but the application did not accept it. You can enter a defect directly in the manual test script:
    1. Click the Add Defects icon (Add new defect). The defect form opens. Some of the fields are already populated with information from the test case.
      Note: To check for potential duplicate defects, click the Find Potential Duplicates (Find duplicate defects) icon.
    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.
  12. In the Actual Results field for step 7, type Received error message, Wrong credit card format, when correct format was entered. Then, click the Fail icon (Apply fail).
  13. Click the Pass icon (Apply pass) for steps 8 and 9.
    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 9 in the following image.
  14. Step 10 is a reporting step. Because you could not complete step 7, the reporting step fails. Click the Fail (Apply fail) icon to give the reporting step a failed status.
  15. Finally, click the Pass icon (Apply pass) for step 11.

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

    Executing a manual test script

    Because you entered test data in step 7, 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. You will run through the previous steps four times in addition to this first run because the data file has five records.
    Tip: If you want to assign the same verdict to the remainder of the steps, click the Apply All icon (Apply all verdict) to process these steps quickly. Select the verdict in the Apply all confirmation window, and click OK.
  16. 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
    Defects and Notes sections

    The following image shows the first 10 steps of the Results Details section; however, all steps are included in the Execution Result.

    Results Details
  17. Log out as tester.

You can view the results immediately or access them later.

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

Feedback