Test execution

There are several way to run tests. Choose the methods and options that best suit your test team.

Run test cases

The simplest way to run a test is to run a test case. The test case can be associated with other test artifacts such as test plans, test scripts, test environments, test case execution records, and test suites.

When you run a test case, you can associate the test run with the context in which the test is run by assigning values for the test plan, iteration, and test environment. Although these associations are optional, many of the quality management reports are based on these values (which are stored in a test case execution record that is associated with the test case). If you have not generated test case execution records prior to running tests, and you fail to assign these values in the Run Test Case dialog box while running a test case, the test run will not be reflected in your reports.

A test case often runs in the local environment, and when the test run is finished, you can update the test case result if necessary. If your test execution needs are relatively basic and you do not need to support multiple test environments, you can get up and running quickly by running test cases directly rather than creating and then running associated test case execution records.

Run test suites

A test suite is a collection of test cases that are grouped for test execution purposes. Test suites can include test cases with both manual and automated test scripts, as well as test cases without associated test scripts, but test suites are most beneficial when you have a series of automated tests that you can run without supervision. When running a suite, you can specify whether to run the test cases in the suite sequentially or in parallel. With sequential suite execution, you can choose to stop the execution of the suite if a single test case does not pass. This is useful if running a test case in a test suite depends on the success of the previous test case.

Run test case execution records and test suite execution records

Test case execution records and test suite execution records map the execution context to the test case or test suite. They specify the test plan, iteration, and test environment for execution, defining a test this way: Run this test case in this particular software and hardware environment and associate the test run with a specific test plan and test iteration. To ensure that your test case or test suite is run in four different test environments, you can create a test case execution record or test suite execution record for each test environment.

Test case execution records and test suite execution records reflect the most recent test case result or test suite result (pass, fail, blocked) that is associated with the test case execution record or test suite execution record.

You can create test case execution records and test suite execution records individually or use a wizard from within the test case or test suite to generate several at once automatically.

Create test results without execution

In some cases, you may want to record the result of a test without actually completing the execution. You can create test results without execution from test case and test suite execution records, test cases, and test suites. If you have a test suite that contains test cases with associated default scripts, you can record a test result for each test case without running the entire test suite.

Modify variables before execution

If you use execution variables in your test scripts, you can modify the values of those variables for a specific test run.

Run manual and automated test types

You can create and run both manual and automated tests, including these tests:

  • Manual tests that are created with Engineering Test Management
  • Keyword-enabled tests that are created with Engineering Test Management
  • Automated tests that are created with other test tools

When you create automated tests, you create references to the actual artifact that were recorded or created with an automated test tool. The automated tests can reside on a test machine in your test lab or at a shared network location. When you run a test at a shared network location, the test is copied to a test machine and then run.

Schedule test artifacts to run

Test artifacts, such as test cases, test suites, test case execution records, and test suite execution records can be scheduled to run at specific times using specific test environments.

Defect tracking

You can associate a defect during a test run by clicking the Create New Defect (Create new defect) icon or Link to Existing Defect (Link to existing defect) icon. These icons are located in the Change Requests section of a test case result and at the top of the Script Steps section while running a test script.

video icon Video

Jazz.net channel
Software Education channel

learn icon Courses

IoT Academy
Skills Gateway

ask icon Community

Jazz.net
Jazz.net forums
Jazz.net library

support icon Support

IBM Support Community
Deployment wiki