How can I query my SilkBean AUT to acquire changed tags?
Sometimes after an AUT has been upgraded or changed some of the identifying tags may have changed. This can be quite an issue with SilkBean based applications. This is due to the tags being numeric iterations, thus making identification of the new tag quite difficult.
A good example of the issue may be if the MainWin tag of the application has changed, this would result in all subsequent tests failing.
The following function runs through a number of iterations. In this provided example 1..15, it retrieves the active window and attempts to generate the declarations for the JavaMainWin of index I (1..15).
This is useful if you have recently upgraded your JVM and have begun to experience "Window not found" errors. In most cases these can be related to a tag changing.
Once the attached function acquires the tag it is a simple case of updating your window declarations.
Note: A larger number of iterations may be needed, 15 is a good base start and should catch most changes however this may be increase simply by editing of the loop statement.