Structuring Your Test Assets

Silk Central tracks results of test executions in the context of versions and builds of one specific product. Therefore a Product needs to be defined before tests can be created. For automated tests, another requirement for test creation is a Source Control Profile. Automated tests in Silk Central actually represent test scripts that are located in source control systems, which are accessed via such source control profiles. Both product and source control profile information are specified on Test Container level, which therefore represents the top-hierarchy node of a test assets structure.

To get started, we'll simply create one container:

  1. In the menu, click Tests > Details View .
  2. In the Tests tree, select the root node to which you want to add the new container as a sub-node.
    Note: Containers cannot be nested, but you can add sub-folders to containers.
  3. Click New Test Container on the toolbar or right-click on the node and choose New Test Container.

    You can also right-click on the node and choose New Test Container.

    A new container root node is added to the Tests tree and the New Test Container dialog box displays.
  4. Type a Name and Description for the container.
    Note: Silk Central supports HTML formatting and cutting and pasting of HTML content for Description fields.
  5. Select any predefined Product that is to be associated with this test container from the list box. For details on adding a product profile, see Adding Products.
  6. Select a predefined source control profile from the Source Control profile list box. If you do not intend to check out any test sources for the test container, for example if you only have manual tests, select ---.
    Note: The Silk Central execution servers retrieve the program sources for the tests included in the container from the defined source control profile. Depending on the specified path in your source control profile, you can specify to use a sub-node in the Root node field of the test container.
  7. Optional: Check the Clear working folder before a test is executed check box.

    If checked, files that have been removed from the source control will also be removed from the working folder. Default is checked.

  8. Optional: Click Browse to select the root node within the selected source control profile. Test sources are within this root node. The root node is used on the execution servers to retrieve the sources of a test.
  9. Optional: When Silk Central is integrated with Silk Performer, you can define the Custom data directory and Custom include directory. In Silk Performer, the Include directory is divided into a System Include directory and a Custom Include directory. The Data directory is divided into a System Data directory and a Custom Data directory. For additional information, refer to the Silk Performer documentation.
  10. The Hidden Test Properties portion of the dialog box allows you to specify the test property types that are to be displayed on the test container’s Properties page, and the Properties pages of all test folders within the container. These settings do not affect the display of individual tests.
  11. Click Edit to adjust the hidden test property settings. The Hidden Test Properties dialog box displays.
  12. Uncheck the check boxes of all test types for which you want to have properties displayed.
  13. Click OK to save your settings and close the Hidden Test Properties dialog box.
  14. Click Save to save your settings.
Parent topic: Designing Tests - Quick Start Task
Next topic: Creating Tests