Known issues in SilkTest 2008

The following are known issuesand provides work-arounds where availablein SilkTest 2008.51Testing软件测试网
x;v+^]"N[`

General

• Using silent installer on Windows 64-bit systems sets wrong environment variables and installs some files to the wrong location. Workaround: Change the szDir value in the Install.iss file to reflect the location where you want to install SilkTest to, for example szDir=C:\Program Files (x86)\Borland\SilkTest. For detailed information on using the silent installer, see theSilkTest Installation Guide. [38734]
• AutoComplete does not distinguish between SilkTest Agents. As a result, AutoComplete displays all methods, properties, variables, and data types regardless of the SilkTest Agent that you are using. For example, if you are using the SilkTest Open Agent, functions and data types that work only with the SilkTest Classic Agent are also displayed when you use AutoComplete. For details about which methods are supported for each SilkTest Agent, review the corresponding .inc file, such as the winclass.inc file.
• The keyboard delay value (OPT_KEYBOARD_DELAY) and the mouse delay value (OPT_MOUSE_DELAY) should not be greater than the window timeout value (OPT_WINDOW_TIMEOUT).
• Using CaptureBitmap on a system where the color depth is 256 colors (8-bit) causes the Open Agent to crash. [38712]
• Using SWT ScrollBar.SetPosition, returns "*** Error: Position cannot be reached." [38536]
• Cannot upload a testplan to SilkCentral Test Manager using a secure Tomcat frontend server. [38532]
• Occasionally, the frame.inc file is created in the SilkTest installation directory, rather than in the project directory. [38455]
• Setting the recovery system using the command line results in compile errors if the characters "{ }" are included. For instance, including coveragepath={"C:\Program Files\Borland\SilkTest\JavaEx\TestApp.jar"}in the command line results in a compile error. [38190]
• When opening the context menu of the Text field on the "Popup Menu" dialog, the OpenContextMenu Action is recorded on the Main Window of the application. As a result, replay fails. [37900]
• StarTeam integration is not available with SilkTest 2008. [37740]
• SilkTest crashes when using the FindWindow function. Workaround: Use 'tag "{sTag}"' instead of 'tag sTag' and the crash no longer occurs. However, FindWindow() is not able to find window declarations using dynamic tags. [37081]
• Executing a SilkTest testcase using the SilkCentral Test Manager interface fails with the error, "Failure invoking SilkTest executable." Workaround: Start SilkTest using the SilkTest interface. ChooseOptions\Agentand then click theTimingtab. Set theKeyboard event delayandMouse event delayvalues to 0.2. You can now invoke the SilkTest executable using the SilkCentral Test Manager. [37066]
• For machines running Windows 2003 SP2, the SilkTest Classic Agent name cannot be set using NetBIOS. [36625]
• On 64-bit systems, SilkTest fails because the QAPHOOKS_INIDIR environment variable is set incorrectly. Workaround: Change the QAPHOOKS_INIDIR environment variable from "C:\ProgramData\Borland\SilkTest" to "C:\Program Files (x86)\Borland\SilkTest\". [35566]
• On Windows Vista, captured bitmaps are not recognized. [34800]
• In a dual core environment, SilkTest may encounter problems because of timing issues. [34475]
• If VerifyProperties() fails for a dialog, e.g. "File open" or "Save as", regardless of which property was selected for verification, call SetActive() for the dialog window before. The problem is that otherwise the Exists property is always false, which causes VerifyProperties() to fail. [34128]
• In Windows XP environments where Visual Studio is installed, occasionally SilkTest hangs when a test is executed. [32974]
• In the accex.inc file, which is used for accessibility testing, the accSelect and the accNavigate methods are commented out. These methods and their related constants did not go through formal QA testing and are not supported in this version of SilkTest. The SELFLAG constants, which are used as the parameters for accSelect, will eventually call IAccessible::accSelect. For more information, refer tohttp://msdn2.microsoft.com/en-us/library/ms696148.aspx. The NAVDIR constants, which are used as the parameters for accNavigate, will eventually call IAccessible:accNavigate. For more information about the NAVDIR constant, refer tohttp://msdn2.microsoft.com/en-us/library/ms697230(VS.85).aspx. [32018]
• SetText() is appending characters instead of substituting characters. Workaround: Use ClearText() before calling SetText(). This prevents the extra characters from being appended. [31961]
• A mapped network drive cannot handle more than 235 chars when using FileOpen(). Workaround: Use shorter filenames. [29557]
• If you notice a performance degradation with the browser when SilkTest is not running, chooseTools > 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]
• 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]
• If you chooseHelp > Help > Tutorialsand receive an error, such as "The file or path was not found", use the directSilkTest tutorials linkinstead. This problem most likely occurs on Windows 2003 and Vista machines.

Browser

• browserChild in Internet Explorer 7 does not have the parent Browser as default. This is due to the implementation of IE7. If the existing browserChild windecl does not have the parent statement, you may see a runtime error similar to "browserChild xxx not found". Workaround: Add parent Browser to the windecl.
• With Internet Explorer 7, Record/Replay menuitems does not work. Workaround: Interactions with menu items and other controls that are defined in the explorer.inc file should not be recorded. Use the window declarations in the explorer.inc file. [38413]
• If Mozilla Firefox is set as your default browser, an error message may occur when you access a URL from another application. Workaround: See Firefox issue246078. [36995]
• When Security Patch KB918899 is installed, SilkTest causes a crash of Microsoft Internet Explorer 6 on playback of testcase. This problem occurs 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 alsohttp://support.microsoft.com/kb/923996/). [29386]
• There is a memory leak in Internet Explorer when running Javascrīpt on a web page. Workaround: Restart the browser. [28965, 28593, 28334]
• 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 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]

Adobe Flex

• Participants in the SilkTest 2008 Early Release for Flex program who recorded Win32 applications with the Open Agent may need to re-record menu items. In the Early Release, the "&" sign for the shortcut was included when menu items were recorded. For instance, the New menu item was recorded as “&New”. Additionally, if there was a shortcut specified separated by a tab from the actual caption, it was recorded as “&NewCtrl+N”. Both cases were changed to record only “New”.
• When you press Ctrl+Alt to verify properties for an element, such as a combo box or drop-down list, the focus shifts from the element to the “Verify Properties” progress bar. Because of the loss of focus, the element disappears and SilkTest cannot verify the properties for the element. An error message also displays. This issue affects only those types of controls that close or disappear when the focus shifts to a different object on the screen. Workaround: Manually verify properites for elements that close or disappear when the focus shifts to a different object on the screen.
• Replaying the OLAPDataGrid results in a #1009 error occasionally. Workaround: Manually insert a sleep(1)function between the OLAPDataGrid control and the commands that continue the recording in the Flex application. [38538]
• When a user records a click on the “Refresh Browser” button and then continues recording against the Flex application in the browser, SilkTest does not record the time between the refresh process and the continuation of the recording. As a result, replay fails. Workaround: Manually insert a sleep function between the “Click Refresh button” and the commands that continue the recording in the Flex application. [37078]
• The following commands are not supported:
  • Record Method
  • Record Defined Window
  • Record Class
  • Record Window Locations
• A maximum of 20 Flex applications can be tested simultaneously. Windows 2000 platforms are the exception to this rule. See the following item for details.
• Windows 2000 does not support simultaneous testing on multiple Flex applications. Only one Flex application can be tested at a time. This is an operating system restriction. [38499]
• When you record actions, the actions are not shown immediately. Recorded actions are shown when recording stops.
• The recovery system for browsers is limited in the following ways:
  • If no URL is retrieved, you must enter the URL as a parameter for the browser in the command line string.
  • SilkTest does not identify the browser window as a browser window. Therefore, the browser class functions are unavailable.
• Functions/classes in the winclass.inc file that are marked with the “supported_ca” keyword are supported on the Classic Agent only.
• The SilkTest Flex Automation SDK is based on the Automation API for Flex. The SilkTest Automation SDK supports the same components in the same manner that the Automation API for Flex supports them. The following is a partial list of known issues:
  • Actions are recorded in invalid order if the ColorPicker control is open when you record actions outside of the ColorPicker control. SilkTest records the closing action for the ColorPicker control automatically and appends it after the recorded action. Workaround: Move the line with the ColorPicker control Close command into the correct line, or delete the line. [38482]
  • When the FlexUIMovieClip::ChangeFocus method is used, an error occurs in the Flash Flex Integration Kit. You can monitor this issue at:https://bugs.adobe.com/jira/browse/FLEXENT-750
  • The "mx:FormItem" does not work with automation. You can assign an empty label with at least one space to the FormItem to resolve this issue. For instance:

    "`+g5Q4O-W"B h.hC0mx:FormItem label=" "

    +u-g ]u b2i5Z
    zO:s
    `0

    I!\H[8b A#^Q0mx:Button id="myButton" label="Validate" click="{updateLabel ()}"/51Testing软件测试网7?,z)L.\ES1d?

    51Testing软件测试网&[jU{;s~g9t9M

    /mx:FormItem

    4u:M7z"hjvgj\0

    $yd*xE@f9R)x0You can monitor this issue at:https://bugs.adobe.com/jira/browse/FLEXENT-74751Testing软件测试网^
    l fY:om

  • If you record actions against controls that become visibile only when the mouse hovers over them, the replay will fail. SilkTest does not record the MouseOver action on controls of this type. As a result, the controls do not display during replay. For example, in the Flex Store sample application, in the Products view, when you move the mouse over a mobile phone, three buttons become visible. However, when you replay that action, it fails because the buttons are not visible during replay. To resolve this issue, manually add a MouseMove to the scrīpt before the buttons become visible.
  • The typekey statement in the Flex Automation API does not support all keys. You can use the input text statement to resolve this issue.
  • When an application is compiled with automation code and successive .swf files are loaded, a memory leak occurs and the application runs out of memory eventually. The Flex Control Explorer sample application is affected by this issue. The workaround is to not compile the application .swf files that Explorer loads with automation libraries. For example, compile only the Explorer main application with automation libraries. Another alternative is to use the module loader instead of swfloader. You can monitor this issue at:https://bugs.adobe.com/jira/browse/FLEXENT-402
  • Dragging and dropping an element that uses the FlexChart class may not work if a chart element is clicked near its edges before you start dragging the element. This results in a failed replay because the drag start coordinates can be incorrect.
  • The FlexTitleWindow control is recorded and recognized by SilkTest as a FlexPanel (although it is defined as a separate control).
  • If too many events are fired simultaneously, some events are suppressed by the API. For example, if the slider in the Flex scroll bar is moved too quickly, the last position is not recorded.

ai&p!_rn'^@ b0For more information about the Flex Automation API known issues, see theAdobe Flex Release Notes.

Adobe AIR

igJ+MEo"T0SilkTest does not support the following Adobe AIR functionality:

• FileDialog handling including: FileEvent, FileSystemComboBox, FileSystemDataGrid, FileSystemEnumarationMode, FileSystemHistoryButton, FileSystemList, FileSystemSizeDisplayMode, FileSystemTree
• HTML control (AIR introduces an HTML control that displays web content)
• Applications with multiple windows
• Drag and Drop operations on the FlexListBase extended controls

Java

• Double-clicking an item in JavaJFCListBox is recorded as two separate 'Select' statements, which causes replay to fail. Workaround: Manually remove one of the 'Select' statements. [34409]
• 'SetText' in a SWT Text field is intermittently recorded as 'TypeKeys'. For example, the recorded scrīpt occasionally records 'SWTControls.TabFolder.Button.Group1.ComboWithCreatableContent.ItemText.SetText ("...")' as
  W:gL QN ^CT2q0'SWTControls.TabFolder.Button.Group1.ComboWithCreatableContent.AddItem.TypeKeys ("...")' . Workaround: Manually change the scrīpt. [34164]
• Verifying properties for a dialog box fails regardless of which property of the dialog box is selected for verification. Workaround: Before verifying properties, issue a SetActive() for the dialog box. [34128]

Powerbuilder

• Using PowerBuilder 11, you cannot record actions against elements in a DataWin in a test application. For example, if you edit text in a DataWin/DWEditField, no action is recorded. However, if you move the mouse over the element, the recorder correctly recognizes the element, but does not record it. Only recording is affected by this issue; replay is not. [37287]

TrueLog

• TrueLog Explorer always displays the name of the scrīpt as scrīpt(#1).
• TrueLog Explorer only displays 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.
• The bitmap for a button click action that closes a child window can be a blank gray area in the "After action" tab. That occurs due to a timing problem, because the window is already closed when the screenshot is taken. [34655]
• A TrueLog component outline box can be out of alignment because certain technologies, such as Java, do not always provide the necessary information accurately. [34563]
• Depending on the amount of controls on a Web page, enabling the "Control Creation/Deletion" option for Firefox tests can adversely affect the performance of the TrueLog Explorer. [34098, 34102]
• When recording against an application with a transparent dialog box, the bitmap is not captured. [29143]
• 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]
• 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 Descrīption field for the error. For example:51Testing软件测试网'c?{4Es
  raise 10, "Exception 10", "Notepad.exe"51Testing软件测试网-V%Zep;B`,Y$p
  will result in the TrueLog descrīption:51Testing软件测试网m6~ZR SA7ll'T
  Exception 10Notepad.exe
  O L(j(Jd.AY9D&h_0[27645]