This section lists significant enhancements and changes that were made to the product for SilkTest 8.0, and tells you where to look for more information when appropriate.

Technology Support

SilkTest 8.0 includes both new and updated support for several leading technologies:

• Eclipse 3.0 and 3.1 on Windows only (see Supported environments and technologies for details)
• Internet Explorer 7 beta 2, with limited support for tabs
• Beta support for Firefox 1.5.0.1, 1.5.0.2 and 1.5.0.3, with limited support for tabs
• Infragistics NetAdvantage WinForms (see Supported environments and technologies for details)
• .NET Common Language Runtime v2.0

Test Creation and Maintenance

• New tagging for browser page elements, leveraging the HTML object attributes for more robust and maintenance-free window declarations
• New "virtual object" capability for enabling window declarations of custom windows which will record Click and DoubleClick interactions
• Leveraging Microsoft's Active Accessibility (MSAA) into window declarations for eased testing of custom objects which implement MSAA
• Extended support for replaying browser tests using the DOM API to drive web page element interaction. By default, API clicks rather than Agent clicks will be used to improve the reliability of SilkTest playback of recorded Click() calls. This applies to click-based methods for HtmlRadioList and HtmlCheckBox; Select() for HtmlRadioList; and Check(), SetState(), Toggle() and Uncheck() for HtmlCheckBox. One of the primary reasons for introducing API clicks is to avoid geometry problems such as those sometimes encountered when manipulating elements within <div> HTML tags. DOM API based clicks can be turned off and Agent based clicks can be enabled via the checkbox Only use Agent-based clicks(not API-based clicks) on the Agent Options dialog as well as by specifying TRUE for the Agent option OPT_AGENT_CLICKS_ONLY via the Agent.SetOption call.

Compatibility with previous releases

This release includes modifications and deletions to supported versions of Windows as well as GUI and browser specifiers. This means that any existing object files will be incompatible with this release, and source files will be automatically recompiled if they are available. If you run object files only, you will have to recompile the sources for those objects before you can use them with SilkTest 8.0.

This release does not support the Virtual Object (VO) extension; to test web applications in browsers, you must use the Document Object Model (DOM) extension.

If you use the new attributes tagging on a project from a previous version of SilkTest, you will no longer be able to use what is now a 8.0 project with previous versions of SilkTest. For more information, see the known issue.

There is no support for SWT controls or Eclipse applications on UNIX through the SilkBean.

Where to go for more information

We have updated the following documentation for SilkTest 8.0:

This section includes information about the supported environments and technologies for SilkTest 8.0:

• the platforms that the SilkTest User Interface and Windows Agent run on
• the platforms the SilkTest 8.0 Agents runs on
• the Java versions that SilkTest 8.0 supports
• the Infragistics versions that SilkTest 8.0 supports
• the DSNs the Data Driven Workflow supports
• supported versions of PVCS

Platforms for SilkTest User Interface and Windows Agent

The SilkTest 8.0 User Interface and the SilkTest 8.0 Windows Agent run on the following platforms:

• Windows 98 (2nd, Millennium Editions)
• Windows 2000 (version 5.0, Service Pack 4)
• Windows XP (version 5.1, Service Packs 1, 1a, 2)
• Windows Server 2003 (Service Pack 1)

SilkTest 8.0 Windows-only testing 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.2, and 1.5.0.3
• Internet Explorer 6 (Service Pack 1) and beta support only for 7 (beta 2)
• Netscape Navigator 7.0x and 7.1
• DHTML (JavaScript and CSS)
• XML
• Microsoft HTC/HTA

For more information, see this table which lists more details about the different combinations that SilkTest 8.0 for Windows supports.

SilkTest 8.0 Windows-only testing also supports applications developed in:

• .NET Standalone WinForms and WebForms using the Common Language Runtime versions 1.0, 1.1, and 2.0
• 3270/5250 Applications via BlueExpress
• ActiveX
• Java
• Powerbuilder 9 and 10
  SilkTest does not support new controls developed in PowerBuilder 6.5 and later.
• Visual Basic 6
• Win32, MFC

Additionally, the SilkTest Extension Kit provides specialized support of custom objects. See the online help for more information about the Extension Kit.

Platforms for SilkTest 8.0 Linux and Solaris Agents

SilkTest 8.0 Agent for Red Hat Linux runs on the following platforms:

• Red Hat Enterprise Linux WS version 3.0
• Red Hat Enterprise Linux WS version 2.1

SilkTest 8.0 requires that you apply any current Red Hat updates for both Linux workstations.

• Solaris 10
• Solaris 9

The Agent for Sun Solaris supports 32-bit applications only.

• Java
• Motif 2.1 and 2.2

Java versions

SilkTest supports the following Java components:

• Sun's Java Development Kit (JDK/J2SE) versions 1.4.2_01 and 1.5
• Eclipse 3.0 and 3.1 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é
• Playback on Linux, Solaris and HP-UX via SilkBean
• Applets
• Native Microsoft JVM
• Sun's Java Plug-in 1.2, 1.3, 1.4, and 1.5.0

The SilkTest SilkBean allows for playback with SilkTest_Java3.jar. If you are going to test SilkBean we advise that you do not use SilkTest_Java2.jar for playback instead of SilkTest_Java3.jar. For more information on configuring the SilkBean, see the online Help topics under "Testing with the SilkBean."

SilkTest does not support JVM 1.4.1_03.

Infragistics Support

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

• 4.3.20043.27
• 5.1.20051.37
• 5.2.20052.27
• 5.3.20053.50

SilkTest can be configured post-installation to support NetAdvantage version variations in the last two version fields, for example, 20043.27, as described in the SilkTest online help.

Supported DSNs

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

Supported versions of PVCS

SilkTest's proprietary version of PVCS 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.

We recommend that you run SilkTest with:

• A PC with a Pentium processor running at a minimum of 200 MHz.
• A hard drive with 60 MB of free space.
• 16 MB of RAM (64 MB if you are testing Java). Add to this the amount of RAM required to run your application under test.

For more information about SilkMeter license server requirements and other important installation guidelines, see the Installation Guide.

This section provides a list and descriptions of defects and enhancements reported against a previous release that were fixed in this release.

• Changes to supported platforms and environments
• Attributes tagging
• DOM extension
• Java support
• ActiveX/VB extension
• General

Changes to supported platforms and environments

• Windows 95, NT4 6A, Windows 2000 SP 1,2,3
• Internet Explorer 4 (SP2), IE 5.01, IE 5.5, IE 6 SP 0 ("Gold")
• Netscape Navigator 4.x, 6.x
• PowerBuilder 6.5, 7, 8
• J2SE 1.1, 1.2.2, 1.3.0, 1.4.0, 1.4.1
• America Online 7, 8 and 8 Plus
• SilkTest's VO extensions

In general, SilkTest attempts to preserve backward compatibility. However, the discontinuation of support for VO extensions, leaving only one extension (the DOM extension) per browser version, made it desirable to streamline the list of browser specifiers in 4Test.inc. Additionally, 4Test.inc included several GUI specifiers that represented platforms that have not been supported for quite a few versions of SilkTest, so the list of GUI specifiers has also been trimmed. If your automation uses GUI or browser specifiers that have been eliminated or renamed, then you will need to modify it. There is information available from the Technical Support web site that describes the changes to the specifier lists and will aid you in updating your automation.

Attributes tagging

Previously, SilkTest recorded five tags to identify Html page elements: caption, prior text, index, window ID, and element. In SilkTest 8.0, there is an additional tag named "attributes”, which gives you a flexible new way to uniquely identify an Html page location. You use the attributes tag to select any Html attribute you want to record, including custom attributes.

There are two changes to SilkTest that are related to attribute tagging:

• You now have the ability to specify the order of precedence for how SilkTest records the different types of tags on the new Edit Class Attributes dialog
• The expansion of the number of characters that appears in the Attributes field of the Record Window Declarations dialog and that you can paste to the SilkTest Editor. You may now paste up to 4096 characters.

The attributes tag does not use the [n] notation to distinguish between windows with the same value of the tag. For more information see "Attributes tag notation" and the "Enabling Html class attribute recording" topics in the online Help.

DOM extension

• A problem with tag generation has been fixed that in certain situations caused an empty string to be inserted into a window declaration for its tag. The tag would be displayed properly in the Record Window Declarations Tag Information box, but the tag in the declaration would be incorrect.
• The DOM extension will now more gracefully handle Unicode characters in object captions. Note that tags for such objects will be different than tags created prior to SilkTest 8.0. However, since the tags in prior versions would have been unusable without manual adjustment with wildcards, existing automation should not be affected.
• The default value of UseScrollIntoView has been changed back to FALSE. In SilkTest 7.5x and 7.6x, the default value was TRUE. Note that API-based clicking is not affected by the value of this option.
• We have fixed an IE DOM extension problem, concerning browsers embedded in ActiveX controls in browser pages. Now SilkTest will see the embedded browser page as a BrowserChild child of the ActiveX control, and will properly handle the HTML children of the BrowserChild.
• The DOM extension will now properly determine the location of items in scrollable overflow elements that are defined with the styles 'overflowX' or 'overflowY'. Previously only the 'overflow' style was handled properly.
• A problem with the IE DOM extension has been fixed that caused applications containing embedded browsers to crash when using SilkTest.
• A DOM extension problem has been fixed that involves determining the location of objects in a nested browser frame. If a browser frame sits within a browser frame that is not the top frame on the page, then the offset of the nested frame would have been factored in twice. Now the location of objects in that frame will be calculated correctly.
• The recorder will now generate the correct coordinates for MoveMouse() actions for HTML elements with overflow. Previously, coordinates may have been too large, causing a 'Mouse coordinate is off the screen' exception upon playback.
• The DOM extension's scrolling algorithm has been improved to properly handle HTML elements with overflow. NOTE: You must set UseScrollIntoView=FALSE, either in domex.ini or via the BrowserPage.SetUserOption() method. The default value of UseScrollIntoView, which is TRUE, will force the use of the DOM API's built-in scrollIntoView function, which does not work properly with overflow elements that are off-screen.
• SilkTest will properly record and playback against 'Browse...' buttons in web pages (i.e., <input type=file> HTML elements).
• The DOM extension will no longer cause Internet Explorer to crash when a web page contains frames that have been created by XSLT/XML.
• A regression problem has been fixed that caused the Verify Properties dialog and the VerifyProperties() method to fail to display or detect the contents of an HtmlTable. The contents were displayed/detected to be an empty list ({}).

Java support

• Recording actions against AWT menus and popup menus has been fixed for JRE 1.5. The recording of window declarations for menus/menu items in AWT applications running under JVM 1.5 has been fixed. Now Record Window Declarations will detect the captions, not just the indices, of menus and items. See the description of the AwtCompTreeLockTimeout Java option below for AWT popup menus.
• The new AwtCompTreeLockTimeout Java option applies only to AWT-based applications which contain AWT popup menus. It should not be used with other applications because it will slow performance. If your application contains AWT popup menus, then you should set this value to a positive number representing milliseconds (for example, 1000, representing 1 second) in order to prevent SilkTest from freezing when interacting with AWT popup menus. It is strongly recommended that you use PopupSelect() rather than JavaAwtPopupMenu::Pick().
  
  For more information about how to implement this option, see the "Setting Java extension options" topic in the online help.
• The AWTCompTreeLockTimeout option described above also fixes a Java extension concurrency problem that may have caused failures in multi-threaded applications in which one thread deleted a component created by another thread. The symptom of the failure is a Java exception stack that begins with the calls:
  java.lang.ArrayIndexOutOfBoundsException: No such child: 1
    at java.awt.Container.getComponent(Unknown Source)
    at segue.monitor.QapSwingMonitor$SwingEventListener.installListeners(Qap SwingMonitor.java)
  
• A problem has been fixed in the Java extension that may have prevented navigation through certain custom controls by means of the keyboard.

ActiveX/VB extension

• The ActiveX/VB extension will no longer crash when it queries the OLE interface of a control and receives an unexpected result due to non-standard implementation of the control. One such example of non-standard implementation would be a property that has the same name as a standard property but returns a value that is not consistent with the standard definition of that property.
• Additional checking has been added to the ActiveX extension in order to prevent the application under test from crashing during recording. Specifically, SilkTest will check that an object is not uninitialized or invalid before trying to record against it.
• A problem in the ActiveX/VB extension has been fixed that could cause an application to crash because of a pointer problem involving VB6 controls.
• There is new VB option, MsgTimeout, which you may need to adjust if you find the VB/ActiveX extension recognizes certain controls as CustomWin rather than as 4Test or recorded classes or if the application under test crashes while a test script is running. You adjust the MsgTimeout to control the timeout used for messaging in the extension. The default is 1000, which corresponds to 1 second. See the "Setting VB/ActiveX options" topic in the online Help for more information.
• The VB/ActiveX extension has been made more robust with respect to how it recognizes ActiveX controls in browser pages, especially when pages are loaded.
• There is a new configuration option in the ActiveX extension that lets you choose whether or not to display the full window hierarchy. The option, ShowAllWin, is set in axext.ini. In the default mode (ShowAllWin omitted or set to FALSE), which is backwardly compatible with previous versions of SilkTest, certain windows perceived to be containers are filtered out in order to simplify the window hierarchy. When ShowAllWin is set to TRUE, the full window hierarchy is displayed. You should try to set the option to TRUE if a control that you need to test is not recognized because it has the same position and size (in other words, the same rectangle) as another control that is recognized.
• Synchronization between the ActiveX extension and the Agent has been improved, which will eliminate some instances in which the ActiveX extension seems to stop working and supported Visual Basic or ActiveX controls are seen as CustomWin.
• We have fixed a problem which caused inconsistent recognition of ActiveX components. The problem was a side effect of fixing a different problem that caused the application under test to crash in certain circumstances when an object was destroyed. If your application under test crashes, try adding the SetAdvSink=FALSE option to the [VBOptions] section of axext.ini in the 'extend' subdirectory of the SilkTest installation directory (not of your project directory if you are using a SilkTest project). See the "Setting VB/ActiveX options" topic in the online Help for more information.

General

• The recorder no longer ignores your preference for tag types when recording tags for HTML classes. This change in behavior is the result of removing the 'setting MultiTags' statements from the classes for controls in extend\htmlpage.inc.
• the .NET extension now supports the UltraWinGrid and UltraWinToolbars container for multiple versions of Infragistics NetAdvantage.
• There is a new GUI specifier, msw2003, that denotes the Microsoft Windows Server 2003 operating system. See also the description of changes to supported platforms and environments.
• There are two new options you can use when starting up SilkTest via the command line.
  • -smlog tells SilkTest to log SilkMeter messages to a file you specify; the messages appear in the log file in addition to appearing in dialogs.
  • -quiet starts SilkTest in "quiet mode", which prevents any pop-up dialog boxes from appearing when SilkTest starts up.
  For more information, see the "Starting SilkTest from the command line" topic in the online help.
• You can now use class-mapping to ignore window classes for the .NET extension. Simply map the class to "Ignore". Note that other extensions do not support class-mapping, so you must modify the extension .ini file in order to ignore window classes in the Java or ActiveX/VB extensions.
• For a browser frame (non-top-level BrowserChild), the window ID form of the tag will be the frame name (value of its NAME attribute) if there is one. As in previous versions of SilkTest, for a top-level BrowserChild, the window ID form of the tag will be its URL.
• If you edit the recorder contents when using Record Testcase or Record Actions, you must allow SilkTest to update the window declarations. The "Paste testcase only" option will be disabled.
• Using a TAB character (chr(9)) in a SetMultiText() or SetText() call will now work properly with multi-line TextField objects.
• We fixed a limitation involving the use of unique child objects in tags. Previously, the unique child object could be 2 levels below the window at most ("<unique child tag>/../.."). Now the level can be deeper (e.g., "<unique child tag>/../../..").
• You can now use the construction 'if..else if..else' with conditional expressions that compare constants. Previously, such a construction would have been incorrectly interpreted as two independent 'if..else' blocks.
• A problem with multilevel tags that use "/.." has been fixed. In previous releases, slashes caused memory allocation problems and caused SilkTest to crash.
• In order to enforce the ban on modifying files while SilkTest is in debug mode, File/Project menu items will be disabled while in that mode. The items will be enabled after SilkTest exits the debugger.
• A problem has been fixed that in certain circumstances would cause the error dialog "Unable to open <Results file>" to appear when running multiple testcases from a multitestcase.
• SilkTest no longer crashes when you declare a DLL which uses as the DLL name a variable that contains the CurrentPath keyword.
• The SetActive() method for the BrowserChild class will raise a 'Window was not found' exception if the wrong BrowserChild is present.
• You can now specify a host adapter number when using the NetBIOS protocol for distributed testing. Previously the adapter number had to be 0, which prevented the use of NetBIOS protocol with adapters that were not set to 0. If you were previously unable to use the NetBIOS protocol with Windows XP, the problem may have been the adapter number.
• Creating a test frame for a .NET application for which the main window is a dialog box (SwfDialogBox) will now set the class of the window will be set to SwfMainWin (with class "[SwfDialogBox]" included in the window tag) rather than to SwfDialogBox. This fix will allow DefaultBaseState() to call the proper Invoke() method to bring up the application.
• Test Manager can now execute tests and retrieve results for SilkTest testplans and scripts that contain (and/or have file names that contain) extended ASCII characters (such as a vowel with an umlaut).
• The SilkTest installation program now adds the SilkTest directory to the end of the PATH environment variable, in order to ensure that the file msvcr70.dll is in the path. This path modification will allow the .NET extension to load properly even when the application under test uses msvcr71.dll instead.
• Two problems have been fixed that could prevent SilkTest from loading an extension into an application if the application was shut down and then was restarted with the same process ID. This situation could occur for any extension if recording or playback was initiated when the application was already started but the Agent was not. It could also occur specifically for the ActiveX extension if the application terminated abnormally.
• An optional modification has been made to the browser extension's scrolling algorithm which may improve handling of off-screen HTML elements with overflow. In order to take advantage of the modification, you must set a new browser user option, UseOverflowScrolling, to TRUE, either in domex.ini or via the BrowserPage.SetUserOption() method. The default value of UseOverflowScrolling, which is FALSE, causes the browser extension to use the same scrolling algorithm that was used in previous versions of SilkTest.
• When you upload a test plan to SilkCentral Test Manager and a verification error occurs, the cursor will locate to the line in the plan file just below the erroneous line after you click OK on the error dialog.
• The file rms.inc, which is used by the interface with SilkCentral Test Manager, will now work with the UNIX/Linux Agent. Please note that for machines running the UNIX/Linux Agent, rms.inc reports the free memory as 0 in the log file.
• You can now use the LoadLibrary() method with the browser extension as well as with the .NET extension. It has been expanded to apply to the Browser window as well as to the SwfMain and SwfDialogBox classes. You use LoadLibrary() to enable a test script to direct a .NET or browser-based application to load an you created extension using the Extension Kit.
• A problem has been fixed concerning the use of pop-up menus with SilkBean. However, if you use either the PopupSelect() method or the JavaJFCPopupMenu (or JavaAWTPopupMenu) class, you must first explicitly issue a right-mouse Click() in order to bring up the menu.

This section contains a list of known issues and limitations that were not fixed in this release, and provides workarounds whenever possible.

• SWT and Eclipse issues
• Attributes tag issues
• Firefox issues
• Internet Explorer issues
• General issues

SWT and Eclipse Issues

• SilkTest cannot record against popup menus that originate by clicking on controls (such as buttons) on JavaMainWin and JavaDialogBox. For more information, see the description of Scripting against popup menus and popup windows below.
• JavaSWTCheckBox does not play back in Eclipse IDE.
• SilkTest cannot record against a SwtComboBox if it is child of ToolBar.

Scripting against popup menus and popup windows

SilkTest 8.0 can only record against popup menus which appear as a result of an action on a JavaMainWin or JavaDialogBox control. SilkTest cannot record popup menus that appear as a result of other SWT controls. SilkTest is also unable to record a DropDown action on JavaSwtDropDownButton control.

You can, however, hand script the interaction against popup menus and popup windows. The following samples describe how to:

• add the declarations of popup menus and needed menu items by hand
• use the ActiveMenuSelect function
• use the DropDownMenuSelect method for JavaSwtDropDownButton
• script popup windows that appear as a result of an action on dropdown button

Add the declarations by hand

One alternative is to add the declarations of popup menu and needed menu items by hand. The bold text in the sample below shows what you would need to add a test script so that SilkTest can activate an SwtTestApp/Standard control/Toolbar against a Menu Dropdown button that appears on the toolbar.

	[+] window JavaMainWin SWTControls
		[ ] tag "SWT Controls"
		[-] JavaSwtPopupMenu PopMenu
			[ ] tag "$Menu"
			[ ] 
			[-] JavaSwtMenuItem Apples
				[ ] tag "Apples"
			[-] JavaSwtMenuItem Oranges
				[ ] tag "Oranges"
		[+] JavaSwtPageList TabFolder
			[-] multitag "TabFolder"
				[ ] "$TabFolder"
			[-] JavaSwtPage ToolBar
				[-] multitag "ToolBar"
					[ ] "$Composite"
				[-] JavaSwtGroup Group1
					[-] multitag "#1"
						[ ] "$Group[1]"
					[-] JavaSwtGroup ToolBarWithChildControl
						[-] multitag "ToolBar with child control"
							[ ] "$Group[3]"
						[+] JavaSwtToolBar ToolBar
							[+] multitag "#1"
								[ ] "$ToolBar"
							[+] JavaSwtDropDownButton PopupDropdown
								[-] multitag "popup dropdown"
									[ ] "$ToolItem[2]"
							[-] JavaSwtDropDownButton MenuDropdown
								[-] multitag "menu dropdown"
									[ ] "$ToolItem[1]"
	[+] window DialogBox Information
		[ ] tag "information"
		[ ] parent SWTControls
		[-] PushButton OK
			[-] multitag "OK"
				[ ] "$2"
	[+] window JavaDialogBox Shell
		[ ] tag "#1"
		[ ] parent SWTControls
		[-] JavaSwtListBox xList
			[-] multitag "#1"
				[ ] "$List"
	[ ] 
	[ ] 
	 [+] testcase tcPopupMenu_Example() appstate none
		[-] recording
			[ ] SWTControls.SetActive ()
			[ ] SWTControls.TabFolder.ToolBar.Group1.ToolBarWithChildControl.ToolBar.MenuDropdown.DropDown ()
			[ ] SWTControls.PopMenu.Oranges.Pick ()
			[ ] Information.SetActive ()
			[ ] Information.OK.Click ()v
			[ ] 
		[ ]
		

Using the ActiveMenuSelect function

The previous example shows the text that you would need to add to a script in order for SilkTest to successfully play back popup menus. Handscripting this information can be prone to errors especially when there are multiple popup menus, for example with toolbars that have multiple dropdown buttons. Each of buttons actually brings its own popup menu, but in declarations all menu items from different menus appear in one large declaration which is not ideal. There is a way to declare such things dynamically, but the syntax is not obvious.

To resolve this issue you can now use the new ActiveMenuSelect method. ActiveMenuSelect is applicable to SWT controls only; you cannot apply it to JavaMainWin or JavaDialogBox controls. (You should not need to apply ActiveMenuSelect to those controls as recording and playback for Popup menus originates from the top-level windows and do not need any additional scripting.)

The function has a following declaration

ActiveMenuSelect (wWINDOW, sMenuItem)

You can use the ActiveMenuSelect function on any control if the resulting action on the control displays a popup Menu. It picks the specified item from a Popup Menu. For example:

	 MyControl.DoSomethingToShowPopupMenu ()
	ActiveMenuSelect (MyControl, "MyFavoriteMenuItem")

A longer sample of using this function for SwtTestApp/StandardControl/Toolbar on MenuDropdown button in a toolbar is shown below. Notice there are two testcases in this fragment; the second testcase is an example of using the DropDownMenuSelect method.

	 [-] window JavaMainWin SWTControls
		[ ] tag "SWT Controls"
		[+] JavaSwtPageList TabFolder
			[-] multitag "TabFolder"
				[ ] "$TabFolder"
			[-] JavaSwtPage ToolBar
				[-] multitag "ToolBar"
					[ ] "$Composite"
				[-] JavaSwtGroup Group1
					[-] multitag "#1"
						[ ] "$Group[1]"
					[-] JavaSwtGroup ToolBarWithChildControl
						[-] multitag "ToolBar with child control"
							[ ] "$Group[3]"
						[+] JavaSwtToolBar ToolBar
							[+] multitag "#1"
								[ ] "$ToolBar"
							[+] JavaSwtDropDownButton PopupDropdown
								[-] multitag "popup dropdown"
									[ ] "$ToolItem[2]"
							[-] JavaSwtDropDownButton MenuDropdown
								[-] multitag "menu dropdown"
									[ ] "$ToolItem[1]"
	[+] window DialogBox Information
		[ ] tag "information"
		[ ] parent SWTControls
		[-] PushButton OK
			[-] multitag "OK"
				[ ] "$2" 
	[ ] 
	[+] testcase tcActiveMenuSelect_Example() appstate none
		[-] recording
			[ ] Window w
			[ ] SWTControls.SetActive ()
			[ ] SWTControls.TabFolder.ToolBar.Group1.ToolBarWithChildControl.ToolBar.MenuDropdown.DropDown ()
			[ ] w = SWTControls.TabFolder.ToolBar.Group1.ToolBarWithChildControl.ToolBar.MenuDropdown
			[ ] ActiveMenuSelect (w, "Oranges")
			[ ] Information.SetActive ()
			[ ] Information.OK.Click()
			[ ] 
		[ ] 
	[+] testcase tcDropDownMenuSelect_Example () appstate none 
		[+] recording
			[ ] SWTControls.SetActive ()
			[ ] SWTControls.TabFolder.ToolBar.Group1.ToolBarWithChildControl.ToolBar.MenuDropdown.DropDownMenuSelect ("Apples")
			[ ] Information.SetActive ()
			[ ] Information.OK.Click()
		[ ]
		

Using the DropDownMenuSelect method for JavaSwtDropDownButton

The dropdown button is the most common way of generating Popup menus in SWT. The dropdownbutton.DropDownMenuSelect(sItem) method combines the DropDown method and the ActiveMenuSelect function in a single method for the JavaSwtDropDownButton class. See above for an example of how to use it.

Scripting Popup windows that appear as a result of an action on dropdown button

In this case only the DropDown action on JavaSwtDropDownButton is not recorded but the Popup Window is recorded and played correctly. This means that you only have to insert a line with the DropDown statement into the script.

The sample code below shows how SilkTest records the SwtTestApp/Standard Control/Toolbar with a popup dropdown button in toolbar.

	 [+] window JavaMainWin SWTControls
		[ ] tag "SWT Controls"
		[+] JavaSwtPageList TabFolder
			[-] multitag "TabFolder"
				[ ] "$TabFolder"
			[-] JavaSwtPage ToolBar
				[-] multitag "ToolBar"
					[ ] "$Composite"
				[-] JavaSwtGroup Group1
					[-] multitag "#1"
						[ ] "$Group[1]"
					[-] JavaSwtGroup ToolBarWithChildControl
						[-] multitag "ToolBar with child control"
							[ ] "$Group[3]"
						[+] JavaSwtToolBar ToolBar
							[+] multitag "#1"
								[ ] "$ToolBar"
							[+] JavaSwtDropDownButton PopupDropdown
								[-] multitag "popup dropdown"
									[ ] "$ToolItem[2]"
							[-] JavaSwtDropDownButton MenuDropdown
								[-] multitag "menu dropdown"
									[ ] "$ToolItem[1]"
	[+] window DialogBox Information
		[ ] tag "information"
		[ ] parent SWTControls
		[-] PushButton OK
			[-] multitag "OK"
				[ ] "$2"
	[+] window JavaDialogBox Shell
		[ ] tag "#1"
		[ ] parent SWTControls
		[-] JavaSwtListBox xList
			[-] multitag "#1"
				[ ] "$List"
	[ ] 
	[ ] 
	
	[+] testcase tcPopupWindow_Example() appstate none
		[-] recording
			[ ] SWTControls.SetActive ()
			[ ] SWTControls.TabFolder.ToolBar.Group1.ToolBarWithChildControl.ToolBar.PopupDropdown.DropDown ()
			[ ] Shell.SetActive ()
			[ ] Shell.xList.Select ("Peaches")
			[ ] Information.SetActive ()
			[ ] Information.OK.Click ()
		[ ] 

Attributes tag issues

• If you are using the SilkTest 8.0 to open a project from a previous version of SilkTest (for example, 7.5), be aware that SilkTest 8.0 adds an additional attribute to your project .ini file. If you use the new attributes tagging with this project, you may no longer open this project in previous versions of SilkTest.

Firefox issues

• SilkTest 8.0 has beta support for the recorder in Firefox which means:
  • the recorder may be slow
  • in order to click on a link you must press and hold down the mouse button and wait for a response
  • Record Actions does not recognize coordinates of XUL buttons
  • DoClick does not successfully work on Html images or on Image Maps in browsers
  Workaround: Increase memory.
• If you are testing against Firefox, you must manually configure the browser by clearing the 'Hide the tab bar when only one web site is open' field on the 'Tabs' tab of the Options dialog. Otherwise, the new CloseOtherTabs() method will not work properly; specifically, it will open all the sites on the Quick Launch bar in separate tabs.
• If you are recording an application using the Firefox browser, SilkTest captures different coordinates for the Click() method if you use Record/Testcase and compare that with the results you get during Record/Actions.
• When using the Firefox or Netscape browser extensions, do not use API click mode when calling the Click() method for an HtmlPushbutton that will bring up a modal dialog. The Click() method will never complete, effectively hanging the test script. Instead, use Agent click mode. You can force Agent click mode for specific calls by calling 'Click (1)' instead of 'Click()'.
• Do not call the Click() method for a XulPushButton if clicking the button brings up a modal dialog. The Click() method will never complete, effectively hanging the test script. Note that XulPushButton controls are generally pushbuttons that are part of the Firefox or Netscape browser window.
• The Firefox extension assumes that the decimal symbol is a period (.). If you are testing Firefox and are using a locale for which the decimal symbol is a different symbol, such as a comma, then please use the Regional Options in the Control Panel to either change your locale, or to change the decimal symbol for your current locale to a period.
• You may not enable Firefox 1.5 through SilkTest's Basic Workflow or otherwise work with Firefox if Netscape 7.0 is also running. Likewise, you may not enable Netscape 7.0 through SilkTest's Basic workflow or work with Netscape if Firefox 1.5 is running. Workaround: Close one of the browsers and continue.

Internet Explorer issues

• While SilkTest 8.0 supports Internet Explorer 7.0, there are several issues with support of tabs within IE 7.0. The tab bar is seen as a single custom window. Individual tabs are not recognized as distinct objects, nor may they be accessed by name or index. When you record tabs, SilkTest captures tab clicks by coordinates which means if the tab size or position changes, you must also change the coordinates in the test script. Workaround: Turn on Accessibility to record IE 7.0 tabs.
• On Internet Explorer 7.1, if you make a selection from an HtmlPopupList twice in a row, SilkTest does not record the first selection; SilkTest records the second selection twice.
• JavaJFCRadioButton.HasFocus() does not work properly on Internet Explorer 6 or 7.
• DoubleSelect() does not work properly with Internet Explorer 7.

General issues

• Casting a REAL to an INTEGER could return a value one less than the truncated REAL. For example, 25.343 could return 24 instead of 25.
• SilkTest_Java3.jar is designed to work with the Java subscription model, in which a component adds listeners for events that it wishes to handle. If you have an applet that uses the older model, which was deprecated in JVM 1.1 in 1997, then SilkTest_Java3.jar may prevent your applet from working properly even when SilkTest is not running. For example, an applet that functions as a menu may not respond to mouse clicks. If you encounter this situation, then use SilkTest_Java2.jar instead of SilkTest_Java3.jar. Note that Enable Extensions/Basic Workflow does not support SilkTest_Java2.jar, so you will have to configure the extension manually to use SilkTest_Java2.jar. See the on-line help for details.
• The VB/ActiveX extension only supports windowless controls when they are contained in windows that are created and destroyed whenever the windowless controls are created/destroyed. Otherwise, recognition problems, and in the worst case application crashes, may occur.
• We noticed in our testing that when dealing with calendar controls in UltraWinGrid cells, the format of the return value for the GetCellText() method differed among UltraWinGrid versions 4.3, 5.1 and 5.2, specifically with regard to inclusion of leading zeros or of a time component. Note that SilkTest does not modify the format of the value returned by the native UltraWinGrid method.
• ClickRegion() does not click on an image map when the browser is too small to display the entire image map. No exception is raised.
• When using AutoComplete, the member list occasionally may reveal methods that are not valid for the 4Test class. The compiler will not catch these usage problems, but at Runtime the following exception will be raised when the script is played back: *** Error: Function <invalid method> is not defined for <window class>.
• GetProperty() and GetPropertyList() on ActiveX controls in a browser return the properties of the parent BrowserChild, rather than of the ActiveX controls themselves.
• SilkTest hangs if you are using 1.4.2 and call Browser.Close() with the Java Console open.
• If an AWT applet in a browser causes a popup dialog box to appear, SilkTest does not see it as a JavaDialogBox and does not see any of the controls within the dialog box. Workaround: Map the AppletPopup custom class to the JavaDialogBox class via the Options/Class Map dialog.

Copyright Notice

© Copyright 1992 - 2006 Segue Software, Inc. All Rights Reserved. Trademark, warranties and disclaimers and software licensing rules apply. Please contact Segue with questions or comments.