SilkTest^® 2006 Release 2 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 in the current release, see the What's New section below.

What's New

This section lists significant enhancements and changes that were made for SilkTest 2006 Release 2.

Warning: If you upgrade your licenses to use SilkTest 2006 Release 2, 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 2006, and which supports these add-ons. Please consider this before visiting the License Generator.

Password Encryption

• SilkTest 2006 Release 2 now supports password encryption/decryption. Passwords can be encrypted, so that they are not displayed in recorded test scripts or when playing back test scripts.
  Two new functions, Decrypt() and Encrypt(), have been added to the 4Test language to support password encryption.

Calling DLL Functions

• SilkTest 2006 Release 2 supports 4Test calling of DLL functions (i.e., functions in DLLs declared in 4Test using the dll keyword) that accept Unicode (wide-character) and ANSI string data by marking their declarations using the new ansicall keyword. The ansicall keyword converts all string parameters from W (wide-character Unicode) to A (ANSI) character format before calling the DLL function internally. The ansicall keyword makes an ANSI call transparent, as the conversion is done internally.
  Note: If you created wrapper DLLs to convert Unicode strings to ANSI strings, the wrapper DLLs will still function. You do not need to update your code.

Rebranding

• The Segue DDA Excel data source has been renamed to Silk DDA Excel. Note that both data sources are supported in SilkTest 2006 Release 2. In the Select Data Source dialog box, Silk DDA Excel is the default selection. However, existing references to Segue DDA Excel will continue to function.
• The sJVMQuery SegueVersion string value for the GetJVMInfo method (JavaMainWin and JavaApplet classes) has been renamed to BorlandVersion. However, the string value SegueVersion will continue to function.
  [29395]

Silk TrueLog Explorer for SilkTest

• The Close Window Delay function has been replaced with TrueLog Delay. TrueLog Delay allows Windows time to draw an application window before a bitmap is taken. The delay can be used for browser testing.
• The TrueLog Options dialog box in SilkTest now includes three preset buttons for pre-determined logging levels.
• For local tests, the TrueLog file is created in the same directory as the results file when TrueLog File Name field contains only a filename, for example, MyTest.xlg. Use full pathnames for TrueLog files when testing on remote systems.

For more information on the Silk TrueLog Explorer, see the Silk TrueLog Explorer for SilkTest User Guide, available from Start > Borland > SilkTest 2006 R2 > Documentation > Silk TrueLog Explorer User Guide.

.NET DataGridView

• SilkTest 2006 Release 2 provides a new .NET 4Test class, SwfDataGridView. This class represents Microsoft’s .NET Framework DataGridView control, which displays data in a customizable grid. For more information, open the 4Test Reference book in the online Help, and choose Classes > .NET Classes. Choose SwfDataGridView from the list.
  To support this functionality, the GetSelCell and GetSelRange methods in the Table class were updated. Open the Index tab in the online Help, enter "GetSelCell" or "GetSelRange" and choose the entry for the Table class.

Timer Functions

• The timer functions have been modified to interface with SilkPerformer. The TimerCreate function now has an optional parameter, sTimerName, that you can use to name the resulting timer handle. There are also two new timer related functions: TimerGetName and TimerGetHandle. These changes have no impact on existing timer features used in SilkTest scripts.
  For more information, search by function name in the Index tab of the online Help.

Synchronizing Controls for Verification

• SilkTest 2006 R2 implements the ability to allow scripts to wait for a control to be in a particular state within a specified timeout, and to wait for a control to disappear. The VerifyProperties() method and other Verify...() methods have been enhanced with an optional timeout parameter, nTimeout.
• A Time To Wait for Properties field has been added to the Property tab of the Verify Window dialog box. The value in this field is passed to the AnyWin.VerifyProperties() method as the optional nTimeout parameter.
• The new AnyWin.VerifyExists method provides a simple method for verifying the existence or non-existence of a window or a control. This method is equivalent to using the bExists property of the VerifyProperties() method.
• The bExists property is now available on the Property tab of the Verify Window dialog box as Exists.

For more information, search for one of the Verify...() method topics in the online Help index or choose Getting Started > Designing and Recording Testcases > Verification > Synchronizing controls for verification in the online Help Table of Contents.

Installation

• The installation process has been streamlined. For more information, see the SilkTest Installation Guide.

Technology Support

• SilkTest 2006 Release 2 now supports the Windows Vista operating system. If the application under test is run with administrator privileges, both SilkTest (partner.exe) and the SilkTest Agent (agent.exe) also need to be run with administrator privileges. The GUI specifier for Vista is: mswvista
  Important: The Windows Help program WinHlp32.exe is no longer included with Windows Vista. A download for 32-bit .hlp files will be available from the Microsoft Download Center. For more information, see: http://support.microsoft.com/kb/917607
• SilkTest 2006 Release 2 now supports the Windows XP 64 bit operating system (testing 32 bit applications only). The GUI specifier for XP 64 bit is: mswxp64
• SilkTest 2006 Release 2 reintroduces support for the following technologies:
  • PowerBuilder 10.x (to, and including, 10.5)
  • SilkBean
  • Bitmap Tool - now accepts filenames with Unicode characters

  See the Supported Environments and Technologies section for more information.

System Requirements

Your computer must meet the hardware requirements listed below:

Supported Environments and Technologies

This section includes information about the supported environments and technologies for SilkTest 2006 Release 2:

• Platform Support
• Supported Environments
• Java Support
• Infragistics Support
• DSN Support
• PVCS Integration Support
• StarTeam Integration Support

Platform Support

SilkTest 2006 Release 2 runs on the following platforms:

• Windows 2000 (version 5.0, Service Pack 4)
• Windows XP (version 5.1, Service Packs 1, 1a, & 2)
• Windows Server 2003 (Service Pack 1)
• Windows Vista

SilkTest 2006 Release 2 supports applications which use the following browsers:

• AOL 9.0 and 9.0 Security Edition
• Beta support for Firefox 1.5.0.1 - 1.5.0.8
• Internet Explorer 6 (SP 1 & SP 2)
• Internet Explorer 7 (GA)
• Netscape Navigator 7.0, 7.01, 7.02, & 7.1
• DHTML (JavaScript and CSS)
• XML
• Microsoft HTC/HTA

SilkTest 2006 Release 2 supports applications developed in:

• .NET Standalone WinForms and WebForms using the Common Language Runtime versions 1.0, 1.1, & 2.0
• ActiveX/Visual Basic 6
• PowerBuilder 10x (up to, and including, 10.5)
• Java
• Win32, MFC

Additionally, the SilkTest Extension Kits provide specialized support of custom objects. See the SilkTest 2006 Release 2 Extension Kit for Windows and the SilkTest 2006 Release 2 Extension Kit for .NET PDFs, located in the Documentation folder of your SilkTest installation, for more information.

To get support for the following technologies, install SilkTest 8.0.

• Motif 2.1 and 2.2
• Windows 98
• Red Hat Enterprise Linux WS versions 2.1 and 3.0
• Sun Solaris versions 9 and 10

See the SilkTest 8.0 release notes for more information.

Note: BlueExpress is no longer supported.

Supported Environments

Supported environments, by platform, are listed below. For supported environments, technical support is available and defects can be logged. Note that it is not possible to test all combinations. Experience indicates that various combinations can result in different behavior with SilkTest. Borland makes every attempt to test as many of these combinations as possible.

• Internet Explorer 6 (SP1 & SP2)
• Netscape Navigator (7.0, 7.01, 7.02, & 7.1)
• Firefox (1.5.0.1 - 1.5.0.8) (Beta support)
• DOM embedded browser control (Win32 & MFC only)
• AOL (9.0 & 9.0 SE)
• .NET Framework (1.1)
• Infragistics NetAdvantage WinForms (5.3, 6.1, 6.2, & 6.3) (Using 1.x assemblies only)

• Internet Explorer 6 (SP1 & SP2)
• Internet Explorer 7 (GA)
• Netscape Navigator (7.0, 7.01, 7.02, & 7.1)
• Firefox (1.5.0.1 - 1.5.0.8) (Beta support)
• DOM embedded browser control (Win32 & MFC only)
• AOL (9.0 & 9.0 SE)
• .NET Framework (1.1, & 2.0)
• Infragistics NetAdvantage WinForms (5.3, 6.1, 6.2, & 6.3) (Using 1.x assemblies only)

• Internet Explorer 6 (SP1 & SP2)
• Netscape Navigator (7.0, 7.01, 7.02, & 7.1)
• Firefox (1.5.0.1 - 1.5.0.8) (Beta support)
• DOM embedded browser control (Win32 & MFC only)
• AOL (9.0 & 9.0 SE)
• .NET Framework (1.1)
• Infragistics NetAdvantage WinForms (5.3, 6.1, 6.2, & 6.3) (Using 1.x assemblies only)

• Internet Explorer 6 (SP1 & SP2)
• Internet Explorer 7 (GA)
• Netscape Navigator (7.0, 7.01, 7.02, & 7.1)
• Firefox (1.5.0.1 - 1.5.0.8) (Beta support)
• DOM embedded browser control (Win32 & MFC only)
• AOL (9.0 & 9.0 SE)
• .NET Framework (1.1 & 2.0)
• Infragistics NetAdvantage WinForms (5.3, 6.1, 6.2, & 6.3) (Using 1.x assemblies only)

• Internet Explorer 6 (SP1 & SP2) (32 bit)
• Internet Explorer 7 (GA)
• DOM embedded browser control (Win32 & MFC only) (32 bit browser control)
• .NET Framework (2.0)

• Internet Explorer 7 (GA)
• DOM embedded browser control (Win32 & MFC only)
• .NET Framework (3.0)
• Infragistics NetAdvantage WinForms (6.3) (Using 1.x assemblies only)

Important: The Windows Help program WinHlp32.exe is no longer included with Windows Vista. A download for 32-bit .hlp files will be available from the Microsoft Download Center. For more information, see: http://support.microsoft.com/kb/917607

Java Support

SilkTest supports the following Java components:

• Sun's Java J2SE versions 1.4.2 and 5.0
• Eclipse 3.0, 3.1 and 3.2 SWT standalone and Rich Client Platform (RCP) applications (SWT standalone applications executed as an applet in the browser not supported, embedded IE control inside of SWT standalone or RCP application not supported)
• AWT
• Java Foundation Classes (JFC, Swing)
• Symantec Visual Café
• Applets
• Sun's Java Plug-in versions 1.4 and 1.5

Infragistics Support

SilkTest supports Infragistics NetAdvantage WinForms UltraWinGrid and UltraWinToolbar controls within the following versions of the NetAdvantage Suite:

• 5.3.20053.50
• 6.1.20061.28
• 6.2.20062.34
• 6.3.20063.53

SilkTest can be configured post-installation to support NetAdvantage version variations in the last two version fields, for example, 20061.28, as described in the SilkTest Online Help.

DSN Support

SilkTest's Data Driven Workflow supports:

• Text files and comma separated value files (*.txt and *.csv files)
• MS Excel 2000
• MS Access 2000
• MS SQL Server 7.0
• Oracle 8x (partial support)
• SyBase SQL Anywhere v6.0

Note: The SilkTest Select Data Source dialog box allows you to choose either the Silk DDA Excel or the Segue DDA Excel data source. For new data driven testcases, choose the Silk DDA Excel data source. Choose the Segue DDA Excel data source for backward compatibility. This allows existing .g.t files that reference Segue DDA Excel to continue to work.

PVCS Integration Support

SilkTest's interface with the PVCS proprietary API supports:

We assume that you are familiar with PVCS and are familiar with how PVCS works. If you are not, consult your PVCS documentation and PVCS release notes for more information.

StarTeam Integration Support

SilkTest's interface with Borland StarTeam supports the SCC Integration module, available with both StarTeam 2005 Release 2 and StarTeam 2006.

Resolved Defects

The following items have been resolved in SilkTest 2006 Release 2.

• Cannot enable IE Extension when "enable ActiveX support" is checked.
  [30161]
• SYS_CompareBitmap causes an agent crash with certain bitmaps.
  [30778]
• When a tree element is in a certain position at the bottom of the treeview box, SilkTest is unable to find the element and throws the error "can't find the tree element".
  [29496]
• HTML ID or HREF tags are not visible at runtime, causing a window not found error.
  Fix: Window ID and attributes tagging has been extended, and the HTML HREF truncation at the 64th character has been removed.
  [30489]
• Browser.Maximize does not work on Windows 2003 Server.
  [29645]
• The RunLinkTester function requires editing 4test.inc to run.
  [29865]
• GetRowCount() returns the wrong number of rows.
  [29935]
• SilkTest is unable to verify properties against an HTML Table if the border is set to zero and border-collapse is set to true in CSS.
  [29873]
• Value property (GetProperty("$Value")) does not return the correct value when the first character of the value is a number.
  [29638, 29837]
• When activating Options/General/Member Type, AutoComplete crashes SilkTest.
  [29566]
• When deriving a class from Anywin, SilkTest reports a compile error on playback, stating that the function Select is not defined.
  [29989]
• Cannot inherit from winclass in winclass.
  [29498]
• RandStr causes a General Protection Fault in SilkTest after a lot of iterations.
  [29497]
• GetPageSource() shows frame source for Internet Explorer 5 but not for Internet Explorer 6.
  [29885]
• Declarations get corrupted by the attributes InnerText tag containing carriage returns. This is fixed now by replacing carriage returns with wildcards.
  [29570]
• There is a problem when recording and playing back against HtmlRadioList. If ungrouping the radio list causes a problem, then use the Agent to select the item, for example:
  set Agent.SetOption (OPT_AGENT_CLICKS_ONLY, TRUE)
  [29409]
• SYS_Execute causes an agent crash.
  [29444, 31345]
• ShowRows() delivers wrong return values for some table types.
  [29383]
• The file "qapwinek.h", which is referenced in the Extension Kit documentation, is missing.
  [29269]
• Incorrect CONST declaration on line 28 of the 4Test.inc file.
  [29194]
• Using GetMultiText on an HtmlTextField is not returning the line of text directly after a blank line in the results file.
  [29034]
• You can now match an item in a frame using attribute tags only.
  [28335]
• SgOcrLib.inc now uses an updated SgOcrLib.dll, with widened string functions. This fixes the invalid error generated by the OcrGetTextFromBmp() method.
  [29335]
• If an attribute value contains a brace, the attribute tag form will now replace the brace with the single-character wildcard (?). For example, for an HtmlTextField with name set to {Product}, the attribute tag is now recorded as:

  [ ] tag "&name='?Product?'"
  

  
  [29046]
• Full attribute matching for objects in a list or browser frame and objects that are direct children of the page has been implemented. The attribute tag now matches even if the declared tag contains a subset of the attributes currently specified in extend\attributes.ini.
  [28335]
• The SilkTest Agent can now run a Perl script with the SYS_Execute function.
  [29365]
• In versions of SilkTest prior to 8.0, the casting of a REAL to an INTEGER truncated the number. In SilkTest 8.0, the casting was rounded. In SilkTest 2006 Release 2, REAL numbers that are cast to INTEGER (or int) are rounded, not truncated. If you want truncation, use Print([INTEGER]r) instead of Print(r).
  [29537]
• Compilation errors in .inc files (.NET only) when in classic mode have been fixed.
  [29601, 29964]
• Fully expanded TreeView levels can now be recorded and run.
  [29580]
• The state of the Maximize button on the MainWin in a Java application can now be assessed with the AnyWin.IsEnabled() method.
  [29957]
• The MoveMouse() method is not defined for the Menu and MenuItem classes.
  [30008]
• The SYS_ file manipulation functions are for remote access. The non SYS_ file manipulation functions are for local access.
  [30009]
• If the type of an HtmlTextField is file, the HtmlTextField::Click() method will now call the Agent Click() method.
  [28399]
• When Active X is enabled, the browser no longer closes when it contains an embedded media player.
  [29844]
• When an object is out of scrollable view and only the horizontal scroll is visible, SilkTest will now automatically scroll the object into view, allowing it to be selected.
  [29974]
• The Accessibility extension now recognizes new accessible child objects.
  [29333]
• GetRowText() now finds the last item in a table when it is supplied with the row name rather than the row number.
  [29543]
• TransformDate() is now transforming dates correctly.
  [29904, 30137]
• If you use Enable Extensions on a .NET application for which the main window is a dialog box (i.e., has no menus), then SilkTest will report that the test failed because no SwfMain was found.
  [27949]

Known Issues

The following are known issues in SilkTest 2006 Release 2.

General

• Console.txt file is not created in Unix Systems. Workaround: None - the Console.txt output in Unix systems is not implemented in SilkTest Bean. [30011]
• A mapped network drive can not handle more than 235 chars when using FileOpen(). Workaround: Use shorter filenames. [29557]
• When Security Patch KB918899 is installed, SilkTest causes a crash of Microsoft Internet Explorer 6 on playback of testcase. This problem occurrs on Windows XP Service Pack 2 (SP2) or Windows Server 2003 Service Pack 1 (SP1) systems, after installing security update 918899. Workaround: Install the latest Windows hotfix (see also http://support.microsoft.com/kb/923996/). [29386]
• When borderless table level is set to "0" SilkTest sometimes recognizes borderless tables. Workaround: Record against Microsoft Internet Explorer 6. [31359, 31539]
• If you notice a performance degradation with the browser when SilkTest is not running, choose Tools > Manage AddOns. Choose QAPHlprObjClass from the Enabled list and click the Disabled option button in the Settings group box. Click OK to save the change.
  [28551]
• There is a memory leak in Internet Explorer when you are running JavaScript on a web page. Workaround: Restart the browser.
  [28965, 28593, 28334]
• The recorder does not highlight Java controls when recording in an applet on Internet Explorer on Windows XP SP2 machines. Workaround: Click anywhere inside the applet; the controls will then become visible during playback.
  [27416]
• If you receive an error message that the SilkTest_Java3.jar cannot be deleted when uninstalling SilkTest, then you must delete the file manually.
  [27548]
• When ShowHtmlForm=TRUE and ShowBorderlessTables is a value less than 1.0, SilkTest cannot recognize controls within a table even if ShowBorderlessTablesFlags is set to "input" or to "img|input". Workaround: Do not set ShowHtmlForm=TRUE.
  [27979]
• The Windows Help program WinHlp32.exe is no longer included with Windows Vista. A download for 32-bit .hlp files will be available from the Microsoft Download Center. For more information, see: http://support.microsoft.com/kb/917607
  [30697]

TrueLog

• The SilkTest Agent occasionally crashes when executed via SilkCentral Test Manager with enabled TrueLog generation.
  [31540]
• TrueLog Explorer always displays the name of the script as Script(#1).
• TrueLog Explorer does display Unicode characters if the machine displaying the TrueLog Explorer has the same code page as the Agent machine that created the TrueLog.
• TrueLog Explorer for SilkTest provides a read-only view of results.
• You may not run TrueLog simultaneously with multiple remote systems.
• If you are running a remote Agent, you may not put in a null path name for the TrueLog.
• If you raise an error in a testcase via a raise statement that specifies a command line, then the corresponding error entry in a TrueLog file will include the command line in the Description field for the error. For example:
  raise 10, "Exception 10", "Notepad.exe"
will result in the TrueLog description:
  Exception 10Notepad.exe
  [27645]
• In certain situations, the bitmap for an action that you are logging may be inaccurate. It may not show the correct window or the correct part of the window. This happens most frequently on the first case on the first action in a testcase. If this occurs, try inserting a SetActive method call just prior to the action in question in the testcase.
  [28138]
• When recording against an application with a transparent dialog box, the bitmap is not captured.
  [29143]

Installation Instructions

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

Getting Help

For information about using SilkTest, see the SilkTest Online Help, available from Help > Help Topics. You can also walk through the SilkTest tutorials, available from Start > Programs > Borland > SilkTest 2006 R2 > Documentation.

Borland offers a variety of support options. To find out about support options, refer to Borland Answers at http://support.borland.com. From the web site, you can:

• Find out how to contact Technical Support

• Browse the Borland Knowledge Base

• Access peer-supported product Forums for exchanging information, tips, and techniques

If your company has a support contract, you can open and update support cases, request product updates, browse Patches and Service Packs, and sign up for e-mail alerts from this web page.