SilkTest
Silk Test is mostly used for functional and regression testing. This tool can be used for Web, Java or .NET and client-server applications. SilkTest offers many features such as basic workflow for recording tests, data driven workflow for linking a single test case to test data values stored in external tables and code completion in the the SilkTest IDE to improve productivity of testers. Silk Test also offers functionality of test case management, test planning, data base function, date time functions etc. to make your automation more effective. Apart from the features provided by the SilkTest, plenty of 4Test scripts are available on internet for you to download and consume in your project.
For the novice users SilkTest offers record/play back option and seasoned SilkTest users can write code in the 4Test language, which is the scripting language for SilkTest. This scripting language is also referred as Visual 4Test scripting language. 4Test is an object oriented 4GL language and offers sufficient built in functionality to ease our life.

Architecture

Architecture wise, SilkTest can be divided in two parts, SilkTest host and agent. Test automation is normally developed in SilkTest host using either record/playback or by manual scripting using 4Test. Normally, test cases for SilkTest are developed in IDE (Integrated Development Environment) provided by SilkTest host software. Executing automated test suite is the responsibility of SilkTest agents. SilkTest even supports parallel execution of test cases with the help of these agents. SilkTest host can communicate with these agents residing on multiple machines and execute automated test cases on multiple machines simultaneously.

One example where this could be used is, if you need to test your application on Windows 2000, Windows XP and Windows 2000 SP 2, you can have SilkTest agent installed on these machines and run automated test suite in parallel on all these machines at once. Feature like this, saves precious execution time for the testers.

File Types

Test cases in Silk Test can be managed in the form of Test Suite (.S) or Test Plan (.P). Individual test cases are normally recorded/manually automated in the Script (.T) files. These (.T) files uses resources from the include files called (.INC) file. Include files or .INC files contain helper routine, GUI object etc. which is used by the test cases present in the (.T) file. In the plan file (.P), these individual .T files can be called and test cases present in these files can be executed. Similarly, using Test Suite (.S), you can call test cases present in all the Test Plans.

For example you might want to have all the test cases representing functionality_X in a plan file TestFunctionality_X.p file. Similarly you might have TestFunctionality_Y.p to represent all the test cases for Functionality_Y. Hierarchically, suite file will come on top of these plan files. From a suite file (.s) different plan files can be called. In this example Suite file TextXY.S will call TestFunctionality_X.p and TestFunctionality_Y.p. So in simple term, suite will contain plan, plan will contain test cases and test cases will use resources/helpers from the include files.

Apart from these files, SilkTest also produces results in a different file format called, .RES. In the older versions of SilkTest, results were only produced in the .RES format and only option to access results was to check it from IDE. Obviously, this was not the right approach since people outside testing team are also interested in the results and they will not have IDE's on their system. To address this issue, SilkTest provides capability to log results directly into MS SQL. This MS SQL server can be installed on any machine in the network and act as a Result Repository. Other machines are connected to this computer and during execution, results can be updated directly into this database. These results can be viewed using SilkTest Results Viewer which allows you to check these results from any machine using browser.

Steps

Normally, following steps are involved in start writing automated test cases in SilkTest

  • Identifying the test cases for automation

  • First step in automation should be to figure out which test cases you would like to automate? Answer to this question will be based on your project attributes like
    • Complexity involved
    • Bandwidth available
    • Tool capabilities
    • Value obtained, by automating

Steps and 4Test Language features on Next Page >>>

Recent Updates
Flash Objects and Selenium
Continuous Integration
Selenium Workshop
Delicious Testing
Pattern for automated testing of web applications
Exploratory Testing
 
Read More
Accessibility API Testing Article Backword BigBang Blackbox Blog Bottomup Boundary CaseStudies Certification DefectReport DistanceTest Equivalence FitNesse Geeks Graybox Guerrilla Testing Tips GUI HTA Humor Hybrid Internationalization Installation Integration Is it done? JUnit Measurement Mercury Quality Centre News One CPU better than two Patent PatternForAutomation Performace Checklist Rational Test Suite Regression Requirement Verification Research Rational Functional Tester Security Selenium Selenium Workshop SilkTest System Testing Templates TestComplete Tools Testing Types Testing Tools In News Testing Terms In News Testometer Test Plan TG Tips For Automation Top Down Integration Trait UAT UI Testing CheckList Unit Testing Usability VMWare Web Application Security Web Application Testing Checklist Whitebox Testing
Disclaimer  |  Privacy Policy  |  g e e k AT T e s t i n g G e e k DOT c o m
© Copyright 2008, www.TestingGeek.com