Why do I encounter the error message "SilkTest reported, Log Error: *** Error: Window "window name" was not found" during replay?
On occasions during replay of a GUI-Level BDF script you may encounter an error message similar to the following:
StExecuteTestcase GUI-Level Testing Replay: 11 - SilkTest reported, Log Error: Window "[BrowserChild]Place Order" was not found
There are typically two possible explanations as to why this type of error has occurred.
If this type of error occurs during a Try-Script Execution then this is an indication that the uploaded SilkTest test case is not accurate and may require modification in SilkTest in order for the testcase to execute successfully. This is because when you complete a Try-script the virtual user runs as a SilkTest Console Session as opposed to an actual Terminal Service Session.
See the following resolution for further details on the difference between a Console and Terminal Session: When replaying a GUI Level BDF script what is the difference between running as a console session and a terminal server session?
Load Test Error:
If this type of error occurs during a Load Test then this is an indication that the root cause of the error is related to the Terminal Service Session in which the SilkTest script is being executed. For example consider the user environment in which you initially configured the SilkTest Project; you will have logged onto a machine, recorded a testcase and then successfully executed the testcase before uploading the project to SilkPerformer.
Once the project has been uploaded you will then have had to provide a set of user credentials as the input parameters for the BDL function "StInitSession()" so that you can connect and execute a Terminal Session within SilkPerformer. However problems may arise if you have used a different set of user credentials to connect to the Terminal Session in SilkPerformer in comparison to the user credentials you used to logon to the machine in which you initially recorded the SilkTest testcase. This can have an affect that unexpected windows or dialog boxes may be displayed during the GUI execution in the Terminal Session.
Therefore to prevent the above error message occurring during a loadtest; you should use the user credentials that you have specified in the BDF script to connect to the Terminal Server via a Remote Desktop Connection. Once connected you should then access the application and complete the actions performed in the testcase manually in order to ensure that all temporary or sporadic dialog boxes have been disabled.