Putting performance test assets under source control

Use version control software, such as Rational ClearCase LT, to put performance test assets under source control.

If you use ClearCase LT—or any other type of version control software—put the following assets under source control to share them with the members of your team that use the same source control product. We recommend that you put the different project assets (schedules, tests, results, datapools, custom code) in separate folders under the main project.
Asset File extension Comments
projects .project This enables the project to be seen and imported by another user.
schedules .testsuite  
tests .testsuite  
custom code .java Put any custom code that you have written for a test under source control. Put this code under the project's src folder; for example, in src\custom.

This code must be versioned as a single logical unit with the test that includes it (meaning they should be versioned together if you change one or the other).

datapools .datapool  
locations .location  
results resultname_timestamp_computername.trc*xmi These assets, which are not visible in the Test Navigator, contain the data used to create reports and should be under source control. To see these assets, start the Navigator view, and perform the check out and check in operations from this view.

We recommend that you store the results a separate results folder, which you can specify when running a schedule or test.

We recommend the following:

For more information on ClearCase LT, see the topic "Rational ClearCase SCM Adapter" in the Help Table of Contents.

Parent topic: Product introduction

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