Data Set Versions

Each time you add a data set to the test data mart, you create another version of the data set. A data set version refers to a specific version of a data set in the test data mart. For example, consider a situation where a test team runs tests on different features of an application. Before you use the data, store the data in the test data mart. You create the first version of the data set. To test different features, you add tables and columns to the test data. You can store the updated test data with the same data set name in the test data mart. You create the second version of the data set. You can add versions to the test data mart each time you want to save the test data.

To identify a data set version, add tags to a data set version. You can use tags to perform a keyword search for data set versions. When you create a version of a data set, the version inherits the tags of the previous version. You can edit inherited tags and add additional tags.

To prevent users from editing a data set version or resetting the data set version, you can lock the data set version. For example, if you do not want users to reset a specific data set version to a target, you can lock the data set.

You can create another version of a data set in the following ways:

Data set versions can have similar metadata or entirely different metadata. For example, you create a data set version DA_APP when you test version 1.0 of an application for a specific customer. You test specific features of the application in this release. You use source data that contains tables relevant to the tests you run. You might add tags to identify the customer. When you test the next version of the application for the customer, you test different features that require different test data. You create and run a different plan with a different data source. Because this is test data for a single application, you enter the same data set name to create another version of the data set. The version retains the tags that identify the customer.

For example, consider a data set version that contains test data that you require to run specific test cases. You can add the name of the test case, an identification number, or any relevant information as a tag to identify the data set version.

You can perform a keyword search for data set versions based on tags. When multiple test teams create data set versions, the teams can add tags to identify the data set versions. Share tag information to help users search for a data set version that you want to share.

You can also use tags to filter and search for data set versions in the Data Sets view.

You can add tags when you create a data set version. A data set version inherits the tags added to the previous version. You can edit or delete the inherited tags and add tags when you create a data set version. You can add multiple tags to a data set version. Use a comma to separate the tags.

You can add tags to an existing data set version from the Overview tab on the data set version page.

You cannot make changes to a locked data set version. The owner and the administrator can reset a locked data set version to a target, but cannot edit or delete the data set version when it is locked. You can reset a locked data set version if you need to check the data before you allow other users to edit or reset it. You can unlock the data set version when you want to allow edits to the data set version.

You can lock and unlock a data set version from the Actions menu on the Overview or Permissions tab on the data set version page.