SilkTest® 2008 R2 Release Notes

This file contains important information that may not appear in SilkTest Online Help. Read this file in its entirety.

For information about installation, deployment, and licensing issues (including the evaluation version of SilkTest), see the SilkTest Installation Guide.

For an overview of the new features, see the What's New section below.

Contents
What's New Resolved Defects Installation Instructions
System Requirements Known Issues Getting Help

What's New

This section lists significant enhancements and changes that were made for SilkTest 2008 R2.

Warning: If you upgrade your licenses to use SilkTest 2008 R2, the new license file(s) will not contain license keys for using any SilkTest International release. The license file(s) will not contain license keys to use the .NET, AOL and BlueExpress add-ons in conjunction with any version of SilkTest which precedes SilkTest 2008, and which supports these add-ons. Please consider this before you upgrade your licenses.

Dynamic Object Recognition

With this release, a new way to execute testcases has been added. Create tests that use dynamic object recognition instead of relying on hierarchical window declarations in an include file. Scripts that use dynamic object recognition are robust and easy to maintain. Dynamic object recognition enables you to create testcases that use XPath queries to find and identify objects. Dynamic object recognition uses a Find or FindAll method to identify an object in a testcase. For example, the following code finds the first MenuItem with the caption 'Exit' in an arbitrary position in the application that you are testing.

MenuItem m = (MenuItem) Desktop.find("//MenuItem [@caption='Exit']")

To create tests that use dynamic object recognition, you must use the Open Agent. The SilkTest Open Agent supports:

Record Window Identifiers Dialog Includes Dynamic Object Recognition Information

You can identify control names and attributes to include in tests that use dynamic object recognition using the Record Window Identifiers dialog. The Record Window Identifiers dialog displays the XPath query string for the object on which the mouse rests. You can capture and edit locator strings in this dialog and copy them into a test.

Windows Presentation Foundation (WPF) Support for the SilkTest Open Agent

SilkTest provides support for testing Windows Presentation Foundation (WPF) applications using the Open Agent. SilkTest supports standalone WPF applications and can play back controls embedded in Framework version 3.5.

SilkTest provides several sample applications for WPF. The sample applications are installed by default and are located at Start/Programs/Borland/SilkTest 2008 R2/Sample Applications/Microsoft .NET/.

xBrowser Support

SilkTest provides support for testing web applications using the Open Agent. At this time, you can use the xBrowser extension to test applications that use Internet Explorer or embedded browser controls. For example, xBrowser support enables you to test an application that runs in Internet Explorer or a browser that is embedded within a Java SWT application.

SilkTest contains a sample Java SWT test application that contains an embedded browser. Sample applications are located at Start/Programs/Borland/SilkTest 2008 R2/Sample Applications/Java SWT/SWT Test Application /. Select the sample application version that is right for your environment. Choose Control/Standard Ctrl Sample and then click the Browser tab.

JavaScript Support

SilkTest provides support for applications that include JavaScript. While JavaScript support already exists for tests that use the SilkTest Classic Agent, now you can test JavaScript in tests that use the SilkTest Open Agent with the xBrowser extension.

You can use ExecuteJavaScript to test anything that uses JavaScript. You can:

Custom Class Attributes in Java SWT and xBrowser Applications

You can enable custom attribute recording for a Java SWT or xBrowser application to make a test more stable. For example in Java SWT, the developer implementing the GUI can define an attribute (for example ‘silkTestAutomationId’) for a widget that uniquely identifies the widget in the application. A tester using SilkTest can then add that attribute to the list of custom attributes (in this case, ‘silkTestAutomationId’), and can identify controls by that unique ID. Using a unique ID is more reliable than other attributes like caption or index, since a caption will change when you translate the application into another language, and the index will change whenever another widget is added before the one you have defined already.

Using custom class attributes becomes even more powerful when it is used in combination with dynamic object recognition. For example, to find the first text field with the unique ID 'loginName' in your application, you can use the following query:

myWindow.find(".//TextField[@silkTestAutomationId='loginName']")

To create tests that use custom class attributes, you must use the Open Agent.

Ability to Suppress Controls for Certain Classes

Earlier versions of SilkTest support suppressing controls for certain classes for .NET applications that use the Classic Agent. Now, you can also suppress the controls for certain classes for Java SWT and Windows API-based applications that use the Open Agent.

New Methods Supported for Adobe Flex

SilkTest now supports the following additional methods for Adobe Flex:

The Flex MouseMove method has been replaced with the AnyWin::MoveMouse method. If you included MouseMove methods in your Flex scripts prior to SilkTest 2008 R2, you must manually update your scripts to use the MoveMouse method. Otherwise, errors will occur with your existing scripts.

Silk4J Eclipse Plugin

The following significant enhancements and changes were made for Silk4J.