Publishing changes in datasets
After you create, edit, or encrypt datasets in IBM® DevOps Test Hub (Test Hub), you can publish all changes made to a dataset to a branch in the project. After you publish the dataset, other members in the project can use your dataset in their test run, if required. The Edit branch automatically disappears from the Branch list and changes made to the datasets are merged into the selected branch of the project repository.
You must have created, edited, or deleted dataset assets in Test Hub.
When you create or edit multiple datasets, the Changes page lists all datasets in the corresponding Edit branches. When you have many datasets listed on the Changes page, you can discard individual changes from the list by clicking Discard from Actions column, then publish or discard all changes made to datasets. If you do not modify any datasets, the Changes page displays a message that indicates there are no changes in any of the datasets.
The Changes page also provides you with information about the number of commits that the Edit branch is ahead and behind. You can click the (n) commits ahead option, and then click Reset to revert your changes. Similarly, you can also click the (n) commits behind option, and then click Merge to merge the changes of other member into the Edit branch.
You can publish the dataset to the remote Git repository either from the Changes page or from the dataset editor panel. When you modify the dataset and publish it to the Git repository, the other members who have access to that dataset can view the updated dataset.
You can click the Open action menu icon to perform the following actions from the Changes
page:
Options | Actions |
---|---|
Edit | Click Edit to make any updates to the dataset before publishing. |
Save As | Click Save As to save a copy of the dataset. |
Discard | Click Discard to remove the changes that you made to the dataset asset. |