This task provides the steps for developing and running tests.
This graphic
shows the steps for developing and running tests. Click this area to get information about completing plan items Click here to get information about elaborating plan items Click here to get information about detailing requirements Click here to get information about developing Click here to get information about building Click here to get information about developing tests Click here to get information about deploying builds to the test lab Click here to get information about running tests Click here to get information about submitting defects

This topic is similar to information that was previously found in Tool Mentors in the IBM Practice Library.

Before you begin

Before you begin this task, verify that the following activities have taken place:
  • The development team has planned the story. This means that they have created plan items for the project features being developed and linked those plan items to the release plan. Furthermore, development tasks have been created and assigned to implement the story.
  • Business analysts have written detailed requirements and those requirements are linked to development tasks and test cases.

1. Develop the test

At this point, you can add detail to the test case outlines that were created during the test planning phase.

  1. Open a test case and add test case details. Details can include a test case design, preconditions, post-conditions, expected results, test case weight, and other attributes.
  2. Write a manual test script that describes the steps to implement the test case. If necessary, you can attach images, text files, comments, and verification text to the test script. You can also create external test data for the test script to use.
  3. Optional: Create one or more test execution records that specify the execution environments for each test case. For example, you can create one test execution record to run the test case using one particular database, application server, and operating system and create another test execution record to run the test case in another environment.
  4. Link the test case to the story that describes the feature to be tested. Typically, the story is developed by someone in the development organization.

Supporting tasks:

2. Deploy the build to the test lab

After you develop the test, you can deploy the latest product build to the test lab and start testing.

  1. Create work item queries that list the stories that are ready to be tested and are included in the latest build. Add these queries as widgets to the dashboard so all team members understand the contents of the build.
  2. Deploy the build to the test lab. You can leverage the same automation tools that are used for smoke test automation.
  3. Run build and deployment verification tests to determine if the build is stable enough for testing. The build verification tests can also be automated.

Supporting tasks:

3. Run tests

After you deploy the latest build to the test lab, you can run tests against that build.

  1. Verify that the required features that need to be tested are implemented in the build.
  2. Search for and select all relevant test cases using one of the available search techniques.
    • Use the full text search capability to quickly locate a set of test cases.
    • Use the Filter Displayed Items text box in View Test Cases to perform a quick search for any test cases that meet your criteria.
    • Use categories and the column filtering feature to perform a more advanced search.

      To open a list of test cases, click Construction > View Test Cases.

  3. Run the tests.

    You can run each test case individually, run a test suite to establish a sequential flow of test cases for execution, or run test execution records. If the test cases are associated with manual tests, you can step through the manual test execution one step at a time. Test cases that are associated with automated tests will run automatically.

  4. Analyze the test execution results.

    Executing tests and reviewing the results might identify defects in the system under test. You can use these results to analyze what has been accomplished versus what has been planned. Furthermore, you can establish the results as baselines for validating functions for performing regression testing when future builds become available. All test case runs are displayed and after the runs are selected, the history of the particular run is provided.

  5. Provide feedback to the team.

    Use dashboards and reports to communicate the test results and provide feedback to the team. You can create custom reports that show the execution status and display the reports on the dashboard.

Supporting tasks:

4. Submit defects

After running the tests, you can create and submit defects. Be sure to link each defect with the relevant work item stories and requirements so the story and requirement owners know about the failures.

Supporting tasks:


By completing this task, you have run a series of tests against a deployed build and communicated the tests results and any associated defects to the broader team.

What to do next

After you test the build, the team should review all outstanding tasks and open defects for the development tasks.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki