Putting test assets under source control
Use version-control software, such as Rational® ClearCase® or Rational Team Concert™, to put test assets under source control.
If you use version-control software, such as Rational ClearCase or Rational Team Concert, put the following assets under source control to share
them with the members of your team that use the same source-control
product. Put the different project assets in separate folders under
the main project.
Follow these guidelines:
Asset | File name 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 src folder for the project; for example, in src\custom. This code must be versioned as a single logical unit with the test that includes it (that is, the code and the test should be versioned together). |
Datapools | .datapool | |
Locations | .location | |
Results | .trc*xmi | Results 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. Store the results in a separate results folder, which you can specify when running a schedule or test. |
- Turn off the Eclipse prompt that is displayed every time you create a file, asking if you want to add it to source control. To do so, click Do Nothing. preferences page and select
- During a session, keep schedules and tests checked out for easy editing. When you exit Eclipse, you are prompted to check them back in.
- Put test logs (files with the .execution file name extension) under source control, in the results folder.
- Do not put the class path file under source control.