Test Automation: mysterious SilkTest

by Nataliia Vasylyna | April 16, 2011 10:00 am

SilkTest is really very mysterious program to automate test plans. It is mysterious, because you cannot find a lot of information in the net on test automation. The purpose of this paper is to describe briefly the main features of the software and scope of its use.

For What Can We Use SilkTest?

SilkTest is used to automate regression testing. Of course, automated testing is not such intellectual as manual testing, but allows you to make a really huge chunk of routine testing in a very short time.

Using the SilkTest means to automate much of the manual routine work to perform it quickly and with a very large percentage of the quality of test coverage.

What Is the Process of Testing for SilkTest?

As in the plans for manual (hand) test basic structural unit is a test case[1]. Test cases are self-sufficient and are responsible for testing of the functionality part of the program. Of course you can test your application with a huge “pile” of test cases, but it is better to combine and structure the test cases in test plans.

Test cases are responsible for checking the functionality of a particular part. Test plans [2]allow you to see the general picture of testing some functionality. In turn, the test plans for specific functionalities can be incorporated into more general test plans.

The implementation of the described features is supported by SilkTest medium at a sufficiently high level.
First, in a special language 4Test script the test cases are described. Test cases in SilkTest are a function that can be called from the test plan. Test cases do not return values, but they record information in a general report on testing.

Each test case is required to keep a log of their work. As a result of completion of the test plan, we get a report where the logs from each test cases conveniently structured by the name of the test case and the place of his call to the test plan.

Create a Test Plan. We Test the “Hello World!”

Let’s create a test plan, which in several places is called a test case SayHelloWorld(), which in turn displays the text “Hello World!” to the testing report.
To start, create a new file, where test cases will be implemented. Choose File-> New … 4Test Script.

[-] Testcase SayHelloWorld () [] print (“Hello World”)

Choose Run-> Testcase – a test case will start, flashed window with a run-time will be shown, and we get a report. The report will be found a log of the test case. In this case, the log will display a line “Hello world”.
It is not practical to display one static line. And what if we want to welcome Vasya, Fyodor, Peter?

Test cases can take parameters. Rewrite a test case so that it could take the name as a parameter:
[-] Testcase SayHelloWorld (string sName) [] print (“Hello” + sName) [] print (“I think, {sName}, that you are the best !!!”)

Run a test case with a string parameter “World” and get a result:
Hello World
I think, World, that you are the best!!!
Test cases can (and should) be universal. Their job may depend on the adopted parameters. And the same code can perform various actions for testing.

However, if the project is more than one test cases or one test case can be run with different parameters there is a need to make a test plan.
To do this you need to click on New and choose Testplan.

As you can see to run the necessary test cases we use keywords script and testcase. Challenge test cases are decorated in a logical hierarchical order. It will be displayed in the report in the same sequence.
Plans can be run both in full and in parts, which may be marked with a marker. Start the plan entirely (Run-> All tests) – and we get a result.
As you can see, the logical structure of the report fully complies with the structure of the test plan.
Not necessary components can be collapsed, that makes work with the editor very handy. If necessary, you can return to a certain test cases, and only restart it. If our test cases were mistakes – they would be marked in red.

Conclusion.

Of course, the real test plans are much more difficult than the test plan shown in the example. And SilkTest designed so that with the help of the environment even the most complex test plans can be made neat and intuitive.

Related Posts:

• Useful Tips for Choosing a Test Automation Tool[3]
• Automated Acceptance Testing or FitNesse to Improve the Quality of Software[4]
• Key Steps in Automated Testing[5]

Source URL: https://blog.qatestlab.com/2011/04/16/test-automation-a-note-about-the-mysterious-silktest/

---