Silk Test Classic

Ensure that the agent.exe and partner.exe processes have been killed before attempting a Silk Test Monitor execution

When running Silk Test monitors or GUI-level tests, Agent.exe or Partner.exe may not close correctly after a monitor execution and the temporary results folder may remain opened. When this happens during a monitor execution, all subsequent monitors fail with the error LoadtestController: 3302 - The results directory could not be cleared and do not clear.

Kill the Agent.exe or Partner.exe process manually on the execution server or create an Action Essential which will automatically kill the processes whenever needed.

Unknown behavior occurs if a window class is declared without a tag

A window class declaration in Silk Test must include a tag, even if the objects in the class are intended to be used only with the Open Agent. Locators can be added to objects of a class. Adding a locator to a class definition will not have an effect. For example, in the following code, the tag line is mandatory.

[-] winclass MyDialogBox : DialogBox
 [ ] tag "[DialogBox]"

If the tag line is present, the code works as it should. However, if the tag line is missing, this leads to unknown errors and possible crashes.

Variables are not displayed correctly in debug mode when "{chr(10)}" is used

When debugging a script that uses the "{chr(10)}" character for line-change, the values of the accessible variables are not displayed correctly and you cannot use Set Value to set the value of a variable.

The INC file for the base state does not compile if the caption of an application contains a single quote

The generated INC file for the base state does not compile if the caption of an application contains a single quote.