Run the Silk Test setup from the CD or through the Network.
The Silk Test Software is available in the Firesip\Europa\softare\siltest5.0.1\siltest� directory in your Network Neighborhood.
Get into the above folder and select the setup.exe file to start the installation.
During installation, it will ask for the licence file. Set the path Firesip\Europa\software\siltest 5.0.1\licence� for the licence.dat file.
In the installation process, it will ask for the Silk/test/Silk Test Agent only option. Select the Silk Test option if you are installing this for testing applications in the stand-alone machine.
For the �Will you be testing browsers?� message box, select Yes if you are going to test web based applications.
It will ask for the default browser option. Select the appropriate Browser you want to test the application using Silk Test. Note that you are allowed to select only one Browser option. By default Silk Test goes fine with Netscape browsers.
After installing, it will open the Silk Test tool with the Quick start wizard open. The quickstart wizard will assist you in creating various silk files. If you are a first time user of silktest, the continue with that.
Getting started with the Quickstart Wizard
You are using Silk Test with the testplan editor, you can use the QuickStart Wizard, which greatly simplifies the four steps of automated testing.
Then you start Silk Test the first time (or whenever you start and have no open windows), the QuickStart Wizard is displayed automatically. You can also invoke the wizard at any time by selecting File/New and clicking the Quickstart Wizard icon.
You can use the Quickstart wizard to :
1. Create a testplan
You simply name the file (giving it the .pln extension) and its directory.
2. Create a test frame,
Which contains descriptions of the GUI objects in your application that you want to test. As prompted, you simply open your application and open the various windows and dialogs that you want to test in the application. The wizard automatically records all the declarations in a file called frame.inc. You don�t have to do any coding.
3. Record testcases
You name the testcase and provide a description for the testplan, then simply record the testcase. Again, you don�t
have to do any coding. The wizard automatically sages the testcase in script (.t) file with the same name as the testplan.
