Committing test results for a test suite

When using the Execution page of the Test Manager view or Test Results view to examine the test results for an executed test suite, you can choose to commit the results. Committing test results creates a suite log record that is associated with the executed test suite record and a test log record associated with each executed configured test case. Using Rational ClearQuest queries, you can report on the suite log and test log information.
To commit test suite results:
  1. Use the Execution page of the Test Manager view or Tests Results view to access the test results. From the Execution page of Test Manager view or Test Results view, click the Uncommitted Results folder to locate the test result for the executed test suite record.
  2. From the Test Manager view or Tests Results view, select a test result and click Commit.
  3. When the test results are successfully committed a suite log and associated test log records are created and the test result entry in the Test Manager and Test Results view is removed. In the Test Manager view, an entry for the test log record is displayed in the Recently Committed Results folder.
If the test log file for any executed test script associated with a configured test case record is in a file location stored in a Rational ClearCase VOB, when the test results for a test suite are committed, the associated test log files are checked in.
Note: If you are using a UCM view, when you perform the Commit action, a test log file is added to the VOB. The activity associated with adding this file to the VOB is LogActivitydate.

In addition, if you are using the version 7.0 Enterprise schema or you have modified the schema to support a TMTestLog and defect reference, after you commit a test suite result you can submit a defect for any executed configured test case in the executed test suite.

For more information, see Setting the preference for saving logs stored in Rational ClearCase and About submitting a defect from a test result.


Feedback