Troubleshooting for Keyword-Driven Testing

Why does the Keywords window falsely show a keyword as not implemented?

If an implemented keyword is displayed as not implemented in the Keywords window, check Project > Build Automatically in the Eclipse menu.

Why do I get the error "No application configuration present" when trying to replay a keyword-driven test?

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. To workaround this issue, record a new keyword-driven test against your application under test. Then open the keyword-driven test that throws the error during execution and add the recorded Start application keyword as the first keyword to the test.