Creating a Baseline for a Project

CAUTION:
Creating a baseline for a project can lock the database for several minutes, depending on the size of the project that the baseline is created for. We recommend to create a baseline for a project during off-hours, when user activity on Silk Central is minimal.
Note: If the original project includes schedules, the scheduling options in the new baseline are set to none to prevent losing the last execution status. When you create a baseline, the History page of each Test item included in the baseline is updated with an entry for the baseline.

To create a baseline for a project:

  1. In the menu, click Projects > Project List . The Projects page displays, listing all existing projects and project baselines.
  2. In the Actions column of the project you want to create a baseline for, click Baseline Project. The Baseline Project dialog box displays.
  3. Type a name and a description for the new baseline.
  4. Optional: If the project contains tests that use shared steps or keywords from libraries, define the handling of the shared steps in the Library assets handling section:
    • Click Copy library assets to detach all references to shared steps and keywords in the original libraries, and instead reference assets in a newly created copy of these libraries in the baseline. Choose this option to create a project baseline for historical or auditing purposes. The library copies are read-only by default.
    • Click Keep references to library assets to keep all references to shared steps and keywords in the original libraries. Choose this option to create a working copy for ongoing testing purposes, for example a new version of the project.
    • To prevent users from editing the library, set the library as read-only. For additional information, see Managing Keyword Libraries and Library Properties.
  5. Optional: If the project contains manual or keyword-driven tests, define in the Test asset versioning section whether a new version should be created for the tests in the original project and/or in the baseline.
    • Check the Create new versions for manual and keyword-driven assets in original project check box to create new versions for all manual and keyword-driven tests with shared objects in the original project.
    • Check the Create new versions for manual and keyword-driven assets in new baseline check box to create new versions for all manual and keyword-driven tests with shared objects in the baseline. If you selected Copy library assets, new versions are also created for all assets in the copied libraries.
    Note: Versions are not created for data-driven instances.
  6. Click OK. The Baseline Project dialog box displays and informs you that the operation may take several minutes to complete.
  7. Click Yes to continue. The Baseline Project - Adapt Project Settings dialog box opens. The dialog box displays the requirement integration settings along with all source control profiles that are configured for the original project.
  8. Click the corresponding Edit button to link the project baseline to the appropriate baseline, branch, label, or other point of reference in the source control profile, or to change the requirement integration settings.
    Note: For more information on editing source control profiles, refer to the Silk Central Help.
  9. Click Finish to finish creating the baseline.
  10. Click Yes in the Baseline Project dialog box to activate the new baseline.
Parent topic: Project Baselines