Component test runs

After you generate a test, supply it with data, and possibly customize the test, you want to know the test results. You get the results by running the test.

A component test run can include a test suite, a test case, or a combination of multiple test suites and test cases. You use run configurations to select the tests to run. You can also use run configurations to engage debugging or profiling on a test run.

A test runs with the data you supply in a test data table. If you include sets and ranges of data in the test data table, then running a single test can result in the running of several individual tests. You must take this into account when planning for the time required for executing the test.

For example, suppose you run a test for a method that has two arguments, arg1 and arg2, and that you have supplied five values for arg1 and six values for arg2. Running this test results in the running of 30 individual tests of that method.

Test data is partitioned into one or more data sets. Each data set of a test data table contains input values and expected output values. At run time, each data set is run separately which also increases the execution time.

On the first component test run, each test case runs all of its data sets. After this however, you can rerun any level of the test, even just a particular data set.

During the component test run, a temporary project is created in your workspace for internal purposes. By default, this project is deleted after the test run. You can change this behavior in the Component Test panes in the Preferences window.

After a component test run, you can see the results in the Run folder of the Test Navigator view. If the results do not meet your expectations, you can modify the component-under-test or the test itself and rerun it as many times as needed until you get the expected results.

Related tasks
Running component tests
Rerunning part of a component test
Running a component test with profiling engaged
Running a component test in debug mode
Stopping a component test

Terms of use | Feedback
(C) Copyright IBM Corporation 2000, 2005. All Rights Reserved.