Troubleshooting for Keyword-Driven Testing

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

If you get this error, your keyword-driven test does not include a Start application keyword as the first keyword. Silk Test Classic 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, Silk Test Classic automatically adds the Start application keyword as the first keyword to the keyword-driven test.

With Silk Test Classic 19.5 or later, parallel testing is enabled by default. When you upgrade from a Silk Test Classic version prior to Silk Test Classic 19.5 to a more recent Silk Test Classic 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 Silk Test Classic is running by setting the environment variable SILKTEST_ENABLE_PARALLEL_TESTING to false.

How can I prevent my browser or mobile app from closing between tests?

When replaying multiple keyword-driven tests from Silk Central with Silk Test Classic 19.5 or later, parallel testing is enabled by default. When you upgrade from a Silk Test Classic version prior to Silk Test Classic 19.5 to a more recent Silk Test Classic version, Silk Test Classic 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 Silk Test Classic is running by setting the environment variable SILKTEST_ENABLE_PARALLEL_TESTING to false.