test log

If you right-click on the performance test that you executed, you can display the test log for that run.

You can configure Test Log Editor Preferences to have defects sent to a standalone server setup and managed by you or your team.

If it finds one, it sets the Latest field to False on the old test log record and sets the new test log record to True.

Through ClearQuest, users can view the status of the scripts, as well as a test log that shows each script step and result.

For a given CTC and iteration, there should be only one test log that has a Latest flag set to True.

Using that method enables you to create and commit a test log record by importing a script log.

Rational Quality Manager can then compare this to baseline data stored as part of the test and highlight any discrepancies in the test log.

The first line indicates that this test log is for the test case named Tc1.

It includes the ability to read test logs created from the testing tool and to create test log results for the configured test case.

In Rational TestManager, delete all test plans, test log folders, and test suites that will not be required after migration.

Because this CTC is associated with more than one iteration, Jane needs to pick the correct iteration to associate with the test log.

Set preferences in the Test Log Editor to specify the name of the server configured in Step 1.

As an added benefit, it also measures GUI performance of AUT objects and reports any GUI delays in the test log.

To track the final verdict, the test log record has a field called Latest, with a value of either True or False.

In the test log, she can then navigate directly to the log file for the script and view any associated defects from the test log.

Important: This step allows the enablement of the Submit, Search, and Query buttons in the Test Log view.

Associated defects are conveniently displayed in the test log, and are directly linked to ClearQuest.

The resulting completion state reported to Rational Quality Manager is based on the overall verdict of the run's associated test log.

Attachments are added while running a test, and are carried forward into the test log.

The Test Log viewer is the best source for the details around a test.

Select an event (at the root or page level) within the test log.

You can choose to do nothing, issue a test log error or warning, or exit the test.

When you view the test log and you find that a test has failed, it is possible to submit defects at that stage.

Jane decides she does want to commit the test log with the failed verdict, and she also wants to log a defect.

You can use the Test Log viewer (Figure 5) to associate defects with a test log using the record number.

When the workbench is opened, you can access the full test reporting and test log capabilities.

The results are written in a test log file inside the WPAR.

This method provides a shortcut for writing a message to the test log.

Switch to the Performance Test perspective and open a test log.

Save logs if a load test fails: You can specify if you want to save the test log whenever a load test fails.

The test log record will be associated with the newly created defect.

The defect record numbers are then displayed in the test log.

After the new defect is saved, it also commits the test log record.

Code Listing 1 and Listing 2 both come from the test log for a single-user test.

You can also submit a ClearQuest defect while you are in the Test Log viewer.

Open an existing test log.

The measurement procedure shall be documented (test log book)

You can export test logs in XML format for further analysis. To export a test log in XML format

Changes the filter to add a check for the iteration that was assigned to the test log (TestLogs. Iteration)

Execute the test and examine the test log