Creating an eCATT Script Using the Standalone Silk Test Workbench

You can create an eCATT script in Silk Test Workbench, record or write additional VB.NET code and test, then transmit the test script to the SAP/R3 database for use in eCATT. In this case, Silk Test Workbench runs in a standalone environment (not started from eCATT), until the test script, project and related assets are passed to eCATT in a BLOB.

Start Silk Test Workbench.
Create and record the test script.
Note: You can also start with a test script created in eCATT that has been loaded from a BLOB into temporary storage in the Silk Test Workbench database.
Playback the test script.
View any results created for the test script playback.
Create any arguments needed for the test script in eCATT.
To transfer the test script, its project and related assets to eCATT, save it in a BLOB. Since Silk Test Workbench is running in standalone mode, the SAP/R3 Login dialog box appears.
Set the SAP/R3 database login parameters and connect to the SAP/R3 database for BLOB transfers.
Note: Silk Test Workbench requires a valid SAP/R3 login user name and password to connect to the SAP/R3 database. See Setting SAP/R3 Login Parameters for specific instructions.
An RFC connection must be established for the current session. Set the RFC connection parameters to transfer BLOB data to eCATT. Once the connections are made, eCATT can be used to work with the test script.