Silk Test Classic Tests

Silk Central’s Silk Test Classic interface offers a reliable means of automating Silk Test Classic users. Each test case of a Silk Test Classic script executes within its own test execution and produces its own results.

The Silk Test Classic Plan test type is used for Silk Test Classic test plans. A test plan usually is a hierarchically-structured document that describes the test requirements and contains the statements, 4Test scripts, and test cases that implement the test requirements.

When you observe running Silk Test Classic executions on the Activities page, the currently running execution plan offers a hyperlink that opens a Details View. This view allows you to closely monitor the state of the currently running execution plan. For Silk Test Classic test executions, the center component of this view consists of two parts: The upper part shows general information about the test, script, test case, and test data. The lower part shows all output messages generated by Silk Test Classic, along with their severity.

In previous versions of Silk Central, Silk Test Classic invocation was implemented through a command-line interface. The new interface works using interprocess communication. You can specify whether or not Silk Central’s Silk Test Classic interface should be used by configuring test-container settings.

For all Silk Test Classic test parameters that are not defined through Silk Test Classic test properties in the Silk Central GUI, the Silk Test Classic default settings are used, for example from partner.ini.