Executing Silk4J/Silk4NET Keyword-Driven Tests Without Uploading a Library

If you have an existing test automation framework consisting of Silk4J or Silk4NET keyword-driven tests and you want to execute them from Silk Central, you can do this by using Silk Central's JUnit and test package functionality. To do so, follow the steps below:
  1. Create a source control profile that points to the artifacts of your Silk Test project (see Source Control Profiles).
  2. Create a test container that uses this source control profile (see Adding Test Containers).
  3. Create a JUnit test (see Creating Tests) and configure the following:
    • For keyword-driven tests that are implemented in Silk4J:
      • Specify the classpath. If you are using the default Silk Test build structure, specify .\output.
      • The .kdt files need to be in the folder that you specified as classpath, either packaged into a .jar file or within a folder in the classpath.
    • For keyword-driven tests that are implemented in Silk4NET:
      • Specify ./Keyword Driven Tests as classpath.

      • Create a parameter for the test container of your tests (see Creating Custom Parameters) called silktest.keyworddriven.dotnetassembly with a relative path to the .Net Assembly, for example \bin\Release\Silk4NETProject.dll.

      • The Silk Test folder called Keyword Driven Tests containing the .kdt files has to reside in the root folder of the source control.
  4. Assign the test to an execution plan (see Assigned Tests).
  5. Optional: Once executed, you can right-click the test and select Convert to Test Package to get a package structure (see Creating a Test Package).
Parent topic: Keyword-Driven Tests