Recording a Keyword in Silk Test Workbench

You can only record actions for a keyword that already exists in a keyword-driven test, not for a keyword that is completely new. To record a new keyword-driven test, see Recording a Keyword-Driven Test.
To record the actions for a new keyword:
  1. Open a keyword-driven test that includes the keyword that you want to record.
  2. In the Keyword-Driven Test Editor, click Implement Keyword to the left of the keyword that you want to implement. The Implement Keyword dialog box opens.
  3. Select which type of asset the new keyword should be:
    • To implement the keyword as a .NET method, click .NET Script. You can add the new keyword to an existing .NET script or create a new .NET script for the keyword by typing a name into the Asset Name field.
    • To implement the keyword as a keyword sequence, click Keyword. You cannot record a mid-level keyword, as it is a sequence of other keywords.
    • To implement the keyword as a visual test, click Visual Test.
  4. Check the Start Recording check box.
  5. Click OK.
  6. If you have set an application configuration for the current project and you are testing a web application, the Select Browser dialog box opens:
    1. Select the browser.
    2. Optional: If you want to test a web application on a desktop browser with a predefined browser size, select the browser size from the Browser size list.
      For example, to test a web application on Apple Safari and in a browser window which is as big as the screen of the Apple iPhone 7, select Apple iPhone 7 from the list.
    3. Optional: Select an Orientation for the browser window.
    4. Optional: Click Edit Browser Sizes to specify a new browser size and to select which browser sizes should be shown in the Browser size list.
  7. In the application under test, perform the actions that you want to test.
    For information about the actions available during recording, see Actions Available During Recording.
  8. Click Stop. The Record Complete dialog box opens.

The recorded actions are displayed in the defined visual test or .NET script.