If an implemented keyword is displayed as not implemented in the Keywords window, check in the Eclipse menu.
If you get this error, your keyword-driven test does not include a Start application keyword as the first keyword. Silk4J requires the Start application keyword to apply the application configuration of your project to the keyword-driven test. When you record a new keyword-driven test, Silk4J automatically adds the Start application keyword as the first keyword to the keyword-driven test.
With Silk4J 19.5 or later, parallel testing is enabled by default. When you upgrade from a Silk4J version prior to Silk4J 19.5 to a more recent Silk4J version, previously executing keyword-driven tests might no longer execute because each individual test is now expected to specify the application under test (AUT).
To workaround this issue, disable parallel testing on the machine on which Silk4J is running by setting the environment variable SILKTEST_ENABLE_PARALLEL_TESTING to false.
When replaying multiple keyword-driven tests from Silk Central with Silk4J 19.5 or later, parallel testing is enabled by default. When you upgrade from a Silk4J version prior to Silk4J 19.5 to a more recent Silk4J version, Silk4J will by default close the browser or the mobile app whenever a keyword-driven test is finished.
This issue does not occur when testing a browser application against Internet Explorer. To workaround this issue, disable parallel testing on the machine on which Silk4J is running by setting the environment variable SILKTEST_ENABLE_PARALLEL_TESTING to false.