Developer(s) | Micro Focus International |
---|---|
Stable release | 2010 Release 2 / December 23, 2010 |
Development status | Active |
Operating system | Microsoft Windows, Red Hat Enterprise Linux WS, Solaris |
Available in | English |
Type | Test automation |
License | Proprietary |
Website | Borland SilkTest |
SilkTest is an automation tool for testing the functionality of enterprise applications in most versions of Windows, Solaris 9 and 10, and Red Hat Enterprise Linux WS 2.1 and 3.0.[1] It was produced by Segue Software which was acquired by Borland in 2006. Borland was acquired by Micro Focus International in 2009. SilkTest became the strategic product to eventually replace TestPartner, which was acquired by Micro Focus International from Compuware.
SilkTest offers various clients: - SilkTest Classic uses the domain specific 4Test language for automation scripting. It is an object oriented language similar to C++. It uses the concepts of classes, objects, and inheritance. - Silk4J allows to do automation in Eclipse using Java as scripting language - Silk4Net allows the same in Visual Studio using VB or C# - SilkTest Workbench allows automation testing on a visual level (similar to former TestPartner)
Contents |
SilkTest identifies all windows and controls of the application under test as objects and defines all of the properties and attributes of each window. Thus it supports object oriented implementation (Partially).
SilkTest can be run to identify mouse movement along with keystrokes (Useful for custom object). It can use both record and playback or descriptive programming methods to capture the dialogs.
Extensions supported by SilkTest: .NET, Java (Swing, SWT), DOM, IE, Firefox, SAP Windows GUI.
SilkTest uses Silk Bitmap Tool (bitview.exe) to capture and compare the windows and areas.
Test Plan (.pln): used to create a suite of tests when combined with test scripts. Example : test.pln
Where Mytest.t is the main script file and firsttest and secondtest are testcase names in Mytest.t file. When this plan file is run it will automatically pick up first and second testcase in order and run those.
Test script (.t): used to write actual test scripts. Example: Mytest.t (Automating notepad application)
When this script runs it will execute firsttest and secondtest in order and then exit the notepad application.
Frame file (.inc): The abstraction layer used to define the windows and controls in application under test that will be further referenced in .t files. Example : Mytest.inc
Here 'Window' is main class with 'Menu', 'Menuitem' as a subclass. File, Replace are objects.
Result file (.res): contains test run results with the names of passed or failed tests along with a description of the failures. Can also contain log messages.
Other than the results file, all files are text-based and can be edited in a text editor or the SilkTest IDE. As of SilkTest 2006 the files can be saved in either ANSI or UTF-8 formats. All of the source files are compiled into pseudocode object files either when loaded or at run time if the source files are changed.