Lesson 2.4: Test for defects

In this lesson, you monitor the status of a story to determine when it is ready for testing. After completing a test case, you submit a defect. You also associate a defect with a build result.

About this task

In this lesson, you learn how to complete these tasks:

  • Check testing status.
  • Explore a build and download a build result.
  • Explore a story to determine whether it is ready for testing.
  • Run a test case.
  • Submit a defect.
  • Complete a test.
  • Mark a defect as blocking.
  • Distribute the weight of a test case.
  • Associate a defect with a build result.

Checking testing status

About this task

Check the testing status of builds and work items from the Dashboard:

Procedure

  1. In the web client, in the upper-left corner, click the Home menu icon. From the list, under Quality Management, click JKE Banking (Quality Management).
  2. Log on by typing tanuj in Use ID and tanuj in Password.
  3. Click the Development tab.

    In the JKE Banking (Change Management) Builds Feed widget, see that there is a continuous build ready for testing. This widget is configured to filter builds, so that only builds with the ready_for_test tag are displayed. You can view the widget configuration in the widget settings.

    Builds ready for testing

    In the Stories ready for testing widget, see that the Allocate Dividends to Multiple Causes story is ready for testing.

Exploring a build

About this task

Explore a build:

Procedure

  1. On General page of the JKE Banking (Change Management) Dashboard, in the builds widget, click the brm.continuous completed build.
  2. On the Build result page, click the Work Items tab, and view the changes that Deb delivered that are in this build.
  3. Optional: Download and extract the file from the build result:
    1. Click the Downloads tab.
    2. Save the .zip file that contains the build result.
    3. Right-click the file, and extract it to a staging test environment folder.

Determining if the story is ready for testing

About this task

Explore the story to determine whether it is ready for testing:

Procedure

  1. In the Work items included in this build area, click the task that Deb delivered called Implement - Allocate Dividends To Multiple Causes.
  2. On the Overview page, in the Quick links area, click the link to the parent story, which is in the Implemented state.
  3. In the Allocate Dividends To Multiple Causes story, in the Quick links area, click the link to the Allocate Dividends to Multiple Causes test case.
    Test case

Running a test case

About this task

In this section, as you run the test case, you are prompted to perform operations against the JKE Banking application and view the application behavior to verify the expected results that are documented in the manual test. You can run the build of the JKE Banking application that Rebecca created, or you can complete the steps for the manual test.

Run a test case:

Procedure

  1. In the Allocate Dividends To Multiple Causes test case, click the green arrow in the toolbar; then click Run.
  2. In the window, leave New Test Case Execution Record.
  3. Set the test plan value to Development Test.
  4. Set Iteration to S2.
  5. Set Test Environment to Db2_Windows. Because test cases are reusable, a single test case can be executed against many different environments. Setting the test environment value in the run dialog ensures that the test execution result will be associated to this particular environment configuration.
  6. Multiple test scripts can be associated to a single test case. This is useful when different steps must be taken to complete a test case on different environments. Leave Allocate Dividends to Multiple Causes selected as the test script.
  7. The build record indicates which build of your application under test you are executing this test against. The build is associated to the test case execution at run time, so that results can be filtered and sorted by application build. If you complete the Build section, you can associate the build that Rebecca created. If not, you can leave it Unassigned.
  8. Your team might have many simple test cases that testers already know how to run and that do not require them to follow manual test steps. The execution variables enable you to override data and configuration values in test scripts. They can be assigned at the test script, test case, or test suite levels. Execution variables are out of the scope of this scenario, so leave this and any other value not already specified cleared.
  9. Click OK.
  10. Mark step 1 as passed by clicking the green check icon on the left toolbar. The execution arrow moves to the next step.
  11. If you are running the sample application, perform the action that is described in the Description column and observe the expected results of the first step.
  12. Continue performing actions and marking steps as passed until step 6, where you observe a defect.

Submitting a defect

About this task

Submit a defect:

Procedure

  1. In the Script Steps area, click the Create new defect button in the toolbar above the script (you might be required to log in).
    Create new defect
  2. In the Create New Defect window, in the Summary field, type Donation amount is allocated to EACH organization, not split between them.
  3. From the Filed Against list, select JKE\BRM.
  4. From the Severity list, select Blocker.
  5. From the Found In list, select Sprint 2 Development.
    Note: The test script steps are automatically included in the defect description field.
  6. Click OK.
    Note: The defect icon displays to the right of the current step in the test script.

Completing a test

About this task

Complete the test:

Procedure

  1. In the script steps, click the red Fail button on the toolbar to mark step 6 as failed.
  2. Continue running the test. Mark the remaining steps as Inconclusive.
  3. Close the JKE Banking application if you are running it.

Marking a defect as blocking

About this task

Mark the defect as blocking:

Procedure

  1. At the top of the test execution window, click Show Result.
  2. In the Execution Result, from the Actual Result list, select Blocked.
  3. In the table of contents, click Defects.
  4. In the Defects window, select the check box that is beside the new defect.
  5. Click the Change Defect Blocking Status icon to indicate that this defect is blocking the completion of this test.
    Blocking defect

Distributing the weight of a test case

About this task

Distribute the weight of this test case to reflect the severity of the problem:

Procedure

  1. In the Overview area, click Weight Distribution.
  2. In the Weight Distribution window, set these weights:
    1. Pass: 50 points
    2. Failed: 30 points
    3. Inconclusive: 10 points
    4. Blocked: 10 points
  3. Save the execution result.

Associating a defect with a build result

About this task

Associate the defect with a build result:

Procedure

  1. Click Project Dashboard > JKE Banking (Quality Management).
  2. On the Dashboard, click the Development tab.
  3. In the JKE Banking (Change Management) Builds Feed widget, click brm.continuous.
  4. In the build result, click the Work Items tab.
  5. Click Associate an existing work item.
  6. In the Select Change Request window, from the Type list, select Defect.
  7. In the Filter field, type Donation.
  8. Select Donation amount is allocated to EACH organization, not split between them, and click OK.
    Associate a defect in a build result

Lesson checkpoint

In this lesson, you learned how to complete these tasks:
  • Check testing status.
  • Explore a build and download a build result.
  • Explore a story to determine whether it is ready for testing.
  • Run a test case.
  • Submit a defect.
  • Complete a test.
  • Mark a defect as blocking.
  • Distribute the weight of a test case.
  • Associate a defect with a build result.