Silk Test

Silk Test is a tool specifically designed for doing REGRESSION AND FUNCTIONALITYtesting. It is developed by Segue Software Inc.

Silk Test is the industry’s leading functional testing product for e-business applications, whether Window based, Web, Java, or traditional client/server-based. Silk Test also offers test planning, management, direct database access and validation, the flexible and robust 4Test scripting language, a built in recovery system for unattended testing, and the ability to test across multiple platforms, browsers and technologies.

You have two ways to create automated tests using silktest:

1. Use the Record Testcase command to record actions and verification steps as you navigate through the application.

2. Write the testcase manually using the Visual 4Test scripting language.

1. Record Testcase

The Record / Testcase command is used to record actions and verification steps as you navigate through the application. Tests are recorded in an object-oriented language called Visual 4Test. The recorded testreads like a logical trace of all of the steps that were completed by the user. The Silk Test point and click verification system allows you to record the verification step by selecting from a list of properties that are appropriate for the type of object being tested. For example, you can verify the text is stored in a text field.

2. Write the Testcase manually

We can write tests that are capable of accomplishing many variations on a test. The key here is re-use. A test case can be designed to take parameters including input data and expected results. This "data-driven" testcase is really an instance of a class of test cases that performs certain steps to drive and verify the application-under-test. Each instance varies by the data that it carries. Since far fewer tests are written with this approach, changes in the GUI will result in reduced effort in updating tests. A data-driven test design also allows for the externalization of testcase data and makes it possible to divide the responsibilities for developing testing requirements and for developing test automation. For example, it may be that a group of domain experts create the Testplan Detail while another group of test engineers develop tests to satisfy those requirements.

In a script file, an automated testcase ideally addresses one test requirement. Specifically, a 4Test function that begins with the test case keyword and contains a sequence of 4Test statements. It drives an application to the state to be tested, verifies that the application works as expected, and returns the application to its base state.

Silk Test - Automated Testing Process

The testing process has these 4 steps :

• Creating a testplan (if you are using the testplan editor)

• Recording a test frame.

• Creating testcases

• Running testcases and interpreting their results.

Creating a testplan

If the testplan editor is used, the automated testing process is started by creating a testplan. A basic testplan is structured as a hierarchical outline and contains:

• Descriptions of individual tests and groups of tests. As many levels of description can be used.

• Statements that link the test descriptions in the plan to the 4Test routines, called testcases, that accomplish the actual work of testing

Recording a test frame

Next, record a test frame, which contains descriptions, called window declarations, of each of the GUI objects in your application. A window declaration specifies a logical, cross-platform name for a GUI object, called the identifier, and maps the identifier to the object’s actual name, called the tag. In addition, the declaration indicates the type of the object, called its class.

Creating testcases

The 4Test commands in a testcase collectively perform three distinct actions :

• Drive the application to the state to be tested.

• Verify the state (this is the heart of the testcase).

• Return the application to its original state.

The powerful object-oriented recorder can be used to automatically capture these 4Test commands to interact with the application, or to white the 4Test code manually if one is comfortable with programming languages. For maximum ease and power, these two approaches can be combined, recording the basic testcase and then extending it using 4Test’s flow of control features.

Running testcases and interpreting results

Next, run one or more testcases, either by running a collection of scripts, called a suite, or, if you are using the testplan editor, by running specific portions of the testplan. As each testcase runs, statistics are written to a results file. The results file and its associated comparison tools allow you to quickly pinpoint the problems in your application.

Advantage of silk Test

• Test automation results are what is demanded by the agile teams and that too on a per build basis. 

• Silk test makes sure about this and delivers the UI automation at the fastest play back speed possible. 

• The play back speed offered by the silk test is the fastest that is available in the current market. 

• This in turn has another advantage which is that it reduces the duration of testing which helps in submitting timely test results as required by the agile teams. 

• The saved time thus can be utilized for further testing activities. 

• Agile teams exhibit a strong and flexible collaboration among the testers and developers and thus the test-ability of the applications can be further improved up on. 

• Here, we should not miss out mentioning that the tool which provides the strongest support for custom UI properties in the industry is none other than the silk test automation tool. 

• Stable and reliable identifiers are required for the UI controls and this is also catered by the silk test automation tool. 

• Silk test is quite different from the other tools in the sense that it does not rely on a small subset of properties for identifying the objects. 

• Silk test provides very detailed test results thus minimizing the efforts that you will have to spend on the analyzation of the test failures. 

• The test failures related to the issues of test script synchronization are minimized by the reliable test execution of the silk test.

Limitations of Silk Test

• Recognition of some objects in some page is not possible due to some technical reasons.

• Some window frames may not be recognized.

• Frequent change in tag value is observed.

• Difficulty in activating some window is experienced.

• In some of the web applications and web pages the links are taken as simple text.