Revision history

The TestArchitect repository saves pertinent information on a project item every time the item is checked in. This includes timestamp, assigned version, project name, item type (test modules, data sets, actions, etc.), item name, user who checked in the item, and included comments.

The repository stores the file history of all revisions of checked in files. For each checked in file, the repository keeps:

1. Checked-in date and time, called timestamp, in the format of mm/dd/yyyy hh:mm:ss.mmm

2. Assigned version: that is, the AUT version(s) assigned to a specific revision.

3. Project name

4. Project item type, of which the possible values are:\

   • User-defined action
   • Test module
   • Interface entity
   • $ Class Map
   • Data set
   • Variation

5. Project item name

6. User who checked in the file

7. Check-in comments

Revision rollback
The rollback feature restores the status of an older checked in revision of any project item to the current working revision.

Viewing history
You can select a checked in revision of any project item to view its history from the Revision History dialog box.

Comparing two revisions of a project item
How to view the differences between two historical revisions of a project item.

Filtering displayed revisions
When viewing revision histories of project items, filtering can be used to help narrow your search.

Renaming history
Renaming History stores all records of name changes made to specific project items.

Revision tag
In TestArchitect, an AUT version node is used to tag a specific revision, since a version commonly identifies a specific release of the AUT, such as version 1.2.

Related information

Revision control