Having problems with your account or logging in?
A lot of changes are happening in the community right now. Some may affect you. READ MORE HERE

How do I use the Version / Build functionality in SilkCentral Test Manager?

How do I use the Version / Build functionality in SilkCentral Test Manager?


How do I use the Version / Build functionality in SilkCentral Test Manager?



How do I use the Version / Build functionality in SilkCentral Test Manager?


Build information can be read from within SilkCentral Test Manager and from stipulated XML files held on the application sever.

From within Test Manager

  1. From within Test Manager the user would create a Product ( Administration -> Configuration -> Products ). From here you can create the different version/build numbers that you require.

    Products are assigned to projects at test container level

  2. When creating Execution definitions the Versions and Builds that you created for this Product in the Products section will be available to choose from.

Using the Build Information File

Build information files, which contain version and build information used for execution runs, are typically stored and searched for on the execution server that is executing a run. When a build information file is not found there, then the file is searched for on the application server. This behaviour is beneficial when you have several execution servers and need to use a single build information file across all execution servers, you only need to maintain a single build information file on the application server.

Similarly, when no execution server has been assigned to a test definition (and also for manual tests), build information files are searched for on the application server.

SilkCentral Test Manager is able to match up test results with build information and display test results for specific build numbers.

  1. Ensure that the build information file is stipulated in the Project -> Settings

  2. Create a Product as before ( Administration -> Configuration -> Products ) and ensure that you have the Product assigned to a Test container.

  3. When creating your Execution definition, check the "Read from Build Information File:"

  4. Your Build information file should be located on the application server or on the individual execution server as aforementioned. It should be in the following location

    C:\Documents and Settings\All Users\Application Data\Segue\SCC31\BuildInfos

  5. The format of the build info file is explained in the SilkCentral Test Manger Help or you can just use the BuildInfoExample.xml file (C:\Documents and Settings\All Users\Application Data\Segue\SCC31\BuildInfos) as an example. When the script is run it will read the XML file, looking for the assigned Product [below "Demo Product"). This product will have the version and build numbers contained

    Once the script has been executed, you can view the Version and Build numbers in the Activities -> Results.

Old KB# 24638


Some content on Community Tips & Information pages is not officially supported by Micro Focus. Please refer to our Terms of Use for more detail.
Top Contributors
Version history
Revision #:
1 of 1
Last update:
‎2013-02-15 19:47
Updated by:
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.